Vedic Phala API

Vedic Phala Matching

• Guṇa Milāna, the 36-point Aṣṭakūṭa, under two conventions: Phala (the classical tables) and Drik (the same kūṭa points as drikpanchang.com). Both scores come back on every call.
• Rapport for any relationship that is not a marriage, from the three kūṭas that do not depend on who is the bride or groom.
• The ten poruthams of the southern tradition.
• Batch scoring: one seeker against up to 1,000 stored profiles, best first. A profile is turned into a card once and matched by its card after that.
• A full report: both charts' doṣas with their cancellations, and the marriage periods ahead.
• Names in eighteen languages. Works without a birth time, and says when a score depends on it.

Phala Ephemeris

• Positions of the Sun, Moon, planets to Pluto and the lunar nodes, sidereal (Lahiri) or tropical.
• A birth chart with the ascendant, nakṣatra and pāda.
• The pañcāṅga for a place and day, with the weekday changing at local sunrise.
• Eclipses, solar and lunar, with local contact times.
• From 6000 BCE to 3000 CE, fitted to NASA JPL's DE441: apparent positions agree with JPL Horizons to about 0.1″. How the calculations are checked →

The SDK: the ephemeris inside your own product

The same engine and data files the app runs, as a library you ship in your product: the JVM (any server), Android and the iPhone, from one codebase. No network, no per-call meter, the same numbers as the API. One licence covers one product, on every platform it runs on.

• The package: the library as a JVM jar and an Android AAR, the 31 ephemeris files (6070 BCE to 3006 CE, 38 MB) and the bright-star catalogue, the integration guide, and a manifest with every file's checksum. The iPhone framework on request.
• The licence is a signed file the library checks when it opens the data, offline. An annual licence stops at the printed date and a renewal is a new file; an outright licence has no date.
• Thirty days of integration support by email come with each licence. You license the release you download, as it is; new releases, if any, are offered at our discretion.
• Want to buy it outright? Write to us with your product and we will quote a price.
• The Matching engine (Guṇa Milāna and the ten poruthams) is in the same library and needs no second licence inside your one product.

Ask for a licence

We reply with an invoice or a payment link, then the licence file and a download link. The licence agreement →

Paying by invoice

A business that would rather pay a monthly invoice in US dollars by bank transfer than subscribe by card can ask for one. This is also the simplest route for companies in India, where recurring card charges to an overseas merchant often fail.

Try it free

A trial key carries a small daily allowance, enough to build against every endpoint. Tell us who you are and what you are building, and we reply with a key.

How units are counted

A request refused for bad input costs nothing. Every answer says what it cost and what is left in the day.

Documentation

The developer guide walks through keys, units, matching in three calls and what to know before showing a score. The reference lists every field of every call, drawn from the API's own OpenAPI document, which tools such as Postman read directly.

A first call, with your key:

curl -s https://match.api.vedicphala.com/v1/match/card \
  -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' \
  -d '{"person":{"date":"1990-02-28","time":"23:30",
       "latitude":28.6139,"longitude":77.209,"zone":"Asia/Kolkata"}}'

Privacy and fair use

Birth details are used to answer the call and are never logged or stored; the API keeps nothing between calls. Scores describe a traditional practice and are not a prediction or advice, and a platform that shows them must say so. Questions about a plan, a bill or a key go to support@vedicphala.com.