ExactPredictions V2

Exact Predictions V2 Astrology API

Current public API generation: V2. Calculate a horoscope with your own API key, then reuse that JSON where another endpoint requires it.

Keep your API key private. API keys are secrets. Do not put them in browser JavaScript, Git, or public pages. Store the key on a server or in an environment variable. This page does not save the key after you close or refresh it. Swagger UI adds Bearer for you. Paste the key alone into Authorize. Customer keys use the epv11_ prefix, for example epv11_your_generated_key.
Back to Quick Start Download sample horoscope JSON Download marriage-matching sample

Quick Start

  1. Create an Exact Predictions account.
  2. Subscribe to an API-enabled plan. Free does not include external API key creation. Pro and Pro+ do.
  3. Sign in and open API Access.
  4. Create your API key and copy it when it is shown. The secret is not shown again.
  5. Click Authorize and paste the key only. Do not type Bearer.
  6. Open POST /v2/horoscope, click Try it out, then Execute.
  7. Use the returned horoscope JSON with other V2 APIs that require it.

API credits are shared by the Exact Predictions App and external V2 calls on the same account. Pro includes 10,000 shared API credits per month. Pro+ includes 30,000. Prices are on the plan page.

How to Test the ExactPredictions API

An API endpoint is one specific job the server can do, such as “create a horoscope” or “calculate Shadbala”.

GET reads information using values in the URL. POST sends a JSON body, which is the usual method for these calculation endpoints.

Authorize

  1. Create your own API key at API Access. There is no shared test key.
  2. Click Authorize at the top of the endpoint list.
  3. Paste the key into the Bearer field. Do not include the word Bearer — Swagger adds that for you.
  4. Click Authorize, then Close.
  5. When you finish, open Authorize again and click Logout if you are on a shared computer.

Run an endpoint

  1. Click a group name, then the endpoint row, to expand it.
  2. Click Try it out.
  3. Fill query fields, or paste JSON into the request body. JSON must use double quotes.
  4. Click Execute.
  5. Read the request URL, the response code, and the response body.
  6. Use Copy JSON or Download JSON under the response, or copy from the code block.

Reuse horoscope JSON

  1. Run POST /v2/horoscope first.
  2. Copy the full response JSON, not one nested section.
  3. Open another compatible endpoint, click Try it out, paste the JSON, then Execute.
  4. You can also download the standard sample horoscope JSON and paste that instead.
  5. The editor may pretty-print a large JSON body. Execute still sends a compact copy, so testing matches the live app.

A successful calculation returns HTTP 200 and a JSON object with "status": "success".

Testing Tips

  • Start with the main horoscope endpoint.
  • Always use valid JSON with double quotation marks.
  • Do not remove required JSON fields.
  • Dates and times must match the documented format.
  • Latitude, longitude, timezone, ayanamsa, language, and node type must use supported values.
  • Copy the complete horoscope JSON, not only one section.
  • 200 — success.
  • 400 or 422 — invalid or missing input.
  • 401 — missing or invalid API key.
  • 403 API_ACCESS_NOT_ELIGIBLE — this account cannot use an external API key.
  • 404 — incorrect or unavailable endpoint.
  • 413 — the JSON body is larger than 2 MB.
  • 429 API_CREDIT_QUOTA_EXCEEDED — the shared API-credit allowance is used up. Do not keep retrying.
  • 429 RATE_LIMITED — short-window or concurrency limit. Retry after the stated delay.
  • 500 — server error; please report it.
  • Do not expose API keys when sharing screenshots.
  • Format large JSON responses for easier reading.

How to report a problem

Contact support with the endpoint path, the HTTP status, and meta.request_id. Do not send your API key.