Skip to content
Featureflip Docs

Records SDK events for analytics and debugging.

POST
/v1/sdk/events
 
curl --request POST \
  --url https://eval.featureflip.io/v1/sdk/events \
  --header 'Authorization: <Authorization>' \
  --header 'Content-Type: application/json' \
  --data '{ "events": [ { "type": "Evaluation", "flagKey": "example", "userId": "example", "variation": "example", "timestamp": "2026-04-15T12:00:00Z", "metadata": { "additionalProperty": "example" }, "prerequisiteKey": "example", "reason": "example", "ruleId": "example" } ] }'

Authorizations

Section titled “ Authorizations ”

Request Body

Section titled “ Request Body ”

Batch of events to record.

object
events
required
Array<object>
nullable
object
type
required
string
Allowed values: Evaluation Impression Identify Custom
flagKey
required
string
nullable
userId
string
nullable
variation
string
nullable
timestamp
string format: date-time
metadata
object
key
additional properties
prerequisiteKey
string
nullable
reason

Optional. Why the evaluation served its variation: rule-match, fallthrough, flag-disabled, prerequisite-failed, error or flag-not-found. Used to attribute evaluation traffic in flag analytics; events without it count as an unknown source.

string
nullable
ruleId

Optional. The id of the targeting rule that matched, when reason is rule-match.

string
nullable

Responses

Section titled “ Responses ”

202

Section titled “ 202 ”

Events were accepted for processing.

401

Section titled “ 401 ”

SDK key is missing or invalid.

Media type application/json
object
type
string
nullable
title
string
nullable
status
integer format: int32
nullable
detail
string
nullable
instance
string
nullable
key
additional properties

Example generated

{
  "type": "example",
  "title": "example",
  "status": 1,
  "detail": "example",
  "instance": "example"
}