Make your first API call from the dashboard

Find or create a key

After signup, the dashboard can use the newly issued key kept in this browser tab for the first-call playground. You can also create or copy a key from API Keys and choose Use copied API key on the dashboard. A copied key is validated before it is placed into the example snippets.

Run the health check

The dashboard offers cURL, Python, and Node.js examples for the authenticatedGET /api/v1/health endpoint. The guide snippets below use an environment variable so the key stays out of source files.

cURL

export KHALEEJI_API_KEY="your_api_key_here"
 
curl -H "Authorization: Bearer $KHALEEJI_API_KEY" \
  "https://khaleejiapi.dev/api/v1/health"

Python

import os
import requests
 
response = requests.get(
    "https://khaleejiapi.dev/api/v1/health",
    headers={"Authorization": f"Bearer {os.environ['KHALEEJI_API_KEY']}"},
    timeout=15,
)
print(response.status_code)
print(response.json())

Node.js

const response = await fetch("https://khaleejiapi.dev/api/v1/health", {
  headers: { Authorization: "Bearer " + process.env.KHALEEJI_API_KEY },
});
console.log(response.status, await response.json());

Set KHALEEJI_API_KEY in your local shell before running these examples. The health endpoint requires a valid API key; load-balancer probes use the separate public /api/v1/ping endpoint.

Verify the key and troubleshoot

Select Run live key check in the dashboard to verify the saved key. The playground reports the result in place; it does not expose the saved key.

• 401 Unauthorized: check that the full key is current and sent as Authorization: Bearer <key>.
• 403 Forbidden: read the response message and confirm the key or account is permitted to use that endpoint.
• 429 Too Many Requests: respect the response's rate-limit guidance and retry after the indicated reset.
• No full key shown: keys are intentionally masked after creation; create a replacement if you no longer have the original.