Inauspicious times
Rahu kaal, Yamaganda, Gulika, Durmuhurta and Varjyam for a date and place, with Abhijit as the good window.
https://api.vedicapi.co/v1/panchang/inauspiciousAuthentication
Send your API key as a Bearer token. Keys start with sk_live_. Keep keys on your server. More on keys
Authorization: Bearer $VEDICAPI_KEY
Headers
AuthorizationRequiredrequiredDescriptionBearer followed by your API key.X-End-UserRequiredoptionalDescriptionYour own id for the person the call is for, up to 64 characters. Shows in Request logs. End-user tagsContent-TypeRequiredrequiredDescriptionapplication/json
Body parameters
datestringrequiredDate, YYYY-MM-DD.
Example2026-11-19latnumberrequiredLatitude of the place.
Example28.6139lonnumberrequiredLongitude of the place.
Example77.209tzstringrequiredIANA zone (Asia/Kolkata) or an offset (+05:30). Past rule changes and daylight saving are handled.
ExampleAsia/KolkatalangstringLanguage of names and labels: en, hi, mr, bn, te, gu, ta, pa, kn, ml, en_IN (Hinglish) or de. Default en.
Exampleen
Response
JSON with 200 OK. Every answer carries units (how many API calls this request counts as) and request_id, and the same values in the X-Units and X-Request-Id headers. The example belowon the right is the real answer to the request shown.
abhijitobjectAbhijit muhurta, the good window around noon.datestringThe date you asked for.durmuhurtaarrayDurmuhurta windows (one or two a day).gulikaobjectGulika kaal start and end.langstringLanguage of names and labels.notestringA short note on how to read the answer.placeobjectThe place you sent, with the UTC offset used.rahu_kaalobjectRahu kaal start and end.sunrisestringLocal sunrise, HH:MM:SS.sunsetstringLocal sunset, HH:MM:SS.varastringWeekday.varjyamobjectVarjyam window, or null on days without one.yamagandaobjectYamaganda start and end.unitsnumberHow many API calls this request counts as: 1, or 5 for a heavy call; 0 for errors and free endpoints.request_idstringId of this call. Search it in Request logs. Also sent as the X-Request-Id header.
Errors
- 400Codes
invalid_jsoninvalid_dateinvalid_latinvalid_loninvalid_tzunsupported_langinvalid_end_userWhenA field is missing or invalid. The message names the field. - 401Codes
missing_keyunknown_keyWhenNo key, or the key is wrong, revoked or past its rotation window. - 403Codes
not_allowedWhenThe key has an allow list and this call came from another IP or domain. - 404Codes
no_such_endpointWhenWrong path or method. - 429Codes
rate_limitedmonthly_limitspend_capWhenOver a limit. Wait the Retry-After seconds before trying again. - 502Codes
engine_unavailableengine_errorWhenOur engine could not answer. Retry with backoff.
Errors are never charged. Every error has one shape: { "error": "<message>", "code": "<code>", "request_id": "req_..." }. Errors and limits