Localization

The Betflow B2B API supports localized responses for trend narratives and descriptions. Send the X-Language header to receive translated content.

Usage

Include the X-Language header in your request:

curl -X POST https://api.odditt.com/v1/trends/mixed-flows \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "X-Language: ES" \
  -H "Content-Type: application/json" \
  -d '{"sport_id": 1, "league_id": 7, "page": 1, "page_size": 10}'

The header value is case-insensitive — es, ES, and Es are all equivalent.

Supported Languages

Code	Language
EN	English (default)
ES	Spanish
PT	Portuguese
IT	Italian
CS	Czech

When no X-Language header is provided, responses default to English.

What Gets Translated

Localization applies to trend narrative content — the human-readable text that describes statistical insights:

• Fact condition descriptions (e.g. "has scored 20+ points in 8 of the last 10 games")
• Fun flow descriptions

Reference data (sport names, league names, team names, player names) and structured fields (IDs, numbers, timestamps) are not translated.

Supported Endpoints

The X-Language header is supported on all trends service endpoints:

• /v1/trends/* — all trend endpoints
• /v1/betting/* — all betting endpoints
• /v1/games/* — all game endpoints

Reference endpoints (/v1/references/*) do not support localization.

note

The language body parameter is deprecated. Use the X-Language header instead. When both are provided, the header takes precedence.