API Docs

REST API Endpoints

4min

We support a number of both server-side and client-side implementation patterns, including no-code solutions.

We also support both REST and Websocket (JSON RPC) style integrations. If you aren't sure where to start, feel free to contact us and we'll discuss what works best for your use case.

Accounts

POST
Request
Body Parameters
key
required
String
ID of the account
name
optional
String
Name of the account
custom_fields
optional
Object
Custom fields to set for the account. Each custom field is a key: value pair.
account_plans
optional
Array
Array of plans the account is subscribed to. Each array element is an object: { plan_key: "value" }.
feature _overrides
optional
Array
Array of feature overrides to set for the account. Each array element is an object: { feature_key: "value", variant_key: "value" }.
Curl
Ruby
Responses
200
400


Features

POST
Request
Body Parameters
detailed
optional
Boolean
whether to retrieve all details associated with the feature, or just the value.
context
required
Object
Name of the account
Curl
Ruby
Responses
200

POST
Request
Body Parameters
detailed
optional
Boolean
whether to retrieve all details associated with the feature, or just the value.
context
required
Object
Name of the account
Curl
Ruby
Responses
200


Metrics

POST
Request
Body Parameters
key
required
String
Metric key
value
required
Integer
Metric value
account_key
required
String
Account key
idempotency_key
optional
String
time
optional
String
Datetime in ISO 8601 format.
Curl
Ruby
Responses
202




Updated 15 Aug 2024
Doc contributor
Doc contributor
Did this page help you?