Persons-5
For instructions on how to authenticate to use this endpoint, see API overview.
Endpoints
GET | |
GET | |
POST | |
GET | |
GET | |
GET |
Retrieve persons lifecycle
This endpoint is meant for reading and deleting persons. To create or update persons, we recommend using the capture API, the $set and $unset properties, or one of our SDKs.
Path parameters
- project_idstring
Query parameters
- formatstringOne of:
"csv""json"
Example request
GET /api /projects /:project_id /persons /lifecycleExample response
Status 200 No response body
Retrieve persons lifecycle
This endpoint is meant for reading and deleting persons. To create or update persons, we recommend using the capture API, the $set and $unset properties, or one of our SDKs.
Path parameters
- project_idstring
Query parameters
- formatstringOne of:
"csv""json"
Example request
GET /api /projects /:project_id /persons /lifecycleExample response
Status 200 No response body
Retrieve persons properties at time
Get person properties as they existed at a specific point in time.
This endpoint reconstructs person properties by querying ClickHouse events for $set and $set_once operations up to the specified timestamp.
Query parameters:
- distinct_id: The distinct_id of the person
- timestamp: ISO datetime string for the point in time (e.g., "2023-06-15T14:30:00Z")
- include_set_once: Whether to handle $set_once operations (default: false)
- debug: Whether to include debug information with raw events (default: false)
Required API key scopes
person:readPath parameters
- project_idstring
Query parameters
- debugboolean
- distinct_idstring
- formatstringOne of:
"csv""json" - include_set_onceboolean
- person_idstring
- timestampstring
Response
Example request
GET /api /projects /:project_id /persons /properties_at_timeExample response
Status 200
Status 400
Status 404
Status 500
Retrieve persons properties at time
Get person properties as they existed at a specific point in time.
This endpoint reconstructs person properties by querying ClickHouse events for $set and $set_once operations up to the specified timestamp.
Query parameters:
- distinct_id: The distinct_id of the person
- timestamp: ISO datetime string for the point in time (e.g., "2023-06-15T14:30:00Z")
- include_set_once: Whether to handle $set_once operations (default: false)
- debug: Whether to include debug information with raw events (default: false)
Required API key scopes
person:readPath parameters
- project_idstring
Query parameters
- debugboolean
- distinct_idstring
- formatstringOne of:
"csv""json" - include_set_onceboolean
- person_idstring
- timestampstring
Response
Example request
GET /api /projects /:project_id /persons /properties_at_timeExample response
Status 200
Status 400
Status 404
Status 500
Create persons reset person distinct id
Reset a distinct_id for a deleted person. This allows the distinct_id to be used again.
Required API key scopes
person:writePath parameters
- project_idstring
Query parameters
- formatstringOne of:
"csv""json"
Request parameters
- properties
Example request
POST /api /projects /:project_id /persons /reset_person_distinct_idExample response
Status 200 No response body
Create persons reset person distinct id
Reset a distinct_id for a deleted person. This allows the distinct_id to be used again.
Required API key scopes
person:writePath parameters
- project_idstring
Query parameters
- formatstringOne of:
"csv""json"
Request parameters
- properties
Example request
POST /api /projects /:project_id /persons /reset_person_distinct_idExample response
Status 200 No response body
Retrieve persons stickiness
This endpoint is meant for reading and deleting persons. To create or update persons, we recommend using the capture API, the $set and $unset properties, or one of our SDKs.
Path parameters
- project_idstring
Query parameters
- formatstringOne of:
"csv""json"
Example request
GET /api /projects /:project_id /persons /stickinessExample response
Status 200 No response body
Retrieve persons stickiness
This endpoint is meant for reading and deleting persons. To create or update persons, we recommend using the capture API, the $set and $unset properties, or one of our SDKs.
Path parameters
- project_idstring
Query parameters
- formatstringOne of:
"csv""json"
Example request
GET /api /projects /:project_id /persons /stickinessExample response
Status 200 No response body
Retrieve persons trends
This endpoint is meant for reading and deleting persons. To create or update persons, we recommend using the capture API, the $set and $unset properties, or one of our SDKs.
Path parameters
- project_idstring
Query parameters
- formatstringOne of:
"csv""json"
Example request
GET /api /projects /:project_id /persons /trendsExample response
Status 200 No response body
Retrieve persons trends
This endpoint is meant for reading and deleting persons. To create or update persons, we recommend using the capture API, the $set and $unset properties, or one of our SDKs.
Path parameters
- project_idstring
Query parameters
- formatstringOne of:
"csv""json"
Example request
GET /api /projects /:project_id /persons /trendsExample response
Status 200 No response body
Retrieve persons values
This endpoint is meant for reading and deleting persons. To create or update persons, we recommend using the capture API, the $set and $unset properties, or one of our SDKs.
Required API key scopes
person:readPath parameters
- project_idstring
Query parameters
- formatstringOne of:
"csv""json"
Example request
GET /api /projects /:project_id /persons /valuesExample response
Status 200 No response body
Retrieve persons values
This endpoint is meant for reading and deleting persons. To create or update persons, we recommend using the capture API, the $set and $unset properties, or one of our SDKs.
Required API key scopes
person:readPath parameters
- project_idstring
Query parameters
- formatstringOne of:
"csv""json"
Example request
GET /api /projects /:project_id /persons /values