Contact
Last updated
One address, read by the people who build the API. Include the detail below and you will usually get a useful answer first time.
We aim to reply within 3 working days.
What to include
A call that failed. The endpoint, the exact request body, and the response you got. The request body matters more than the description of it — most reports turn out to be one field.
A billing question. The payment reference from your receipt, and the date. Do not send card details; we cannot see them and would not need them.
A wrong result. The birth details you used, what the API returned, and what you expected with the source you are comparing against. Different software uses different ayanamsa and house systems, so the comparison point is the useful part.
Never send us an API key. We do not need it and cannot read it back — keys are stored hashed. Send the key prefix (the first few characters) if you need to identify one.
Security issues
Email the same address with “security” in the subject and we will prioritise it. Please give us a reasonable chance to fix something before disclosing it publicly.
Before you write
The documentation lists every request field with its allowed values and a verified example, and the playground will run your exact request against a live server. Between them they answer most of what we get asked.
Postal address
Email is far faster than post for anything to do with the API.