Key points
- Each enabled API has its own service key.
- A valid key for one service should not be assumed to work for a different API family.
- Per-service keys make environment scoping, rotation, and access isolation easier to manage.
Updated on 2026-05-12
NovaDataHub Engineering
Developer docs
Service Key Workflow
NovaDataHub uses separate keys per enabled service so access stays isolated between SERP, reviews, cricket, and FX workflows. This page explains how to think about that model during onboarding, environment setup, debugging, and production rollout.
Common errors
- 401 invalid_key
- 403 service_not_enabled
- 429 rate_limited
Reference details
Parameters, response shape, and operational notes
Parameter notes
- Decide which service key belongs to which application component before rollout.
- Keep service names explicit in configuration rather than using one generic API key variable for every workflow.
- Match the endpoint family and the service key together when debugging auth failures.
Response highlights
- The same x-api-key header pattern is reused across API families, but the underlying service key is different.
- A working curl request should always confirm both the correct header name and the correct service-specific secret.
- Production systems usually benefit from storing one config value per service, not one shared secret for everything.
Operational notes
- Name secrets clearly so operators can tell SERP, reviews, cricket, and FX credentials apart.
- Rotate only the affected service key when one integration path changes or is compromised.
- Keep dashboard, staging, and production environments from drifting into mixed-key usage.
Implementation checklist
- Create one environment variable or secret per enabled service.
- Validate each key against the matching endpoint family before deployment.
- Do not reuse one service key across unrelated workflow code paths just because the header name is the same.
- Document which background jobs, apps, or workers depend on which service key so rotations stay safe.
Code examples
Visible integration examples
curl
curl -s -H "x-api-key: YOUR_SERP_KEY" "https://novadatahub.com/search?q=service+key+workflow&gl=us&hl=en&sync=true"Python
import os
import requests
serp_key = os.environ['NOVADATAHUB_SERP_KEY']
resp = requests.get('https://novadatahub.com/search', params={'q': 'service key workflow', 'gl': 'us', 'hl': 'en', 'sync': 'true'}, headers={'x-api-key': serp_key}, timeout=60)
print(resp.status_code)C# HttpClient
using var http = new HttpClient();
http.DefaultRequestHeaders.Add("x-api-key", Environment.GetEnvironmentVariable("NOVADATAHUB_SERP_KEY"));
var response = await http.GetAsync("https://novadatahub.com/search?q=service+key+workflow&gl=us&hl=en&sync=true");
Console.WriteLine((int)response.StatusCode);Sample JSON response
{
"ok": true,
"status": "completed",
"result": {
"query": "service key workflow",
"organic": [{ "position": 1, "title": "Example service key result" }]
}
}Related resources
Move from reference docs into the next relevant workflow
Google SERP API docs
Start with the most complete public endpoint reference when validating header, key, and request construction patterns.
Open docsService key workflow
Keep per-service access clean across SERP, reviews, cricket, and FX integrations.
Open docsAPI playground workflow
Use the playground to confirm a service key and request shape before debugging larger integration code.
Open docsInvalid API key debugging
Use the troubleshooting guide when the right service key still appears to fail in code or in production environments.
Open guidePython integration
See a compact example of how authenticated NovaDataHub requests look in Python.
Open Python docsC# integration
See how to attach x-api-key with HttpClient and consume JSON responses in .NET services.
Open C# docsRelated links