People & IdentityRetrieve a person summary

Retrieve a person summary

Fetch a person profile with an expanded metrics block (sessions, devices, first-touch geography, technology, landing page, and UTM attribution). Returns data: null when no matching person exists.

curl -X GET "https://mythic-analytics.gulp.workers.dev/client/v1/data/people/8f3c1e00-4a2b-4c9d-9e11-1a2b3c4d5e6f/summary?location_id=acme-retail" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "success": true,
  "data": {
    "id": "8f3c1e00-4a2b-4c9d-9e11-1a2b3c4d5e6f",
    "properties": {},
    "identities": [
      {}
    ],
    "first_seen_at": "2024-12-25T10:00:00Z",
    "last_seen_at": "2024-12-25T10:00:00Z",
    "metrics": {
      "session_count": 10,
      "unique_sessions": 42,
      "unique_devices": 42,
      "first_geo_country_name": "John Doe",
      "last_geo_country_name": "John Doe",
      "first_browser": "example_string",
      "first_os": "example_string",
      "first_device_type": "example_string",
      "first_landing_page": "example_string",
      "first_utm_source": "example_string",
      "first_utm_medium": "example_string",
      "first_utm_campaign": "example_string",
      "first_referrer": "example_string",
      "first_referring_domain": "example_string"
    }
  }
}
GET
/people/{personId}/summary
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Agency key as bearer token. Format: Bearer ak_.... Must name a location via the location_id query parameter or X-Location-Id header. Scoped keys (mcp_) are accepted too and need people:read. See Using an mcp_ key over HTTP.

Agency key as bearer token. Format: Bearer ak_.... Must name a location via the location_id query parameter or X-Location-Id header. Scoped keys (mcp_) are accepted too and need people:read. See Using an mcp_ key over HTTP.
Bearer Token
Bearer Tokenstring
Required

Location secret key as bearer token. Format: Bearer sk_.... Resolves its own location — no location_id needed.

Location secret key as bearer token. Format: Bearer sk_.... Resolves its own location — no location_id needed.
path
personIdstring
Required

Canonical person id, or any raw identity value linked to the person (anonymous id, device id, email, or user id).

query
location_idstring

Required for agency (ak_) keys. Ignored for secret (sk_) keys, which resolve their own location. May also be supplied via the X-Location-Id header.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Agency key as bearer token. Format: Bearer ak_.... Must name a location via the location_id query parameter or X-Location-Id header. Scoped keys (mcp_) are accepted too and need people:read. See Using an mcp_ key over HTTP.

header
Authorizationstring
Required

Bearer token. Location secret key as bearer token. Format: Bearer sk_.... Resolves its own location — no location_id needed.

Path Parameters

personIdstring
Required

Canonical person id, or any raw identity value linked to the person (anonymous id, device id, email, or user id).

Example:
8f3c1e00-4a2b-4c9d-9e11-1a2b3c4d5e6f

Query Parameters

location_idstring

Required for agency (ak_) keys. Ignored for secret (sk_) keys, which resolve their own location. May also be supplied via the X-Location-Id header.

Example:
acme-retail

Responses

successboolean
datastring