Worship · 1 endpoint
Qibla Direction
The bearing to the Kaaba from any point, as a true great-circle heading — not the straight line a flat map suggests.
- Status
- Operational
- Price
- 1 credit / request
- Rate limit
- 300 / 60s
- Cache
- None
- Requests
- 0
Endpoint
How to call it
GET/v1/qibla
Code
Request — cURL
v1
curl https://api.diraz.co.id/v1/qibla \
-H "Authorization: Bearer drz_live_…"For AI agents
Callable through the MCP server with the same key:
call_api {"endpoint":"qibla","params":{"lat":"-6.2088","lon":"106.8456"}}Parameters
- latnumber · required
- Latitude.
- lonnumber · required
- Longitude.
Example response
200 OK
JSON
{
"data": {
"coordinates": { "latitude": -6.2088, "longitude": 106.8456 },
"bearing": 295.15,
"compass": "WNW",
"distance_km": 7896.4
},
"meta": {
"request_id": "req_7Q2fK4mZ"
}
}- bearing
- Degrees clockwise from true north.
- compass
- The same bearing as a sixteen-point compass name.
- distance_km
- Great-circle distance to the Kaaba.
Errors
When something goes wrong
Every failure carries a stable machine-readable code and the same meta.request_id a success carries — quote it and we can find your request. Errors are never billed.
401 Unauthorized
JSON
{
"error": {
"code": "UNAUTHORIZED",
"message": "The API key is invalid, expired, or revoked."
},
"meta": {
"request_id": "req_7Q2fK4mZ"
}
}- UNAUTHORIZEDHTTP 401
- Missing, malformed, expired, or revoked API key.
- FORBIDDENHTTP 403
- The key is valid but lacks the scope this product needs.
- VALIDATION_ERRORHTTP 422
- A query parameter is the wrong type or out of range.
- RATE_LIMITEDHTTP 429
- Rate limit exhausted. `Retry-After` says how long to wait.
- SERVICE_UNAVAILABLEHTTP 503
- No data recent enough to serve. Carries `Retry-After`, and is never billed.
Health
Is it up?
- Qibla Direction
1/1 passing