Skip to main content
Apostra user preferences are scoped to the authenticated user. They control the default language for new Apostra conversations and expose display preferences the UI can use when formatting Apostra surfaces.
These endpoints are available only when Apostra is enabled for the caller’s account.

Get preferences

GET /api/v2/murph/user-preferences Returns the caller’s current Apostra preferences. If the request is authenticated with a service token instead of a user session, the endpoint returns the same shape with all preference fields set to null.
curl

Response

Set default language

PUT /api/v2/murph/user-preferences/language Sets the caller’s user-level default Apostra language. New conversations inherit this value at creation time. Existing conversations keep their own language override unless you update them separately. Send preferredLanguage: null to clear the user default and return new conversations to auto-detect.
curl

Request body

Response

The response returns the full preference object now in effect.

Supported languages

Errors

  • 400 VALIDATION_ERROR — invalid request body, unsupported language code, invalid locale, invalid timezone, or invalid currency.
  • 400 BAD_REQUEST — setting a user-level default was attempted from a non-user auth context.
  • 401 UNAUTHORIZED — missing or invalid bearer token.
  • 403 FORBIDDEN — Apostra is not enabled for the caller’s account.
See Errors for the full error contract.

Ask Apostra

How storefront operators use Apostra in the platform.

Apostra confirmations

Confirmation flows for Apostra actions that need approval.