origin-not-allowed
| Status | 403 |
| Title | Origin not allowed |
| Code | origin-not-allowed |
| Type | https://docs.satellitedata.net/problems/origin-not-allowed |
Coming later This problem belongs to the MCP endpoint and website sessions, which lean v1 does not have yet.
Meaning
Section titled “Meaning”The request’s Origin header is not on the allow-list for this route.
Likely causes
Section titled “Likely causes”- A browser page calling
/mcpfrom an origin not on its allow-list; the MCP transport requires origin checks to block DNS rebinding. - An account route called with a website session from a site other than satellitedata.net.
Call /mcp from a server or an allowed origin, and use account routes from the website.
Example
Section titled “Example”{ "type": "https://docs.satellitedata.net/problems/origin-not-allowed", "title": "Origin not allowed", "status": 403, "detail": "The request's `Origin` header is not on the allow-list for this route.", "instance": "/v1/...", "code": "origin-not-allowed", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D"}The detail above is a placeholder; the real one names the value at fault.
See Errors for the members every problem carries.