Troubleshooting
Symptoms, causes and fixes for common problems signing in, publishing APIs and making paid requests.
On this page
Cannot sign in
Symptoms. You return to the sign-in page, or see "We stopped this sign-in request" or "The wallet didn't sign".
- Signing in needs JavaScript. Enable it and reload.
- If you declined the request in your wallet, start again and approve the message. Nothing was sent.
- "We stopped this sign-in request" means the message didn't name this site or your wallet. Reload the page and try again; don't sign messages for other sites.
- Each sign-in message can be signed once and expires after a few minutes. If you waited too long, start again.
- Too many attempts from one address are rate limited for a minute.
See also: Create an account
Cannot connect a wallet
Symptoms. "No Solana wallet was found in this browser", or "This wallet can't sign in here".
- Install a Solana wallet that supports the Wallet Standard and message signing, such as Phantom, Solflare or Backpack, then reload.
- Unlock the wallet and make sure it has a Solana account.
- If the wallet can't sign messages, choose another wallet.
See also: Create an account
API registration fails
Symptoms. Saving the Details step shows an error on a field.
- Slug taken: slugs are unique across NODRA. Choose another.
- Address isn't reachable from the public internet: the upstream URL resolves to a private, local or internal address. Use the public
https://address. - Upstream URL rejected: it must use
https://, contain no username, password,?or#. - Below the minimum price: raise it to at least the minimum shown.
See also: Configure your API
Upstream authentication fails
Symptoms. Test calls fail with "Your API answered with an error" and status 401 or 403.
- Check the header name matches what your API reads.
- For
Authorization, include the scheme, for exampleBearer …. - Replace the key with a freshly copied one; keys are write-only and can't be viewed.
See also: Configure upstream authentication
API test request fails
Symptoms. The Test call panel shows "Test failed".
- Couldn't reach your API: check DNS, that the host is up, and that its TLS certificate is valid.
- Didn't answer in time: test calls wait 10 seconds. Test a faster path.
- Answered with an error: check the status. Redirects (3xx) aren't followed; answers over 1 MiB are refused.
- Doesn't meet the billing rule: the answer was 2xx but empty. Test a path that returns content.
- Rate limited: wait a minute between bursts of tests.
See also: Test your API
API cannot be published
Symptoms. Launch API is disabled, or the launch fails.
- Run a passing test. A key change since the last pass resets it.
- "Attach a wallet before you launch": your account needs a wallet.
- "Your wallet needs USDC once": send any amount of USDC to the wallet, then check again.
- "The price is too low for the fee rules": raise the price.
- Too many launch attempts in 24 hours are refused; try again later.
See also: Publish your API
API is not appearing in the directory
Symptoms. Your API is missing from /apis.
- Only live APIs appear. Check its status in My APIs: drafts, launching and paused APIs are hidden.
- Check Show in the public directory is on.
- Directory responses may be cached for up to 30 seconds. Usage numbers take a few minutes to appear.
- Search matches the name, description and slug; try the exact slug.
See also: Manage your APIs
HTTP 402 received
Symptoms. Every call to a gateway URL returns 402.
- That's expected for a call without a
PAYMENT-SIGNATUREheader: read the quote and pay it. - If you sent a payment, the
errorin the body and header says why it was rejected; a fresh quote is attached. - Make sure you send
PAYMENT-SIGNATURE, not the version 1 headerX-PAYMENT.
See also: Understand an HTTP 402 response
Payment authorization rejected
Symptoms. 400 invalid_payment_header, 400 invalid_payment, or a 402 with a reason after paying.
invalid_payment_header: the header must be base64 JSON withaccepted.extra.memoandpayload.transaction.unknown_quote: the memo doesn't match a quote. Copyextra.memoexactly.quote_already_used: each quote pays for one call. Ask for a new quote.payment_expired: pay within 60 seconds of the quote.exposure_cap_exceeded: your wallet has too much unsettled. Wait for earlier payments to settle.policy_*codes: the transaction includes something not allowed, such as an address lookup table or another program. See Authorization rules.
See also: Error handling
Payment verification fails
Symptoms. A 402 whose reason is an x402 verification code, or 503 payment_verification_unavailable.
- Pay exactly
amountofassetto the associated token account ofpayTo, with 6 decimals. - Use
extra.feePayeras fee payer, and don't sign for it or reference it in any instruction. - Make sure your USDC token account holds enough for the payment.
- Use a recent blockhash; stale transactions fail simulation.
payment_verification_unavailableis a temporary outage. Resend the same payment afterRetry-After.
See also: Verification and settlement
Upstream request times out
Symptoms. 504 with {"error":"upstream_failed","reason":"timeout"}.
- The provider didn't answer within 20 seconds. You weren't charged.
- Retry later with a new quote, or choose another API.
- Providers: speed up the endpoint; check its median latency on your directory page.
See also: Failed requests
API request returns an error
Symptoms. 502 upstream_failed with a reason and upstreamStatus.
- The provider answered with an error or an unbillable answer, so its body is withheld and you weren't charged.
status_4xxusually means a wrong path, parameter or body. Check the API's description.status_5xxis the provider's own failure. Try later.empty_body: the provider answered 2xx with no content.
See also: Failed requests