Skip to content

Whether the Spanish display language is enabled (signed-out read)

GET
/settings/language/availability
curl --request GET \
--url https://api.tovarifinancial.com/settings/language/availability

UNAUTHENTICATED by design: signed-out screens choose their language before any credential exists. Answers ONLY the deployment-wide Spanish rollout flag — true only when SPANISH_LOCALE_ENABLED is exactly ‘true’ — and nothing about the caller: it reads no header (no X-Client-Locale, Accept-Language or Authorization), no query string and no request context, and touches no database. The client resolves the device language itself. The 200 is publicly cacheable (Cache-Control: public, max-age=300); the error answer is no-store.

The deployment flag

Media typeapplication/json
object
data
required
object
spanishEnabled
required
boolean
message
string
requestId
required
string
timestamp
required
string format: date-time
Examplegenerated
{
"data": {
"spanishEnabled": true
},
"message": "example",
"requestId": "example",
"timestamp": "2026-04-15T12:00:00Z"
}
Cache-Control
string

Always public, max-age=300 — the body is identical for every caller.

Internal error (no internal detail leaked)

Media typeapplication/json
object
errorCode
required

Machine-readable error code (AUTH_ERROR_CODES).

string
Allowed values: INVALID_EMAIL_FORMAT USER_ALREADY_EXISTS INVALID_INVITE_CODE WRONG_PASSWORD USER_NOT_FOUND AUTHENTICATION_FAILED EXPIRED_CODE INVALID_CODE INVALID_PASSWORD VALIDATION_ERROR SIGNUP_FAILED DATABASE_ERROR SERVICE_UNAVAILABLE PLAID_ERROR IDEMPOTENCY_CONFLICT ACCOUNT_ALREADY_LINKED NOT_FOUND
message
required
string
fieldErrors

Optional field-level validation errors, keyed by field name.

object
key
additional properties
Array<string>
requestId
required
string
timestamp
required
string format: date-time
Example
{
"errorCode": "INVALID_EMAIL_FORMAT"
}