Skip to main content
GET
Get settings
Return the effective subject’s preferences (qualityMode, learnModeDefault). A subject that has never written settings reads the server defaults. Free operation, not metered.

Authorization

This route requires the read scope. A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.

Headers

These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.

Success responses

Errors

Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.

Notes

  • Settings reads and writes are not metered.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Response

Successful Response

The caller/subject's preferences (spec 4.9, honest M1 subset).

Only fields backed by a real, round-tripping user_settings column are present. qualityMode is documented as a string (not a closed enum) so a future stored mode never breaks a tolerant reader; on the wire today it is one of fast | balanced | thorough.

learnModeDefault
boolean
required
qualityMode
string
required