vedicAPI

Inauspicious times

Rahu kaal, Yamaganda, Gulika, Durmuhurta and Varjyam for a date and place, with Abhijit as the good window.

POST/panchang/inauspicious
Counts as 1 API call

Authentication

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

  • Authorization
    Requiredrequired
    DescriptionBearer followed by your API key.
  • X-End-User
    Requiredoptional
    DescriptionYour own id for the person the call is for, up to 64 characters. Shows in Request logs. End-user tags
  • Content-Type
    Requiredrequired
    Descriptionapplication/json

Body parameters

  • datestringrequired

    Date, YYYY-MM-DD.

    Example 2026-11-19
  • latnumberrequired

    Latitude of the place.

    Example 28.6139
  • lonnumberrequired

    Longitude of the place.

    Example 77.209
  • tzstringrequired

    IANA zone (Asia/Kolkata) or an offset (+05:30). Past rule changes and daylight saving are handled.

    Example Asia/Kolkata
  • langstring

    Language of names and labels: en, hi, mr, bn, te, gu, ta, pa, kn, ml, en_IN (Hinglish) or de. Default en.

    Example en

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 below 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

  • 400
    Codesinvalid_jsoninvalid_dateinvalid_latinvalid_loninvalid_tzunsupported_langinvalid_end_user
    WhenA field is missing or invalid. The message names the field.
  • 401
    Codesmissing_keyunknown_key
    WhenNo key, or the key is wrong, revoked or past its rotation window.
  • 403
    Codesnot_allowed
    WhenThe key has an allow list and this call came from another IP or domain.
  • 404
    Codesno_such_endpoint
    WhenWrong path or method.
  • 429
    Codesrate_limitedmonthly_limitspend_cap
    WhenOver a limit. Wait the Retry-After seconds before trying again.
  • 502
    Codesengine_unavailableengine_error
    WhenOur 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