New Numerology API

Security

Security and data handling

Birth details and names are personal data, and your users trust you with them. This page says what our APIs keep, what they do not, and how your keys are protected. The legal version is our Privacy Policy.
Read the Privacy PolicyHow API keys work

Updated

© API for Astrology (apiforastrology.com). "Security: a request's journey". All rights reserved. Not to be copied or reused.HTTPSYour appOur gatewayPrivate networkCalculationserviceBirth detailsAug 15, 1990 · New YorkAnswerKey checked, hash onlyBody not stored

  • Birth details and names you send

    Request bodies are never stored.

    • The APIs use the dates, times, places and names in a request only to compute the answer. Neither our gateway nor the calculation service stores request bodies. Numerology requests carry a person's name and birth date, and they are handled the same way.
    • Web addresses (URLs) can appear in server logs. So send birth details and names in the body of a POST request, not in the URL.
    • No request data goes to an AI provider. Readings are written from fixed rules and a written library of text, so the same input always gives the same answer.
    • For each call we keep a short record for support. It has the time, the endpoint, the status, how long it took and the request ID. It holds no birth details or names.
    • When a call fails, we keep the error and the response your app got, with birth details, names and other input values removed. You can then see why it failed on the Errors tab of your Usage page.

  • API keys

    Keys are stored only as hashes.

    • We store only a hash of each key, plus its first characters and its last 5 characters so you can recognize it. The full key is shown once, when you create it.
    • Test keys and live keys are separate. Test keys call the same API with a small allowance and are never billed.
    • Each key has its own per-minute rate limit. Revoke a key at any time from your account, and it stops working right away.
    • Owners and admins manage keys. Members can see a key's name and prefix, but cannot create or revoke keys.

  • How the service is built

    Only our gateway can reach the calculation service.

    • Customers call only our API gateway. The calculation service runs on a private network and accepts calls only from the gateway.
    • The gateway forwards only the operations on its own list, with only their own query fields. Anything else gets a 404. A request body can be up to 64 KB, and a call stops after 30 seconds.
    • Connections use HTTPS. Passwords and API keys are stored only as hashes. Only the people who run the service can reach the database.
    • The site and the API run with a major cloud hosting provider. Business customers who sign a data processing addendum (DPA) can get the full list of our providers.

  • Your account and your data

    Ask, and we delete it within 30 days.

    • We keep your account, team and settings while your account is open. We delete them within 30 days after you ask us to close the account.
    • Owners and admins can see who changed what in the account on the Activity page.
    • We use the cookies needed to keep you signed in, and Google Analytics cookies to see how people use this website. There are no advertising cookies, and analytics never gets birth details or API keys.
    • To see, export or delete your data, email privacy@apiforastrology.com.
    • Business customers can ask for a data processing addendum (DPA) at the same address.

Found a security problem? Email support@apiforastrology.com. Our security.txt lists the same address. We aim to reply within one business day.

Send birth details safely

Put the birth details in the JSON body of a POST request, not in the URL. Send your key in the Authorization header. Keep the key on your server, in an environment variable such as ASTROLOGY_API_KEY, never in a web page or a phone app.

POST /v1/planets

# John Doe, born Aug 15, 1990, 10:30 AM, New York
curl -X POST "https://apiforastrology.com/api/astrology/v1/planets" \
  -H "Authorization: Bearer $ASTROLOGY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"year":1990,"month":8,"day":15,"hour":10,"minute":30,"second":0,"latitude":40.7128,"longitude":-74.006,"timezone":"America/New_York"}'

Security questions

All questions
Do you store the birth details or names I send?

No. The gateway and the calculation service use them only to compute the answer. Neither one stores request bodies, for the Astrology API or the Numerology API. Send them in the body of a POST request, because web addresses (URLs) can appear in server logs.

Does any request data go to an AI provider?

No. Readings are written from fixed rules and a written library of text, so no request data leaves our service for an AI model.

What should I do if an API key leaks?

Roll it in your account. You get a new key, and the old one keeps working for 24 hours while you switch. If you think it is being misused, disable it at once while you check, or revoke it for good.

Can I get a data processing addendum (DPA)?

Yes. Business customers can ask for one at privacy@apiforastrology.com. Customers who sign it can get the full list of our providers.

Astrology API

Try it with a test key

Test keys call the real API with 1,000 requests a month and are never billed. Or try a request in the API reference first.

Get a free API keyOpen the API reference

Your first answer

John Doe, New York

POST /v1/planets200 OK
  • RisingVirgoHast
  • SunCancerAshlesha
  • MoonTaurusMrigashira
  • MarsAriesKrittika

Real API output. A free test key gets the same answer.

  1. 01

    Test key: 1,000 test calls a month to build with

  2. 02

    Free plan: 2,000 live calls a month, no card needed

  3. 03

    Open rules: every rule is published, so you can check any answer