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

Reclassify many manual steps at once

POST/operator/manual-steps/bulk-retag
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.

Scopes:operator
Request body
requiredapplication/json
step_idsstring[]required
min items 1
dispositionmanual_step_dispositionrequired
default: "unclassified"
Allowed:unclassifiedautomatetemplatiseaccept_manual
Responses
200

Retagged.

statusstring
steps_retaggedinteger
dispositionmanual_step_disposition
default: "unclassified"
Allowed:unclassifiedautomatetemplatiseaccept_manual
403

Authenticated but not permitted (e.g. non-operator on an operator route).

errorobjectrequired
Show properties
codestringrequired
messagestringrequired
detailsobject | null
422

Request body failed validation.

errorobjectrequired
Show properties
codestringrequired
messagestringrequired
detailsobject | null
Try it
Server
Authorization
Bodyapplication/json
Request
curl -X POST "https://api.sarvex.example.com/v1/operator/manual-steps/bulk-retag" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "step_ids": [
    "string"
  ],
  "disposition": "unclassified"
}'
Response
{
  "status": "success",
  "steps_retagged": 0,
  "disposition": "unclassified"
}