Muhurta purposes
The 23 purposes muhurta/find accepts, with their labels and categories. Free to call.
GET
Free to callhttps://api.vedicapi.co/v1/muhurta/purposesAuthentication
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 tags
Query parameters
This endpoint takes no parameters.
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.
alsoarrayEndpoints for purposes with their own rules.purposesarrayEach purpose: key, label, category and whether it needs a partner.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_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