Daily horoscope
A per-chart daily reading from real panchang, ashtakavarga and tarabala, with a rating, best and avoid times and lucky items. No LLM.
https://api.vedicapi.co/v1/horoscope/dailyAuthentication
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
datetimestringrequiredLocal birth time, ISO 8601 with no offset: 1990-10-21T00:45. Seconds are optional.
Example1990-10-21T00:45latnumberrequiredLatitude of the birth place, -90 to 90.
Example28.6139lonnumberrequiredLongitude of the birth place, -180 to 180.
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.
ExampleenayanamsastringAyanamsa. Lahiri (chitrapaksha) is the only one today and the default. Any other value gets 400 unsupported_ayanamsa.
One oflahiridatestringDay to read, YYYY-MM-DD. Default today at the birth place.
Example2026-11-19
Birth fields are the same on every chart endpoint. Times are local to the place; pass the zone in tz and we handle past rule changes and daylight saving.
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.
avoid_timeobjectWindow to avoid (Rahu kaal).based_onarrayWhat the reading was worked out from.best_timeobjectBest window of the day.birthobjectThe birth you sent, with the UTC offset used at that moment.chandrashtamabooleanTrue when the Moon is 8th from the birth Moon sign.datestringThe date you asked for.langstringLanguage of names and labels.luckyobjectLucky number and colours for the day.methodstringHow the answer is made.moon_house_from_moon_signnumberMoon's house that day from the birth Moon sign.moon_signstringBirth Moon sign.ratingstringDay score as a word.sarvashtakavarga_pointsnumberSarva points of the sign the Moon is in.scorenumberDay score, 0 to 100.starsnumberDay score as 1 to 5 stars.tarastringTara from the birth nakshatra.textstringThe reading, in your lang.transit_moon_signstringMoon's sign on the date.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_datetimeinvalid_latinvalid_loninvalid_tzunsupported_ayanamsainvalid_dateunsupported_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