Submits a request to register a requested_url for use as partner_return_url in verification flows. 201 does not mean the URL is already approved — check status. Once approved, the server matches incoming partner_return_url values against the stored requested_url (and rules for optional dynamic segments). The returned normalized_host, normalized_scheme, and normalized_path_prefix are auxiliary (display, allowlisting, storage/uniqueness; normalized_path_prefix may be a fingerprint/hash) — they are not a separate path-matching DSL.
Until approved, POST /users/{id}/verification/flows with that return URL may fail with 422.
Sanctum personal access token (access_tokens / partner API settings).
UUID API key stored for the partner user.
2048Request recorded; await approval before using this URL in POST …/verification/flows.
Record of a partner’s return-URL request. Treat requested_url and status as the source of truth for what is approved. The normalized_* fields supplement host/scheme display and internal storage; matching for flows is based on requested_url approval and server rules, not on interpreting normalized_path_prefix alone.
Approval workflow state (e.g. pending admin review vs approved); exact values are implementation-defined.
URL string you registered; this is what the server uses (with trim and dynamic-segment rules) to decide if a partner_return_url in POST …/verification/flows is allowed.
Host parsed from the registered URL (display and bookkeeping). Flow matching is not defined solely by this field.
Scheme parsed from the registered URL; production requires https except in API test mode.
Storage / uniqueness key derived from the registered URL (e.g. hash). Do not use this alone to infer which paths are allowed — use requested_url and approval status.