Fix payment, order, and API access problems
Use the actual payment status and error code to find your next step and the right support contact.
On this page
A paid order is missing
- Check the right area: APIs are in “Purchased products”, services are in “Service orders”, and service payments awaiting funds are in “Service payments”.
- Check the account: use the original buyer account for a signed-in purchase, or the checkout contact email for a guest service purchase. Verify that email or use the sign-in link sent to it.
- Open “Service payments” to check status. For a bank transfer, use “Open Stripe bank transfer instructions”; for an unfinished checkout, use “Continue checkout”. Returning to the product page alone does not confirm payment.
- If payment is confirmed but the purchase is still missing, collect the product link, payment or checkout ID, payment time, and account email, then contact platform support.
Look up the API error code
These are stable errors returned by the Invokora gateway. The same HTTP status may also come from the merchant’s API, so inspect the response code and body together.
| HTTP / code | Meaning | Next step |
|---|---|---|
| 401 · invalid_api_key | The key is invalid or the current subscription cannot authenticate. | Check X-Invokora-Key, the product base URL, and subscription status. Rotate a lost key in the workspace. |
| 403 · endpoint_not_allowed | The plan does not permit this endpoint. | Check the allowed endpoints and HTTP method in the product detail. Change plans or contact the merchant for more access. |
| 429 · rate_limit_exceeded | Requests are arriving too quickly. | Reduce concurrency and request frequency. Wait according to the plan’s rate limit before retrying. |
| 429 · object_quota_exceeded | A metering object has reached its allowance. | Check the affected object and reset time under plan usage. Wait for reset or choose a suitable plan. |
| 402 · bandwidth_payment_required | More bandwidth requires a payment method. | Check bandwidth in the API detail and follow the steps to enable paid excess bandwidth. |
| 413 · request_too_large | The request body exceeds the limit. | Reduce the file or body size and check endpoint limits. |
| 502 · origin_unavailable / origin_response_too_large / origin_metering_invalid / transformation_failed | The API service or merchant response configuration could not complete the request. | Save the error code, time, and requestId, and ask the merchant to check the API. Contact the platform too if the issue persists. |
Free trial is unavailable or approval is pending
If “Free trial” is missing, the merchant usually does not currently offer an eligible free BASIC plan. You can read the public documentation, choose another available plan, or ask the merchant.
“Waiting for merchant approval” requires a merchant decision. Return to the product and choose “Refresh status”. After approval, you still need to subscribe. Ask the merchant for a valid entry if a private invitation has expired.
If you already subscribe but the product-page console asks for a key, paste your saved key. Alternatively, open the buyer workspace and use its console with your signed-in session.
Contact the right support team
| Issue | Contact | Include |
|---|---|---|
| API parameters, response data, plan permissions, or approval | The product’s merchant | Product link, endpoint and HTTP method, time, error code, and requestId if available. |
| Service requirements, progress, delivery, or revisions | “Messages” in the service order | Order ID, the specific delivery issue, and relevant screenshots or files. |
| Account, payment records, API invoices, or platform errors | support@invokora.com | Account email, product link, order or invoice ID, and time of the issue. |