Find the error message, error number, or result shown in your app, then follow the plain-language steps. Technical details are available for the person who manages your connection.
Match the error message, error number, or result shown in your app. The plain-language description underneath explains what it means.
Problems with API keys, credits, or permission to use an action.
Openmart couldn't recognize the API key connected to your app or workflow. The key may be missing, incomplete, or no longer active.
Send the key in the Authorization: Bearer <your_api_key> request header. Existing integrations may also use X-API-Key. A missing or unknown key returns HTTP 401. You can test the same key with GET /api/v2/credit-balance.
Your team doesn't currently have enough available credits, or your account needs a billing check before the action can finish.
Credit-related failures return HTTP 402. Check the balance with GET /api/v2/credit-balance. Do not automatically retry a 402 response until the account issue is resolved.
Openmart recognized the key, but that key or account isn't allowed to use this action or one of its options.
HTTP 403 means the key was recognized, but the account or key cannot use the requested action or option. Do not retry until access or request options have changed.
Problems with information you send or the records that come back.
Some information is missing, entered in the wrong format, or outside the limit allowed for that action.
HTTP 400 and 422 are not temporary failures. Check the response's error or detail field. Common messages include:
The app reached the server, but the API address or action type did not match an available endpoint.
HTTP 404 is not retryable until the request URL or method changes. Pay special attention to /api/v1/ versus /api/v2/ and to path parameters such as a batch ID or task ID.
The search worked, but Openmart couldn't find records that match all of the information and filters you provided.
Check whether tags replaced the normal search query, whether location filters are too narrow, and whether the response envelope changed because estimate_total=true.
The action worked, but some IDs didn't match a record or the full result set is split across multiple pages.
Business-record endpoints silently omit IDs with no matching record. Search endpoints return a limited page and a cursor for the next page. Reuse the complete cursor from the previous response without editing it.
Problems with long-running jobs, request volume, or temporary outages.
Some Openmart enrichment jobs run in the background. A successful start means the work began, not that the final result is ready.
Poll GET /api/v1/task/batch/:batch_id/status until batch_ready is true. Then retrieve task IDs and final results. Set the HTTP client timeout to at least 60 seconds for batch-submission requests.
Your app or workflow is asking Openmart to do too much at the same time.
HTTP 429 is retryable. Honor the Retry-After header when present and use increasing delays between attempts.
Sign in to Openmart and open API management. If another person manages your connection, ask them to update the key in the app or workflow for you.
No. Never send an API key in email, chat, screenshots, or support requests. Send the exact error message and remove sensitive information from any examples.
Different apps can send the same action in different ways. Tell the person who manages your connection which tool works, which tool fails, and the exact error shown. Some clients or proxies may drop a body from a GET request. Never put an Openmart API key directly in public browser code.
Yes. A background job may have started even if your app stopped waiting for the response. Look for the job ID or batch ID and check its status before starting the same job again.
Openmart may not have every field for every business. Your app should treat a missing value, null, and an empty list as “no value available” unless the endpoint page says otherwise.
Some endpoints return a simple list by default but wrap the list with a total count when estimate_total=true. Compare your setting with the response examples on that endpoint's page.
Error 429, temporary server errors such as 500–504, and network timeouts can usually be tried again after waiting. API key, credit, access, and invalid-information errors must be fixed first.
Some enrichment jobs run in the background. The batch ID is the job ID your app uses to check progress and collect the final results.
Send the information below to your Openmart contact or the person who manages your connection. This helps them investigate without needing your API key.