Common Errors

NovaDataHub APIs use HTTP status codes and structured JSON error responses so applications can handle failures in a predictable way.

Key points

Authentication errors indicate missing or invalid keys.
Quota and plan errors indicate access or usage limits.
Timeout and data-source errors should be handled with retry or fallback logic.

Common errors

401 invalid_key
402 no_active_plan or quota_exceeded
429 rate_limited
500 data_source_failed

Reference details

Parameters, response shape, and operational notes

Parameter notes

401 usually means a missing or invalid API key.
402 errors often indicate plan or quota state rather than malformed requests.
429 should be treated as a throttle signal and retried carefully.

Response highlights

Error payloads are intentionally compact so they can be logged and indexed easily.
The most useful fields to store are status code, error code, and request context.
Different endpoints share common error semantics to simplify client code.

Operational notes

Classify retryable versus non-retryable errors in your client.
Log request identifiers and key parameters for easier support debugging.
Surface quota and rate-limit errors clearly in dashboards or alerting.

Implementation checklist

Map each error code to a clear operator or user-facing action.
Keep a sample of raw error payloads in logs so debugging stays grounded in real responses.
Avoid treating all 4xx codes the same, especially when quota and auth have different remedies.

Code examples

Visible integration examples

curl

curl -i -H "x-api-key: INVALID" "https://novadatahub.com/search?q=test&sync=true"

Python

import requests
resp = requests.get('https://novadatahub.com/search', params={'q': 'test', 'sync': 'true'}, headers={'x-api-key': 'INVALID'})
print(resp.status_code, resp.text)

C# HttpClient

using var http = new HttpClient();
http.DefaultRequestHeaders.Add("x-api-key", "INVALID");
var resp = await http.GetAsync("https://novadatahub.com/search?q=test&sync=true");
Console.WriteLine((int)resp.StatusCode);

Sample JSON response

{
  "ok": false,
  "error": "invalid_key"
}

Related resources

Move from reference docs into the next relevant workflow

Rate-limit handling

Read the queueing, retry, and backoff guide for calmer handling of 429 responses in recurring jobs.

Open guide

Quota exceeded handling

Separate exhausted-plan behavior from retry logic so operator actions and user messaging stay clearer.

Open guide

Async job polling strategy

Use the async workflow guide when timeouts and intermediate states need different handling than hard failures.

Open guide

Google SERP API docs

Review a concrete endpoint that returns auth, quota, rate-limit, and timeout responses in a developer-friendly JSON format.

Open docs

Create account View pricing Google SERP API page

Continue with connected pages

Rate limits docs

Open the related NovaDataHub page for deeper documentation, comparisons, or implementation guidance.

Open page

Rate-limit handling guide

Open the related NovaDataHub page for deeper documentation, comparisons, or implementation guidance.

Open page

Quota exceeded guide

Open the related NovaDataHub page for deeper documentation, comparisons, or implementation guidance.

Open page

Authentication docs

Open the related NovaDataHub page for deeper documentation, comparisons, or implementation guidance.

Open page