User & Company
Endpoints for retrieving user and company metadata, as well as segments.Endpoint | Description |
---|---|
/api/v1/analytics/exports/lookups/user_properties | Get user properties |
/api/v1/analytics/exports/lookups/company_properties | Get company properties |
/api/v1/analytics/exports/lookups/segments | Get segments (paginated) |
Features & Events
Endpoints for retrieving features, events, and event property metadata.Endpoint | Description |
---|---|
/api/v1/analytics/exports/lookups/features_events | Get features & events |
/api/v1/analytics/exports/lookups/events_properties | Get trackable events’ properties/attributes (paginated) |
Experiences & UI
Endpoints for retrieving experiences, UI elements, surveys, resource center modules, and checklists.Endpoint | Description |
---|---|
/api/v1/analytics/exports/lookups/flows | Get flows (experiences) |
/api/v1/analytics/exports/lookups/banners | Get banners |
/api/v1/analytics/exports/lookups/spotlights | Get spotlights |
/api/v1/analytics/exports/lookups/surveys | Get surveys (with modules) |
/api/v1/analytics/exports/lookups/resource_center_modules | Get resource center modules |
/api/v1/analytics/exports/lookups/checklists | Get checklists (with tasks) |
How to Use
All endpoints require authentication via your API key:Example Response
Pagination
Some endpoints (such asevents_properties
and segments
) are paginated. The response includes a cursor
object in the metadata
section:
after
: Cursor for fetching the next set of results.before
: Cursor for fetching previous results (if available).limit
: Number of results per request.total_count
: Total number of available records.
Example Paginated Request
Example Paginated Response
- Always check if
cursor.after
exists in the response before making the next request. - If
cursor.after
isnull
, you have reached the last page of data. - To modify the number of results per request, use the
limit
parameter in your query string (default is 50).