Mobile number numerology API reference
Updated
The number check endpoints of API for Astrology (apiforastrology.com) read a mobile, vehicle or house number for its owner. Only the digits count, read against the owner's mulank and bhagyank. Each number gets a fit: good, neutral, mixed or difficult. Other endpoints compare up to 5 numbers and read a business name. The group has 3 endpoints.
Call POST /v1/number with the kind of number, its value and the owner's birth_date. POST /v1/numbers compares up to 5 numbers in the order you send them, never ranked. POST /v1/business reads a business name and its launch date for the owner. Every fit follows one rule with no weights, explained in how a fit is decided.
Number checks: a mobile, vehicle or house number, several numbers side by side, and a business name with its launch date.
3 endpoints. Paths are relative to https://apiforastrology.com/api/numerology. Send your API key in the Authorization: Bearer header (see authentication). No key yet? Get a key. To send test requests from the browser, open the interactive reference.
Overview: Number checks.
Which number check endpoint to call
| What you need | Endpoint | Cost |
|---|---|---|
| A check of one mobile, vehicle or house number. Start here | POST /v1/number | 1 reading credit |
| Up to 5 numbers of one kind, side by side | POST /v1/numbers | 2 reading credits |
| A business name and its launch date, read for the owner | POST /v1/business | 2 reading credits |
Mobile, vehicle, house or business number
POST /v1/number
Adds up a mobile, vehicle or house number. Only digits count: letters are listed in ignored_letters and not counted. A business name is read by its letters instead. Then it gives the fit with the owner's mulank and bhagyank, by the same rule as the name checker.
Uses 1 reading credit. On live keys a successful response uses them from your monthly reading credits, and no calls. Test keys answer for the sample people only, and it counts as 1 test call. What reading credits buy.
Cost: 1 reading credit on a live key, 1 test call on a test key.
Required inputs
| Name | In | What it is |
|---|---|---|
| kind | body | What the number is. |
| value | body | The number as written, such as 98290 12345, RJ14 CD 4521 or B-402. For business, the business name in English letters. |
| birth_date | body | The owner's date of birth, YYYY-MM-DD. |
Optional inputs (2), with their defaults
| Name | In | What it does |
|---|---|---|
| lang | query | Language of the readings and names: en, hi. Codes stay in English. |
| detail | query | Length of the readings: standard (the default, short, for app cards) or expanded (about three times longer, for reading in full). A passage with no long form yet comes back at standard length and is listed in localization.fell_back_to_standard. |
Main response fields
kind(string)kind_name(string)about(string)value(string)digits(string)total(number)compound(number)number(number)ignored_letters(array)planet(string)planet_name(string)person(object): holds birth_date, mulank, bhagyank.fit(object): holds number, links, outcome, outcome_name, reading.not_claimed(string)localization(object): holds lang, detail, fell_back_to_en, fell_back_to_standard.
# A mobile number for John Doe, born Aug 15, 1990
curl -X POST "https://apiforastrology.com/api/numerology/v1/number" \
-H "Authorization: Bearer $ASTROLOGY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"kind":"mobile","value":"212 555 0147","birth_date":"1990-08-15"}'{
"kind": "mobile",
"kind_name": "Mobile number",
"about": "A mobile number is read by adding all its digits.",
"value": "212 555 0147",
"digits": "2125550147",
"total": 32,
"compound": 32,
"number": 5,
"ignored_letters": [],
"planet": "Mercury",
"planet_name": "Mercury",
"person": {
"birth_date": "1990-08-15",
"mulank": 6,
"bhagyank": 6
},
"fit": {
"number": 5,
"links": [
{
"from": "mulank",
"from_number": 6,
"to_number": 5,
"relation": "friend",
"via": [],
"from_name": "mulank",
"relation_name": "friendly"
},
{
"from": "bhagyank",
"from_number": 6,
"to_number": 5,
"relation": "friend",
"via": [],
"from_name": "bhagyank",
"relation_name": "friendly"
}
],
"outcome": "good",
"outcome_name": "Good fit",
"reading": "This number gets along well with your own numbers. It tends to support you."
},
"not_claimed": "Numbers describe tendencies, not fixed events. Use them as a guide, not a rule.",
"localization": {
"lang": "en",
"detail": "standard",
"fell_back_to_en": [],
"fell_back_to_standard": []
}
}Example from a real call for A mobile number for John Doe, born Aug 15, 1990. Long lists and texts are shortened.
Parameters, schemas and a test request in the interactive reference. Feature: Number checks.
Compare several numbers
POST /v1/numbers
Up to 5 mobile, vehicle or house numbers of one kind, each read exactly as the number route reads one. In the order given, never ranked (ranked: false): choosing a number is the person's call.
Uses 2 reading credits. On live keys a successful response uses them from your monthly reading credits, and no calls. Test keys answer for the sample people only, and it counts as 1 test call. What reading credits buy.
Cost: 2 reading credits on a live key, 1 test call on a test key.
Required inputs
| Name | In | What it is |
|---|---|---|
| kind | body | What the numbers are. |
| values | body | Up to 5 numbers to compare, as written. Returned in the order given, never ranked. |
| birth_date | body | The owner's date of birth, YYYY-MM-DD. |
Optional inputs (2), with their defaults
| Name | In | What it does |
|---|---|---|
| lang | query | Language of the readings and names: en, hi. Codes stay in English. |
| detail | query | Length of the readings: standard (the default, short, for app cards) or expanded (about three times longer, for reading in full). A passage with no long form yet comes back at standard length and is listed in localization.fell_back_to_standard. |
Main response fields
kind(string)kind_name(string)person(object): holds birth_date, mulank, bhagyank.checks(array of objects): each item holds kind, kind_name, about, value, digits, total, compound, number, ignored_letters, planet, planet_name, person.ranked(boolean)not_claimed(string)localization(object): holds lang, detail, fell_back_to_en, fell_back_to_standard.
# Two mobile numbers for John Doe, born Aug 15, 1990
curl -X POST "https://apiforastrology.com/api/numerology/v1/numbers" \
-H "Authorization: Bearer $ASTROLOGY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"kind":"mobile","values":["212 555 0147","212 555 0199"],"birth_date":"1990-08-15"}'{
"kind": "mobile",
"kind_name": "Mobile number",
"person": {
"birth_date": "1990-08-15",
"mulank": 6,
"bhagyank": 6
},
"checks": [
{
"kind": "mobile",
"kind_name": "Mobile number",
"about": "A mobile number is read by adding all its digits.",
"value": "212 555 0147",
"digits": "2125550147",
"total": 32,
"compound": 32,
"number": 5,
"ignored_letters": [],
"planet": "Mercury",
"planet_name": "Mercury",
"person": {
"birth_date": "1990-08-15",
"mulank": 6,
"bhagyank": 6
},
"fit": {
"number": 5,
"links": [
{
"from": "mulank",
"from_number": 6,
"to_number": 5,
"relation": "friend",
"via": [],
"from_name": "mulank",
"relation_name": "friendly"
},
{
"from": "bhagyank",
"from_number": 6,
"to_number": 5,
"relation": "friend",
"via": [],
"from_name": "bhagyank",
"relation_name": "friendly"
}
],
"outcome": "good",
"outcome_name": "Good fit",
"reading": "This number gets along well with your own numbers. It tends to support you."
},
"not_claimed": "Numbers describe tendencies, not fixed events. Use them as a guide, not a rule.",
"localization": {
"lang": "en",
"detail": "standard",
"fell_back_to_en": [],
"fell_back_to_standard": []
}
},
{
"kind": "mobile",
"kind_name": "Mobile number",
"about": "A mobile number is read by adding all its digits.",
"value": "212 555 0199",
"digits": "2125550199",
"total": 39,
"compound": 39,
"number": 3,
"ignored_letters": [],
"planet": "Jupiter",
"planet_name": "Jupiter",
"person": {
"birth_date": "1990-08-15",
"mulank": 6,
"bhagyank": 6
},
"fit": {
"number": 3,
"links": [
{
"from": "mulank",
"from_number": 6,
"to_number": 3,
"relation": "neutral",
"via": [],
"from_name": "mulank",
"relation_name": "neutral"
},
{
"from": "bhagyank",
"from_number": 6,
"to_number": 3,
"relation": "neutral",
"via": [],
"from_name": "bhagyank",
"relation_name": "neutral"
}
],
"outcome": "neutral",
"outcome_name": "Neutral",
"reading": "This number is neutral to your own numbers. It neither helps nor gets in the way much."
},
"not_claimed": "Numbers describe tendencies, not fixed events. Use them as a guide, not a rule.",
"localization": {
"lang": "en",
"detail": "standard",
"fell_back_to_en": [],
"fell_back_to_standard": []
}
}
],
"ranked": false,
"not_claimed": "Numbers describe tendencies, not fixed events. Use them as a guide, not a rule.",
"localization": {
"lang": "en",
"detail": "standard",
"fell_back_to_en": [],
"fell_back_to_standard": []
}
}Example from a real call for Two mobile numbers for John Doe, born Aug 15, 1990. Long lists and texts are shortened.
Parameters, schemas and a test request in the interactive reference. Feature: Number checks.
Business name and launch date
POST /v1/business
A business name read against its owner (Chaldean, as a name). It also gives up to 5 spellings of its first word that sound the same and suit the owner. When launch_date is given, it shows how that date's number suits the owner. Same rules as the name checker and the number checker.
Uses 2 reading credits. On live keys a successful response uses them from your monthly reading credits, and no calls. Test keys answer for the sample people only, and it counts as 1 test call. What reading credits buy.
Cost: 2 reading credits on a live key, 1 test call on a test key.
Required inputs
| Name | In | What it is |
|---|---|---|
| name | body | The business name, in English letters. |
| birth_date | body | The owner's date of birth, YYYY-MM-DD. |
Optional inputs (3), with their defaults
| Name | In | What it does |
|---|---|---|
| lang | query | Language of the readings and names: en, hi. Codes stay in English. |
| detail | query | Length of the readings: standard (the default, short, for app cards) or expanded (about three times longer, for reading in full). A passage with no long form yet comes back at standard length and is listed in localization.fell_back_to_standard. |
| launch_date | body | A planned launch or opening date, YYYY-MM-DD. Optional. |
Main response fields
name(object): holds kind, kind_name, about, value, name, total, compound, number, master, planet, planet_name, person.suggestions(array of objects): each item holds name, word, changes, total, compound, number, planet, planet_name, fit.found(number)suggest_about(string)not_claimed_spelling(string)launch(object): holds date, number, planet, planet_name, fit, about.not_claimed(string)localization(object): holds lang, detail, fell_back_to_en, fell_back_to_standard.
# Acme Inc., owned by John Doe, born Aug 15, 1990, opening Dec 12, 2026
curl -X POST "https://apiforastrology.com/api/numerology/v1/business" \
-H "Authorization: Bearer $ASTROLOGY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"Acme Inc.","birth_date":"1990-08-15","launch_date":"2026-12-12"}'{
"name": {
"kind": "business",
"kind_name": "Business name",
"about": "A business name is read from its letters, the same way as a person's name.",
"value": "Acme Inc.",
"name": "Acme Inc.",
"total": 22,
"compound": 22,
"number": 4,
"master": true,
"planet": "Rahu",
"planet_name": "Rahu",
"person": {
"birth_date": "1990-08-15",
"mulank": 6,
"bhagyank": 6
},
"fit": {
"number": 4,
"links": [
{
"from": "mulank",
"from_number": 6,
"to_number": 4,
"relation": "friend",
"via": [
"Rahu"
],
"from_name": "mulank",
"relation_name": "friendly"
},
{
"from": "bhagyank",
"from_number": 6,
"to_number": 4,
"relation": "friend",
"via": [
"Rahu"
],
"from_name": "bhagyank",
"relation_name": "friendly"
}
],
"outcome": "good",
"outcome_name": "Good fit",
"reading": "This number gets along well with your own numbers. It tends to support you."
},
"not_claimed": "Numbers describe tendencies, not fixed events. Use them as a guide, not a rule.",
"localization": {
"lang": "en",
"detail": "standard",
"fell_back_to_en": [],
"fell_back_to_standard": []
}
},
"suggestions": [
{
"name": "Aacme Inc.",
"word": "Aacme",
"changes": [
{
"code": "double_a",
"from": "a",
"to": "aa",
"at": 0,
"name": "Doubled an a"
}
],
"total": 23,
"compound": 23,
"number": 5,
"planet": "Mercury",
"planet_name": "Mercury",
"fit": {
"number": 5,
"links": [
{
"from": "mulank",
"from_number": 6,
"to_number": 5,
"relation": "friend",
"via": [],
"from_name": "mulank",
"relation_name": "friendly"
},
{
"from": "bhagyank",
"from_number": 6,
"to_number": 5,
"relation": "friend",
"via": [],
"from_name": "bhagyank",
"relation_name": "friendly"
}
],
"outcome": "good",
"outcome_name": "Good fit",
"reading": "This number gets along well with your own numbers. It tends to support you."
}
}
],
"found": 1,
"suggest_about": "These spellings sound the same as your name but add up to a number that suits you. Only small, common spelling changes are tried.",
"not_claimed_spelling": "A new spelling changes the number of the name, not the person. Choose one only if you are happy to use it every day.",
"launch": {
"date": "2026-12-12",
"number": 7,
"planet": "Ketu",
"planet_name": "Ketu",
"fit": {
"number": 7,
"links": [
{
"from": "mulank",
"from_number": 6,
"to_number": 7,
"relation": "neutral",
"via": [
"Ketu"
],
"from_name": "mulank",
"relation_name": "neutral"
},
{
"from": "bhagyank",
"from_number": 6,
"to_number": 7,
"relation": "neutral",
"via": [
"Ketu"
],
"from_name": "bhagyank",
"relation_name": "neutral"
}
],
"outcome": "neutral",
"outcome_name": "Neutral",
"reading": "This number is neutral to your own numbers. It neither helps nor gets in the way much."
},
"about": "A launch date adds up to its own number. It is read against the owner's mulank and bhagyank."
},
"not_claimed": "Numbers describe tendencies, not fixed events. Use them as a guide, not a rule.",
"localization": {
"lang": "en",
"detail": "standard",
"fell_back_to_en": [],
"fell_back_to_standard": []
}
}Example from a real call for Acme Inc., owned by John Doe, born Aug 15, 1990, opening Dec 12, 2026. Long lists and texts are shortened.
Parameters, schemas and a test request in the interactive reference. Feature: Number checks.
Where the rules come from
The Chaldean letter values, with no letter worth 9, follow the table in Cheiro's Book of Numbers (1926).
Related pages
- Features: Number checks.
- Used for: Number and name sellers, Business naming tools, Numerology apps, Astrologer platforms.
- Guides: Quickstart, Conventions, Errors, Changelog.