Redirect an end user

Méthode GET {API_BASE}/v2.1/user/{key}/{crid}/redirect

Redirect to the recording or preview page according to current code status.

Autorisation

Scope requis user_v2

The API key is intentionally kept in the path for V2 compatibility: /v2.1/client/{key}/{crid}/... or /v2.1/user/{key}/{crid}/.... Client routes require the client_v2 scope. User routes require the user_v2 scope. Unknown, expired, revoked, malformed, or wrong-scope keys return the legacy JSON error envelope.

Paramètres

Nom	Emplacement	Type	Requis	Contraintes	Description
`key`	Chemin	`string`	Requis		API key kept in the URL for V2 compatibility. Requires `client_v2` or `user_v2` depending on the route.
`crid`	Chemin	`string`	Requis		Client reference ID, usually an order or campaign reference.

Réponses

302

Redirect to the resolved user-facing destination.

400 application/json Schéma LegacyError

Invalid key, CRID, payload, message state or business precondition.

403 application/json Schéma LegacyError

Key is authenticated but scope or platform constraints are invalid.

json 403

{
  "status": 1,
  "error": "forbidden"
}

forbidden

json 403

{
  "status": 1,
  "error": "forbidden"
}

invalidPlatformConstraint

json 403

{
  "status": 1,
  "error": "key_invalid"
}