Key points
- Send the API key in the x-api-key header.
- Each enabled API has its own key.
- Unauthorized requests return an error response rather than HTML.
Updated on 2026-05-12
NovaDataHub Engineering
Developer docs
Authentication
NovaDataHub uses per-service API keys sent through the x-api-key header. After enabling a service, the key can be tested in the API playground or used directly in code.
Common errors
- 401 invalid_key
- 403 forbidden for unauthorized private access
Reference details
Parameters, response shape, and operational notes
Parameter notes
- Header: x-api-key is required on protected endpoints.
- Per-service keys keep access isolated between SERP, reviews, cricket, and FX APIs.
- Keep API keys server-side whenever possible instead of exposing them in public client code.
Response highlights
- Protected endpoints return JSON error payloads rather than HTML redirects.
- Public diagnostics such as /api/public/ping can help you verify connectivity patterns.
- The same authentication pattern applies across the API families.
Operational notes
- Rotate compromised keys immediately from the dashboard.
- Treat missing-key, invalid-key, and forbidden responses differently in logs.
- Use one integration helper so auth behavior stays consistent across your services.
Implementation checklist
- Confirm the key exists and belongs to the correct enabled service.
- Test the same header pattern in curl, Python, and C# before moving into production code.
- Store secrets in environment variables or secure config providers instead of source files.
Code examples
Visible integration examples
curl
curl -s -H "x-api-key: YOUR_API_KEY" "https://novadatahub.com/api/public/ping"Python
import requests
resp = requests.get('https://novadatahub.com/api/public/ping', headers={'x-api-key': 'YOUR_API_KEY'})
print(resp.json())C# HttpClient
using var http = new HttpClient();
http.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var body = await http.GetStringAsync("https://novadatahub.com/api/public/ping");
Console.WriteLine(body);Sample JSON response
{
"status": "ok",
"time": "2026-05-11T00:00:00Z"
}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