Marriage muhurta
Ranked marriage dates for a couple, with their ashtakoota score. The wedding place is required.
https://api.vedicapi.co/v1/muhurta/marriageHeavy call: it does more work, so it counts as 5 API calls on your plan. 15 API calls for a range over 90 days, 25 over 180 days. How API calls are counted
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
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
boyobjectrequiredBirth details of the groom. An object with datetime, lat, lon and tz, the same as the birth fields.
Example{"datetime":"1990-10-21T00:45","lat":28.6139,"lon":77.209,"tz":"Asia/Kolkata"}datetimestringrequiredLocal birth time, ISO 8601 with no offset: 1990-10-21T00:45. Seconds are optional.
latnumberrequiredLatitude of the birth place, -90 to 90.
lonnumberrequiredLongitude of the birth place, -180 to 180.
tzstringrequiredIANA zone (Asia/Kolkata) or an offset (+05:30). Past rule changes and daylight saving are handled.
girlobjectrequiredBirth details of the bride. An object with datetime, lat, lon and tz, the same as the birth fields.
Example{"datetime":"1991-12-02T14:40","lat":19.076,"lon":72.8777,"tz":"Asia/Kolkata"}datetimestringrequiredLocal birth time, ISO 8601 with no offset: 1990-10-21T00:45. Seconds are optional.
latnumberrequiredLatitude of the birth place, -90 to 90.
lonnumberrequiredLongitude of the birth place, -180 to 180.
tzstringrequiredIANA zone (Asia/Kolkata) or an offset (+05:30). Past rule changes and daylight saving are handled.
fromstringrequiredStart date, YYYY-MM-DD.
Example2028-01-01tostringrequiredEnd date, up to 366 days from the start.
Example2028-12-31latnumberrequiredLatitude of the wedding place. Or send a place object with lat, lon and tz.
Example28.6139lonnumberrequiredLongitude of the wedding 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.
Exampleenbest_availablebooleanWhen no day passes every check, return the days that miss one weak point, each with the trade-off named. Default true.
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.
ashtakootaobjectThe couple's guna milan score.best_availablebooleanTrue when no time passed every check and these are the best available.boyobjectFirst person's birth as you sent it.computed_msnumberTime the scan took, in ms.day_killedobjectDays ruled out, by reason.days_scannednumberDays checked.fromstringStart of the range.girlobjectSecond person's birth as you sent it.langstringLanguage of names and labels.season_killedobjectDays ruled out by season (Kharmas, combust Jupiter or Venus and so on).text_langstringLanguage of the longer text. English for now.tostringEnd of the range.trade_offsarrayWhat the best-available windows accept, in plain words.valid_daysnumberDays that passed every check.windowsarrayRanked time windows, best first.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_boyinvalid_girlinvalid_placeinvalid_latinvalid_loninvalid_tzinvalid_frominvalid_toinvalid_rangerange_too_longunsupported_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. - 503Codes
busyWhenLong searches are busy. Wait the Retry-After seconds and retry. Nothing is counted. - 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