String docs
Fetch

Access control & KYC

How restricted destinations and request patterns are gated.

Some destinations and request patterns require approval before use. This may include social and professional networks, search engines, community forums, messaging services, video and live-streaming platforms, employment and recruiting sites, dating services, and adult-content platforms.

Both access-control cases return 403 Forbidden with a reason that says which one applies:

CaseStatusBody fieldExample
Destination domain not enabled for your organization403 ForbiddenreasonAny method against an unapproved hostname
Reachable URL but the chosen method requires KYC for that path403 ForbiddenreasonPOST to a restricted endpoint

403 — domain not enabled

{ "reason": "Requests to example.com are not allowed. Contact [email protected] for access." }

403 — method requires KYC for the path

{ "reason": "POST requests to this path are blocked pending KYC. Email [email protected] with your request to get access." }

Requesting access

In either case, email [email protected] with your use case to request access for your organization. Path blocks can be lifted per organization — including persisted-login flows that need POST access to sign-in paths across every destination — so say which paths you need rather than working around the 403.

In-session navigation

Access control isn't only applied to the initial URL. When you drive a page with browser actions or the CDP browser, every in-session navigation — clicks, redirects, and script-driven navigations — is re-checked against the same rules.