About HTTP Request
Why a browser cannot call every API
A page may only read a response from a server that opted in, by sending an Access-Control-Allow-Origin header. This is CORS, and it is the browser protecting other sites from the page you are on — not the API refusing you.
The request often reaches the server anyway; the browser just will not hand you the reply. That is why a call that works in curl can fail here, and why the error is the unhelpful Failed to fetch.
Two ways through: use an endpoint that allows browsers, or point the block at a proxy you run, which adds the header on the way back. Settings → Network.
Nothing is sent until you press Send
Typing a URL costs nothing. Re-opening the bode replays the last response rather than calling again, and opening a bode someone shared never fires their requests for them.
That last part matters for anything with side effects. A shared bode containing a POST is safe to open.
What gets sent with the request
What you type, and nothing else. Cookies are not attached, and no browser credentials ride along.
A token in the Authorization field is held for the session only: it is never written into the bode, a saved version, or a share link. Send someone a bode and they use their own.
Common questions
- Why do I get "failed to fetch" when the URL works in my browser?
- Almost always CORS. Opening a URL directly is not a cross-origin request, so the rule does not apply; a page calling it is, so it does. Use an API that allows browsers, or set a proxy in Settings → Network.
- Can I point it at my own proxy?
- Yes, and that is the intended path. Settings → Network takes a URL with a {url} placeholder, or a prefix. It stays on your device and is never part of a shared bode.
- Is my API token saved anywhere?
- No. The Authorization field is session-only — not in the autosave, not in a saved version, not in a share link. A refresh clears it.