DOCUMENTATIONv2

GET

Identity · mobile

Issue messaging ticket

/api/v2/identity/mobile/messaging/ticket

AUTHENTICATIONBearer token · trust:readAUTHORITATIVE OWNERidentity-serviceCONTRACT AUTHORITYGenerated Rust OpenAPISTATUSSource ready · production listed

PURPOSE + BUSINESS CONTEXT

Issue a short-lived device- and session-bound messaging ticket for an installation with an active signed device credential.

WHEN THIS CALL IS USEFUL

Request immediately before opening or refreshing the messaging transport, after the same authenticated session has an active registered messaging-device credential.

OUTCOME · Discover

What changes

Issues a secret hmt_v1 ticket bound to the current profile, session, and device for at most 600 seconds. It does not send a notification, change preferences, acknowledge an event, or authorize any owning business resource.

WHY IT MATTERS

Gives people and agents a contract-backed way to discover issue messaging ticket.
Separates subject identity, consent, evidence, provider output, review, issuer credentials, and relying-party acceptance instead of collapsing them into a universal trust score.

ISOLATION + AUTHORITY

Bearer subject, tenant, purpose, policy version, role, issuer, reviewer, provider, and relying-party boundaries remain distinct. The response or transition grants no payment, custody, settlement, publisher, matching, or trading authority and must not expose regulated evidence beyond the live schema.

BEFORE YOU CALL

Authenticate at the documented boundary: bearer+scope.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Resolve the applicable purpose, policy version, consent or role basis, and required assurance before relying on this result.

WHAT TO DO NEXT

Select one canonical identifier from the response and open its detail operation when the live contract exposes one.
Use the returned lifecycle state and policy version to choose the next least-privilege trust action; do not infer a missing stage.

AGENT GUIDANCE

Use issue messaging ticket only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Treat policy availability, consent, evidence capture, completed checks, review, decision, credential issuance, validity, and relying-party acceptance as separate facts.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

MACHINE CONTRACT

The exact deployed parameters, schemas, responses, security requirements, and Hybrid-Chain agent metadata are authoritative at this operation's production OpenAPI JSON Pointer. The readable tables below add integration guidance; the deployed OpenAPI controls if guidance and the machine contract ever differ.

Open the authoritative production contract ↗

EXTENDED INTEGRATION GUIDANCE

Readable request and response reference

Examples illustrate integration intent; the referenced OpenAPI operation and component schemas define the executable shape.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE

AuthorizationheaderRequired

Bearer tokenCredential containing the trust:read scope.EXAMPLEBearer hc_live_…

RESPONSES

Status and payload examples

200Short-lived device- and session-bound messaging bearer ticket returned under no-store.Read completed · JSON RESPONSE+

{
  "ticket": "hmt_v1.opaque-secret",
  "expires_in": 300,
  "profile_id": "profile-01J…",
  "device_id": "mobile-installation-01",
  "session_id": "session-01J…"
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then select one canonical identifier from the response and open its detail operation when the live contract exposes one.
RETRY SAFETY: Repeat only when the integration needs a fresher authoritative projection.
STATE RECONCILIATION: Use returned identifiers and versions as the comparison point for later reads. Refresh the specific profile or account projection and compare tenant, profile, lifecycle, and version identifiers before retrying.

401The bearer credential is missing or invalid.Authentication required · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "The bearer credential is missing or invalid."
}

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Discard the rejected credential, complete the documented authentication or reassertion flow, and rebuild any request signature with fresh timestamps and nonces.
RETRY SAFETY: Retry only with a newly valid credential and fresh replay-protection values. Do not replay an expired signature.
STATE RECONCILIATION: Authentication failed before an authoritative read was returned for the authenticated profile, tenant brand, referral, funding, and account-lifecycle projections.
ESCALATE WHEN: Escalate when a fresh session resolves to an unexpected tenant or profile, or when an account lifecycle receipt cannot be found after reconciliation.

403The session lacks trust:read or an active messaging-device credential.Authority or policy denied · JSON RESPONSE+

{
  "code": "messaging_device_required",
  "message": "The session lacks trust:read or an active messaging-device credential."
}

INTEGRATION DECISIONmessaging_device_required

CALLER ACTION: Verify the exact scope, tenant or workspace membership, owner boundary, step-up purpose, feature policy, and resource eligibility. Never broaden authority automatically.
RETRY SAFETY: Do not retry until the missing authority or policy condition has been deliberately resolved with least privilege.
STATE RECONCILIATION: Confirm the caller and resource resolve to the same authority boundary for the authenticated profile, tenant brand, referral, funding, and account-lifecycle projections.
ESCALATE WHEN: Escalate when a fresh session resolves to an unexpected tenant or profile, or when an account lifecycle receipt cannot be found after reconciliation.

503Authoritative Identity messaging ticket issuance is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "identity_messaging_unavailable",
  "message": "Authoritative Identity messaging ticket issuance is unavailable."
}

INTEGRATION DECISIONidentity_messaging_unavailable

CALLER ACTION: Treat the failure as transient and preserve the last known good representation without presenting it as fresh.
RETRY SAFETY: Retry with bounded exponential backoff and jitter; stop after the integration's failure budget is exhausted.
STATE RECONCILIATION: Refresh the specific profile or account projection and compare tenant, profile, lifecycle, and version identifiers before retrying.
ESCALATE WHEN: Escalate when a fresh session resolves to an unexpected tenant or profile, or when an account lifecycle receipt cannot be found after reconciliation.

OPERATIONAL NOTES

Security and lifecycle guarantees

Call immediately before opening or refreshing the messaging transport. The request accepts no query parameters or body, and the same authenticated session must own an active registered device binding.
The hmt_v1 ticket is a bearer secret and expires in at most 600 seconds. Never place it in a URL, prompt, log, analytics event, persistent database, shared cache, crash report, or support transcript; discard it at expiry.
Ticket issuance does not send, deliver, read, acknowledge, or change a notification. A delivered message is only a prompt to re-read the owning API resource; message order and delivery are not canonical business state.
The response is Cache-Control: no-store and Pragma: no-cache. Ticket possession grants messaging transport access only and cannot widen any business-domain authority.

DOCUMENTATION STATUS

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-09-11T06:35:11.572Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation ↗Return to the V2 directory ↗