API Support

Sign in at the dashboard — with Google or a one-time code to your e-mail — and create a key on the Keys page. The Free plan needs no card, and the quick start has your first request in curl, Python and Node.

The key goes in the Authorization header as Authorization: Bearer kj_live_…, and a secret key sent in the query string is refused on purpose. A newly revoked key can also keep answering for up to a minute, and a new one can take the same minute to be seen — the gateway caches a key record for sixty seconds. See authentication.

A secret key (kj_live_…, kj_test_…) is a credential: it belongs on your own server and must never appear in a mobile app, a browser bundle or a repository. A publishable key (kj_pub_…) is meant to be visible in a web page — it is accepted only from the origins you list against it, and never on the heavy endpoints. Full detail in authentication.

The origin the browser sent is not one listed on that key. The match is exact — scheme, host and port are all part of an origin, and * is not a wildcard. Add the origin on the Sites page of the dashboard.

Revoke it in the dashboard; revocation is immediate. Then tell us at support@goappsters.in so we can watch the account for misuse. Requests made with your key before you revoke it are charged to your account.

Each API has a price in credits: a calculation 1, a written reading 5, a scan across time 10 or 20, a PDF 500 or 1,000. The whole list is Credits per API, and every plan can call all of it except PDFs, which are not on Free. A request we refuse costs nothing: a validation error, an invalid or revoked key, a rate limit, a quota stop, or a failure on our side. A cached answer costs the same as a fresh one — you asked and you got the answer. A match batch costs 1 credit per pair. The time zone lookup and the reference tables are free.

meta.credits on every JSON answer and the X-KJ-Credits header on every metered one. With a secret key, X-KJ-Credits-Remaining says what is left. The dashboard’s Usage page shows credits and requests by endpoint and by day.

Usually refused requests: they appear in your logs and not in ours, because they were never charged. Check too that you are counting credits and not requests — a reading is one request and 5 credits. Included credits also reset on your billing day — the day of the month your paid plan started, at midnight UTC — not on the 1st, and they do not roll over. The dashboard shows the next reset.

Each plan has a sustained per-minute rate and a burst, both published on the pricing page and enforced by the gateway. Over the rate you get 429 rate_limited until the minute passes; the response headers say how long to wait, and retrying with a short backoff is the right response. Nothing is throttled silently.

The ones that compute a great deal more than the rest — a month of panchang, a year-long transit scan, a batch match, a PDF. They are open on every plan (PDFs on every paid plan), cost more credits, and carry their own limit of 10 requests a minute. The scan, the batch and the PDFs are closed to publishable keys; a request for one with such a key, or for a PDF on Free, returns 403 plan_required.

Two ways, both on the Plan page. Buy a credit pack (Starter, Growth and Scale): extra credits on the plan you are on, spent after the month’s own and good for 12 months. Or upgrade: the new allowance applies as soon as the payment clears. Either lifts a quota stop within a minute. If you run over most months, upgrading is the cheaper of the two, and the page says so when it is. For committed volume, write to us about an Enterprise plan.

A pack counts only on the plan it was bought on, or a higher one. On a lower plan — or on Free, after a cancellation or a failed payment — it is frozen, not lost: nothing is taken from it, and it counts again when you are back on that plan, until its 12 months are up. The Plan page lists each pack and says which are frozen. A pack is not refundable; see the refund policy.

Usually not: ayanamsa, house system, sunrise convention and time zone each move a result legitimately, and why results differ walks through all four. If it still looks wrong after that, send us the request body, the settings you used and what you expected — that is enough for us to reproduce it.

On the Plan page of the dashboard, under Tax invoices. GoAppsters Private Limited issues a GST tax invoice for every payment as soon as it clears and e-mails you a link to it — open it to print it or save it as a PDF — and a credit note for any refund. Indian accounts are billed in rupees, GST included. Your legal name, GSTIN and billing address are printed as they are on the Settings page when you pay, so add them before paying; an invoice already issued is not changed. Razorpay also e-mails a payment receipt, which is not a tax invoice.

Cancel on the Plan page. Your plan and keys keep working to the end of the period you have paid for, and no further payment is taken. The refund rules — the 7-day window on a first payment, renewals, annual plans, duplicate charges and outages — are all in the Refund and Cancellation Policy.

On the Plan page, under Change your plan. It changes the subscription you already have — it never starts a second one, and there is no payment window to go through again.

A bigger plan starts at once. Razorpay works out what the rest of the current period costs on the new plan, charges that difference to the card already on the subscription, and the new allowance is yours immediately.

A smaller plan starts at your next renewal. Nothing is charged on the day you ask, you keep the allowance you have paid for until the period ends, and the page shows the date. Until that date a Keep <your plan> button calls the change off. Razorpay allows one scheduled change at a time, so the other plans are held until you either let it happen or call it off.

No. A failed payment is retried for seven days; if it has still not succeeded the account returns to the Free plan and your keys keep working at Free limits. We e-mail you when a payment first fails.

Yourself, at once: Settings in the dashboard has a Delete my account button. The account, its keys and its usage counters are deleted there and then, and the keys stop working within a minute. Invoices and the tax records attached to them are kept for as long as Indian law requires, and what survives and for how long is set out in the API Privacy Policy. If you cannot sign in any more, write to support@goappsters.in from the account’s own e-mail address with the subject Delete my API account and we will do it for you.

Birth details are not part of this, because they were never stored: a request body is used to compute an answer and is then gone.

Yes — ask in the same e-mail, or within 30 days of termination, and we will send the usage data and invoices held for your account.