Record page view

Record an event for one of your organization’s configured websites. Your API key identifies your organization; projectSlug selects the website. Follow the traffic guide for trusted identity and country handling.

Website traffic guide · All endpoints · SDK: recordPageView

Authentication

Server-to-server HMAC. Your key selects the partner; your backend must authorize the end user.

CRISP enables access to the features agreed for your integration. Contact CRISP if an enabled feature returns an access error.

Idempotency-Key: Not required by this operation. Signing and authentication →

Request fields

Required means the field must be present. Nullable means an explicit JSON null is allowed; it does not mean optional.

Path parameters

None.

Query parameters

None.

Header parameters

No operation-specific headers. The HMAC headers above still apply.

JSON body

Field	Type / presence	Description and constraints
`eventId`	`string` Required Non-null	Format: uuid
`projectSlug`	`string` Required Non-null	—
`visitorToken`	`string` Required Non-null	—
`pagePath`	`string` Required Non-null	—
`referrerHost`	`string \| null` Optional Nullable	Expand the structure below.
referrerHost: expand fields string
`countryCode`	`string \| null` Optional Nullable	Expand the structure below.
countryCode: expand fields string
`isLanding`	`boolean` Optional Non-null	—

Additional fields are not allowed in this object.

Request example

Illustrative identifiers only: replace them with resources from your integration. Keep credentials on your backend. HTTP placeholders must be signed; the SDK signs automatically. Financial intent keys must be persisted and unique per new action.

POST /v1/traffic/page-views
Host: partner-api.crisp.trade
X-Crisp-Partner-Key: <server-key-id>
X-Crisp-Timestamp: <fresh-ISO-8601-UTC-timestamp>
X-Crisp-Nonce: <fresh-unique-nonce>
X-Crisp-Signature: <computed-base64-HMAC>
Content-Type: application/json

{
  "eventId": "11111111-1111-4111-8111-111111111111",
  "projectSlug": "main",
  "visitorToken": "example-visitor-token",
  "pagePath": "/markets"
}

Response fields

HTTP responses use the envelope below. SDK calls expose its payload as result.data, with HTTP status and request metadata on the SDK wrapper.

202 · Accepted; inspect lifecycle state. This is not proof of a fill or payout.

Accepted for processing, not proof of a fill, completed provisioning or settled payout. Inspect resource state and follow the recovery guide.

Data payload

Field	Type / presence	Description and constraints
`recorded`	`boolean` Required Non-null	—

Additional fields are not allowed in this object.

Full HTTP envelope

Field Type / presence Description and constraints

data

object

Required

Non-null

Expand the structure below.

data: expand fields

Field	Type / presence	Description and constraints
`recorded`	`boolean` Required Non-null	—

Additional fields are not allowed in this object.

requestId

string

Required

Non-null

Request correlation ID for debugging and support.

Additional fields are not allowed in this object.

Response example

Schema illustration, not live account data. Null means unavailable or not applicable, never an invented zero. Empty arrays do not imply the endpoint always returns no results.

202 response JSON

{
  "data": {
    "recorded": false
  },
  "requestId": "example-request-id"
}

Errors and recovery

Status	Meaning
`400`	Inspect error.code and retain the original financial intent.
`401`	Inspect error.code and retain the original financial intent.
`403`	Inspect error.code and retain the original financial intent.
`404`	Not visible for this account. A recovery lookup miss is not proof that an in-flight submission failed.
`409`	Inspect error.code and retain the original financial intent.
`429`	Inspect error.code and retain the original financial intent.
`500`	Inspect error.code and retain the original financial intent.
`502`	Inspect error.code and retain the original financial intent.
`503`	Inspect error.code and retain the original financial intent.

Inspect the error code and outcomeUnknown, not just the HTTP status. Preserve the original intent after financial uncertainty. Read-only retries should honor Retry-After. Recovery workflow →

Error response fields

Field Type / presence Description and constraints

error

object

Required

Non-null

Expand the structure below.

error: expand fields

Field	Type / presence	Description and constraints
`code`	`string` Required Non-null	—
`message`	`string` Required Non-null	—
`requestId`	`string` Required Non-null	Request correlation ID for debugging and support.

Additional fields are not allowed in this object.

Raw contract

OpenAPI download · Advanced schema and legacy anchor

Authentication

Request fields

Path parameters

Query parameters

Header parameters

JSON body

Request example

Response fields

202 · Accepted; inspect lifecycle state. This is not proof of a fill or payout.

Data payload

Response example

Errors and recovery

Raw contract

On this page