Get the merchant's validation status
Pre-validation is Sarvex’s own suite against the store’s UCP endpoints, with the
spec version targeted. sandbox/production are always not_submitted — they
are external verdicts Sarvex does not run; kept on the schema for compatibility
rather than removed.
/stores/{store_id}/validation/statusAuthorizationBearer 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.
store_idstringrequiredA store the caller's merchant owns. Authorized server-side against the principal; not a free-form tenant selector.
Validation status.
pre_validationstringnot_runpassingfailingsandboxstringnot_submittedpendingpassedfailedproductionstringnot_submittedpendinglivetarget_spec_versionstringlast_run_atstring<date-time> | nullopen_failuresvalidation_failure[]Show propertiesHide properties
validation_failurerequirementstringspec_sectionstringexpectedobjectreceivedobjectsummarystring