Reclassify a manual step
PUT
/operator/manual-steps/{step_id}/retagAuthorization
AuthorizationBearer token (JWT) · headerrequiredJWT 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:
operatorPath parameters
step_idstringrequiredRequest body
requiredapplication/jsondispositionmanual_step_dispositionrequireddefault: "unclassified"
Allowed:
unclassifiedautomatetemplatiseaccept_manualResponses
200
Retagged.
statusstringstep_idstringdispositionmanual_step_dispositiondefault: "unclassified"
Allowed:
unclassifiedautomatetemplatiseaccept_manual403
Authenticated but not permitted (e.g. non-operator on an operator route).
errorobjectrequiredShow propertiesHide properties
codestringrequiredmessagestringrequireddetailsobject | null422
Request body failed validation.
errorobjectrequiredShow propertiesHide properties
codestringrequiredmessagestringrequireddetailsobject | null