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
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
400Malformed request (subcode invalid_purl_resolve_request)
404PURL could not be resolved