Skip to main content
PATCH
/
api
/
v1
/
organizations
/
current
/
preferences
cURL
curl -sS -X PATCH "$FLUIDE_BASE_URL/api/v1/organizations/current/preferences" \
  -H "Authorization: Bearer $FLUIDE_ACCESS_TOKEN" \
  -H "X-Fluide-Api-Key: $FLUIDE_API_KEY" \
  -H "X-Fluide-Client-Id: fluide-developer" \
  -H "Content-Type: application/json" \
  -d '{}'
{
  "success": true,
  "message": "Operation completed successfully",
  "data": {}
}

Authorizations

​
Authorization
string
header
required

Access token JWT. Use as Authorization: Bearer . In the API playground, paste the JWT only.

​
X-Fluide-Api-Key
string
header
default:fl_dev_your_key
required

Developer API key (fl_dev_...). Required on every API call with a machine access token.

​
X-Fluide-Client-Id
string
header
default:fluide-developer
required

First-party client audience. Must match the fluide_client_id claim on the JWT. Use fluide-developer for Connect.

Body

application/json
​
locale
enum<string>

BCP 47 locale (en | fr supported in admin)

Available options:
en,
fr
Example:

"en"

​
timeZone
string

IANA timezone identifier

Maximum string length: 64
Example:

"Africa/Douala"

​
billingRegion
enum<string>

Billing region for price book resolution

Available options:
GLOBAL,
EU,
US
Example:

"GLOBAL"

​
billingCurrency
string

ISO 4217 billing currency

Required string length: 3
Example:

"XAF"

Response

Patch active organization locale, timezone, and billing profile preferences

​
success
boolean
required

Whether the request succeeded

Example:

true

​
message
string
required

Human-readable outcome message (localized when i18n is configured)

Example:

"Operation completed successfully"

​
data
object

Endpoint-specific payload