Skip to content
SarvexDocs
Esc
↑↓navigate↵open⌘Jpreview

Revert a write-back to its prior value

POST/stores/{store_id}/catalog/write-backs/{write_back_id}/revert
Authorization
AuthorizationBearer token (JWT) · headerrequired

JWT issued by the external IdP via the OAuth 2.0 authorization-code flow (Kinde in production; a simulator in test). The client obtains it and sends it as a Bearer token on every authenticated call. Sarvex's services verify it — issuer, audience, signature (IdP JWKS), expiry — and read identity and tenant from its claims. Sarvex does not issue or revoke these tokens. merchant_id/store_id are read from the verified claims (and the merchant→store mapping), never from the URL. The operator scope is required for /operator/*. Operators acting on a specific merchant pass the X-Operate-As header, which is recorded in the audit log.

Path parameters
store_idstringrequired
write_back_idstringrequired
Header parameters
Idempotency-Keystring

Client-generated key; replays return the original result.

Responses
200

Reverted.

revertedboolean
404

Resource not found within the caller's tenant.

errorobjectrequired
Show properties
codestringrequired
messagestringrequired
detailsobject | null
Try it
Server
Authorization
Parameters
Request
curl -X POST "https://api.sarvex.example.com/v1/stores/string/catalog/write-backs/string/revert" \
  -H "Authorization: Bearer YOUR_TOKEN"
Response
{
  "reverted": true
}