Whether the Spanish display language is enabled (signed-out read)
const url = 'https://api.tovarifinancial.com/settings/language/availability';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.tovarifinancial.com/settings/language/availabilityUNAUTHENTICATED 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.
Responses
Section titled “Responses”The deployment flag
object
object
Examplegenerated
{ "data": { "spanishEnabled": true }, "message": "example", "requestId": "example", "timestamp": "2026-04-15T12:00:00Z"}Headers
Section titled “Headers”Always public, max-age=300 — the body is identical for every caller.
Internal error (no internal detail leaked)
object
Machine-readable error code (AUTH_ERROR_CODES).
Optional field-level validation errors, keyed by field name.
object
Example
{ "errorCode": "INVALID_EMAIL_FORMAT"}