Skip to main content
POST/v1/numerology/lucky-numbers

Generate lucky numbers

Generates a deterministic lucky number set from name and date in the JSON body (BirthInput-aligned), with optional count (1-20, default 6). Returns lucky numbers with supporting numerology context.

GET is deprecated

GET /v1/numerology/lucky-numbers still works for existing integrations but is deprecated since 2026-10-04: it puts personal data in the URL, where logs keep it. Its responses carry a Deprecation header. Use POST as shown here; the answer is the same. It stays available for at least 12 months. See the changelog.

Request parameters​

namerequired
string
Person name
daterequired
string (date)
Birth date (YYYY-MM-DD)
countoptional
integer
How many lucky numbers to return

Response fields​

success
boolean
True if the request succeeded
message
string
Human-readable status message
data
object
data.lucky_numbers
array[integer]
Lucky numbers, no repeats: first the Life Path, Expression, Soul Urge, Personality and Birth Day (these may be master numbers 11, 22, 33), then digits 1-9 from the birth date in ascending order, topped up with unused digits 1-9 (at most 9 are guaranteed)
data.power_number
integer
Most powerful number for the person
data.date_specific
boolean
Whether numbers are specific to a date
data.interpretation
string
How to use these numbers

Errors​

Invalid API key format.
API key is missing. Include it in the Authorization header as 'Bearer YOUR_KEY'.
The provided API key was not found. Verify the key in your Asterwise dashboard.
This API key has been revoked.
Too many requests per minute. Please slow down.
Something went wrong on our end. Please try again, or contact [email protected] if the problem persists. Include your request_id when contacting support.
Too many requests from this IP address. Please slow down.
Monthly API call limit reached. Upgrade your plan to continue.
Request body exceeds maximum allowed size of 64KB.
Your subscription has expired. Please renew at asterwise.com/dashboard to continue.
The request couldn't be processed. See the 'details' field for specific field-level issues.