a month ago
I’m on the Hobby plan and need help with a read-only request to the Railway API.
At 2026-10-07 05:19:09 UTC, the response was HTTP 403, Content-Type text/plain, Server cloudflare, with error code 1010. CF-Ray: a46a7301a852d41e-KIX.
An earlier request using the same existing authentication source succeeded. One diagnostic repeat of the failing read request, with the same request and headers, returned 1010 again. No mutation was sent during these failed requests.
I have stopped API requests and have not changed the User-Agent, credentials, or route to get around the block. What is the supported way to resolve this, and are there documented client requirements for authenticated API requests?
I can provide additional non-sensitive diagnostic details through an appropriate channel. Thank you.
5 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We don't require a specific User-Agent or any browser-like signature for API requests. Clients should send queries to https://backboard.railway.com/graphql/v2 as a POST with Content-Type: application/json and the token in the right header: Authorization: Bearer <token> for account or workspace tokens, or Project-Access-Token for project tokens. GET requests to that endpoint are blocked at the edge, even for read-only queries.
Hobby workspaces can make up to 1,000 API requests per hour per token. These limits are tracked by token, not by client signature.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Thank you for the guidance. We checked the saved request code for the failure at 2026-10-07 05:19 UTC. It explicitly used POST to https://backboard.railway.com/graphql/v2, Content-Type: application/json, and the Authorization: Bearer header. It was a read-only GraphQL query, and redirects were disabled.
The response was still HTTP 403 with Cloudflare error 1010 and a non-JSON body. The CF-Ray was a46a7301a852d41e-KIX. We have not changed the User-Agent, credentials, or route to bypass the rejection, and have not retried the API request since that diagnostic.
Could you help clarify why this POST request was rejected, or advise the supported next diagnostic step for these conditions?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The request you describe matches what our public API expects: a POST to https://backboard.railway.com/graphql/v2 with Content-Type: application/json and an Authorization: Bearer header. Its format was not the cause.
A plain-text 403 with Cloudflare error 1010 comes from the security layer in front of the API. The request was rejected there and never reached the API, so it was not a token, permission, or API rate-limit failure. Since an earlier request with the same credentials succeeded, your account and token are not the problem either.
The CF-Ray you shared, a46a7301a852d41e-KIX, is what identifies the edge rule that fired. To help pin it down, please share the client and library you used and their versions, the exact User-Agent string sent, and whether the request came from a home or office connection, a cloud or datacenter host, or a VPN or proxy. Holding off on retries in the meantime is the right call.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Thank you. We are keeping API retries paused.
From the retained script and diagnostic records, the client was a custom Python script using the standard-library urllib.request, executed locally on macOS. The Python version used for the failed request was not recorded.
The script did not explicitly set a User-Agent. Standard urllib.request behavior would use Python-urllib/<Python major.minor>, but we did not capture the outgoing headers, so we cannot confirm the exact value sent. Our current audit environment is Python 3.12.12; that does not establish the version used at the time.
The connection category was not recorded. We cannot confirm whether it was a home/office connection or whether a VPN or proxy was involved. Local execution on a Mac does not establish the network category. The script did not explicitly disable urllib's default proxy handling.
The failed request was at 2026-10-07 05:19:09 UTC, with CF-Ray a46a7301a852d41e-KIX, returning HTTP 403 and error 1010. Could you investigate that event using the timestamp and CF-Ray? We will avoid further requests while this is being investigated.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Thanks, that covers everything we need from your side. The CF-Ray and timestamp you shared identify the exact event at our edge, so there is nothing more to capture or reconstruct, and you don't need to change your token or credentials.
The rejection happened in the security layer in front of the API, before the request reached it, so nothing about it shows up on your account and no data was read or changed. Keeping retries paused is the right call for now.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago