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

Get the raw served manifest

GET/stores/{store_id}/presence/manifest
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

A store the caller's merchant owns. Authorized server-side against the principal; not a free-form tenant selector.

Responses
200

The current manifest as served to agents, plus cache state.

manifestobject

The UCP capability document as served.

cacheobject
Show properties
built_atstring<date-time>
ttl_secondsinteger
staleboolean
source_watermarkstring<date-time>
Try it
Server
Authorization
Parameters
Request
curl -X GET "https://api.sarvex.example.com/v1/stores/string/presence/manifest" \
  -H "Authorization: Bearer YOUR_TOKEN"
Response
{
  "manifest": {},
  "cache": {
    "built_at": "2019-08-24T14:15:22Z",
    "ttl_seconds": 0,
    "stale": true,
    "source_watermark": "2019-08-24T14:15:22Z"
  }
}