Skip to content
Indiana
Dashboard
Docs
Browse docs / Evaluate remote Features

Evaluate remote Features

POST/api/v1/features/evaluate

0.3 source candidate: evaluate only flags configured for server evaluation. Customer sessions cannot supply customerId; verified identity and stored attributes override caller values. Returns results and configuration generation; the server records exposures.

API v1Updated

Make the request

0.3 source candidate: evaluate only flags configured for server evaluation. Customer sessions cannot supply customerId; verified identity and stored attributes override caller values. Returns results and configuration generation; the server records exposures.

Credential
Server API key or customer token. Customer calls cannot select another customer.
Permission
features:read
Set the base URL and App ID from SDK setup. These examples use placeholders and do not execute requests. Never put a server key in browser code.
request.shShell
curl -X POST "$INDIANA_BASE_URL/api/v1/features/evaluate" \  -H "Authorization: Bearer $INDIANA_CUSTOMER_TOKEN" \  -H "X-Indiana-Project: $INDIANA_PROJECT_ID" \  -H "X-Indiana-Protocol: 0.3" \  -H "X-Indiana-Environment: sandbox" \  -H "Content-Type: application/json" \  -d '{  "attributes": {}}'

The response tab lists field types, not an example payload. Actual values depend on customer state.

Request parameters

JSON body

attributesobjectRequired

Up to 128 keys, 1–128 characters each, and 64 KiB total JSON. Values may contain nested JSON, limited to 20 levels and 10,000 nodes per value. Reserved fields are rejected. Null is a value; delete keys with removeAttributes. Tags live in attributes.tags and change through tagChanges.

featuresarrayOptional

The features value for this operation. Its accepted type and constraints are listed above and below.

minItems: 1 · maxItems: 500

customerIduuidOptional

Indiana customer ID mapped from a verified identity on the server. Omit for customer-token calls, which use the token-bound customer.

Response fields

Successful responses include requestId and scope. Use the actual business status or accepted field to determine the result. Optional fields are omitted when unavailable.

HTTP 200 · application/json

requestIduuidRequired

Server-generated HTTP request UUID. Include it when reporting a failed request.

scopeobjectRequired

The App and environment of this response. Headers only verify scope; they cannot switch key scope.

Show child fields
projectIdstringRequired

App ID bound to the credential.

minLength: 1

environmentenumRequired

Separate data scope: sandbox or live.

Show allowed values

"sandbox""live"

generationstringRequired

The generation value for this operation. Its accepted type and constraints are listed above and below.

pattern: ^[a-f0-9]{64}$

evaluatedAtdate-timeRequired

UTC server time at which this state was evaluated.

expiresAtdate-time | nullRequired

ISO 8601 UTC expiry. Expired sessions and reservations cannot be reused.

featuresobjectRequired

The features value for this operation. Its accepted type and constraints are listed above and below.

Handle errors

Common failures
CodeRecovery
UNAUTHENTICATEDVerify the key or refresh the expired customer token once.
FORBIDDENCheck current key permissions and customer access.
INVALID_REQUESTCheck field types, UUIDs, decimal strings and mutually exclusive fields.
SCOPE_MISMATCHUse the App and environment bound to the credential.

Common failures

  • UNAUTHENTICATED

    Recovery
    Verify the key or refresh the expired customer token once.
  • FORBIDDEN

    Recovery
    Check current key permissions and customer access.
  • INVALID_REQUEST

    Recovery
    Check field types, UUIDs, decimal strings and mutually exclusive fields.
  • SCOPE_MISMATCH

    Recovery
    Use the App and environment bound to the credential.

Related:All request and error conventions·Back to endpoint index