CORS errors
The browser console reports that a request to SilentShield was blocked by the CORS policy, for example: Access to fetch at 'https://api.silentshield.io/…' from origin 'https://your-site.example' has been blocked by CORS policy. These are the causes and how to fix them.
How SilentShield answers
The API answers requests from any website with the CORS headers the browser needs, error responses such as 403 or 429 included. It never accepts cookies from other websites: the widget identifies itself with your API key.
Causes
The response has no CORS headers
Then the response did not come from the SilentShield API but from something in between: a firewall, a proxy, a browser extension or a gateway error such as 502 or 504. In the Network tab of the developer tools, open the request and check the status and the response headers. A status of (failed) or 0 means the request never reached us.
The request sends cookies
Your code sends the request with credentials: 'include' (fetch) or withCredentials: true (XMLHttpRequest, axios). The API does not allow that for other websites, so the browser discards the response. Remove the option; the API key is all the API needs.
Your own request header
Before such a request the browser asks with an OPTIONS request (preflight) whether the header is allowed. A header that is not in the list below fails this check, and the request is never sent. Send additional data in the request body instead.
A response header cannot be read
Of the response headers, JavaScript in the browser may read only Content-Length. The quota headers (X-Quota-…) are therefore only visible on your server. The browser reports no error here; the value is simply null.
client.js is blocked (403 or ERR_BLOCKED_BY_ORB)
The domain check could not see your site because the request carried neither Origin nor Referer, for example under Referrer-Policy: no-referrer. Add referrerpolicy="origin" to the script tag, as in the snippet from the dashboard.
The verification runs in the browser
/v1/verify belongs on your server. In the browser your API key would be readable by anyone, and a bot could simply skip the check. Send the form with its behavior_nonce field to your server and verify it there.
Allowed request headers
The browser may send these headers to the SilentShield API:
Origin
Content-Type
Accept
Authorization
X-API-Key
X-Page-URL
X-Page-Path
X-Requested-With
Stripe-Signature
X-SilentShield-ZeroPIIIs the domain itself not registered with the key? Domain Mismatch