resolve

Resolves an opaque PURL token for a campaign into its personalisation fields. Unauthenticated: the PURL token is the only credential. Authorization and legacy Token headers are ignored; an access_token or any other extra query parameter is rejected with 400. Requires the opaque_purls feature flag. Every resolution failure returns the same generic 404. Each campaign has a per-minute and per-day resolution budget; only requests whose token matches a usable PURL spend it, so invalid, expired, or revoked tokens do not.

For custom components:

RaiselyComponents.api.all('purls').all('resolve').post(data = {}, params = {}, headers = {}) => Promise<{result}>

See Restie Response Data for a more detailed overview of responses through the client wrapper

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
uuid
required

UUID of the ACTIVE campaign the PURL was generated for

Body Params
string
required
^[A-Za-z0-9_-]{43}$

Opaque PURL token

Responses

400

Malformed request (subcode invalid_purl_resolve_request)

404

PURL could not be resolved

Language
Credentials
Bearer
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json