The Numerology API v1.0.2¶
The Numerology API is a production-grade platform for building numerology and astrology products with deterministic outputs, structured JSON contracts, and broad endpoint coverage.
- 220+ documented endpoints across numerology, horoscope, astrology, compatibility, travel, education, family legacy, and divination tools
- v1.0.2 current release with 10 new extended endpoint families and full 26-language response coverage
- Public RapidAPI path for fast prototyping and onboarding
- Direct API + dashboard path for advanced and enterprise-grade integration
- Developer-ready docs with request examples, parameter contracts, and response patterns
- v1.0.2 additive release with 10 new direct API endpoint families for relationship milestones, relocation, vehicles, phone-number fit, signatures, pets, creative projects, family legacy, education paths, and travel destination alignment
- 26 supported response languages:
en,fr,es,de,pt,ja,hi,ar,ru,tr,it,pl,nl,id,ko,th,ro,ur,gu,bn,vi,ta,te,mr,pa,zh - Multi-system numerology support via
num_sys:pythagorean,chaldean, andvedic
v1.0.2 Highlights¶
v1.0.2 is an additive production release for the Numerology API. It builds on the released v1.0.1 multi-system and 8-language milestone by adding 10 more extended endpoint families and expanding supported response coverage to 26 languages.
This release focuses on four major goals:
- New extended endpoint coverage
- Adds 10 new endpoint families.
- Each new endpoint supports both
GETandPOST. - All new endpoints use clean public routes under
/api/v1/*. - New endpoint families include relationship milestones, relocation, vehicle identity, phone-number fit, signatures, pets, creative projects, family legacy, education paths, and travel destination alignment.
| New v1.0.2 endpoint family | Public route |
|---|---|
| Relationship Milestone Numerology | /api/v1/relationship-milestone-numerology |
| Relocation Compatibility | /api/v1/relocation-compatibility |
| Vehicle Identity Numerology | /api/v1/vehicle-identity-numerology |
| Phone Number Personal Fit | /api/v1/phone-number-personal-fit |
| Signature Numerology | /api/v1/signature-numerology |
| Pet Name Harmony | /api/v1/pet-name-harmony |
| Creative Project Numerology | /api/v1/creative-project-numerology |
| Family Legacy Matrix | /api/v1/family-legacy-matrix |
| Education Path Numerology | /api/v1/education-path-numerology |
| Travel Destination Alignment | /api/v1/travel-destination-alignment |
- Continued multi-system numerology
- New name/title/text-based endpoints support optional
num_sys. - Supported systems:
pythagoreanchaldeanvedic
-
pythagoreanremains the default to preserve existing behavior. -
Expanded language coverage
- v1.0.1 remains the released 8-language milestone:
enesdefrptarhija
- v1.0.2 adds 18 additional languages:
rutritplnlidkothrourgubnvitatemrpazh
-
The new endpoint families include localized JSON meaning files across all 26 supported language directories.
-
Documentation and release readiness
- Adds integration docs for all 10 new endpoint families.
- Adds a v1.0.2 changelog.
- Updates the Extended Endpoints index and API reference release links.
- Exposes the new endpoints in dashboard internal docs and command palette discovery.
- Verifies route visibility, JSON coverage, localized meaning structure, and test-suite stability with Python 3.11.
v1.0.1 Highlights¶
v1.0.1 is an additive production release for the Numerology API. It builds on the v1.0.0 extended numerology rollout by adding deeper name, timing, business, decision, family, team, money, and archetype readings.
This release focuses on four major goals:
- Broader endpoint coverage
- Adds 10 new endpoint families.
- Each new endpoint supports both
GETandPOST. -
All new endpoints use clean public routes under
/api/v1/*. -
Multi-system numerology
- New name-based endpoints support optional
num_sys. - Supported systems:
pythagoreanchaldeanvedic
-
pythagoreanremains the default to preserve existing behavior. -
Expanded language coverage
- Supported response languages now include:
enesdefrptarhija
-
The 10 new endpoint families include localized JSON meaning files for all 8 supported languages.
-
Documentation and release readiness
- Adds integration docs for all 10 new endpoint families.
- Updates the Extended Endpoints index.
- Documents
GET,POST,lang, andnum_sysbehavior. - Verifies route visibility, JSON coverage, and test-suite stability with Python 3.11.
v1.0.0 Highlights¶
This release combines two major tracks into one platform version:
- Extended Numerology rollout
- Added 23 new endpoint families and 41 new GET/POST operations.
- Added new categories:
Identity & Name,Spiritual & Shadow, andRelationship. - Expanded timing coverage with personal week and universal day/week/month/year routes.
-
Validated multilingual smoke coverage (
en,es,de,fr,pt) at 100% in release QA. -
Horoscope engine migration and expansion
- Added 53+ new endpoints with standardized canonical report routing under
/api/v1/horoscope/reports/*. - Expanded daily/weekly/monthly/yearly report families and specialized suites (planetary, aspects, transits, house, planet-house).
- Upgraded request/response consistency and route parity for production integrations.
→ Read Full v1.0.0 Changelog → Read Horoscope Engine Architecture
Access Paths¶
| Path | Best For | Auth | Notes |
|---|---|---|---|
| RapidAPI (Public) | Prototyping, quick tests, smaller public integrations | x-rapidapi-key | English-first public route |
Direct API (api.numerologyapi.com) | Advanced integrations, extended numerology categories | X-API-Key | Required for direct-only endpoint families |
Dashboard (dashboard.numerologyapi.com) | Key management, private docs, enterprise controls | Account login | Operational management + enterprise features |
Direct-Only Categories
In v1.0.2, extended and enterprise-grade categories are currently available via direct API access only:
Identity & NameSpiritual & ShadowRelationshipTravel, relocation, education, vehicle, phone-fit, pet, signature, and family legacy endpoint familiesCycles: Personal Week, Universal Day, Universal Week, Universal Month, Universal Year, Monthly Energy Heatmap, Caution Dates CalendarAll Horoscope Report Endpoints
Base URL: https://api.numerologyapi.com
API Reference Map¶
- API Reference Overview
- Core Endpoints
- Cycles & Transits
- Identity & Name
- Spiritual & Shadow
- Relationship
- Bridge Endpoints
- Karmic Endpoints
- Horoscope Endpoints
- Other Endpoints (Tarot / Gematria)
Horoscope Engine (Production Model)¶
The horoscope stack is deterministic and Swiss Ephemeris-driven, designed for real production behavior (stable outputs, reproducible QA, and cache-friendly route design).
- Deterministic factor stacks by period (daily, weekly, monthly, yearly)
- Public mode (sign-based) and personalized mode (birth-data aware)
- Report suites beyond general horoscope: planetary, aspects, transits, house, planet-house
- Enterprise wrappers in responses (
_enterprise,_api_metadata_) for operational metadata
→ Engine Deep Dive → Horoscope Reports Overview
Quick Start¶
Direct API (recommended for advanced coverage)¶
curl "https://api.numerologyapi.com/api/v1/life_path?birth_year=1990&birth_month=5&birth_day=15&lang=en" \
-H "X-API-Key: YOUR_API_KEY"
Direct API v1.0.2 extended endpoint¶
curl "https://api.numerologyapi.com/api/v1/relationship-milestone-numerology?person_a_name=Amina%20Bello&person_a_dob=1992-04-18&person_b_name=Jonas%20Meyer&person_b_dob=1990-11-06&milestone_date=2027-06-12&milestone_type=wedding&num_sys=chaldean&lang=fr" \
-H "X-API-Key: YOUR_API_KEY"
RapidAPI (public route)¶
curl "https://the-numerology-api.p.rapidapi.com/life_path?birth_year=1990&birth_month=5&birth_day=15" \
-H "x-rapidapi-key: YOUR_RAPIDAPI_KEY" \
-H "x-rapidapi-host: the-numerology-api.p.rapidapi.com"
Response Shape (example)¶
{
"life_path_number": 3,
"summary": {
"title": "Life Path 3",
"overview": "Creative, expressive, and socially magnetic energy pattern."
},
"_enterprise": {
"client": "The Numerology API"
},
"_api_metadata_": {
"api_version": "1.0.2",
"endpoint_name": "life_path",
"documentation_url": "https://docs.numerologyapi.com/"
}
}
Migration Notes for Existing Integrations¶
- Route direct-only v1.0.2 categories to
https://api.numerologyapi.com. - Prefer
POSTfor richer/nested request contracts where available. - Use
langon supported direct API routes for localized JSON meanings across the 26-language response set. - Use
num_syson name/title/text-based numerology routes when you needpythagorean,chaldean, orvediccalculations. - Keep date/month inputs normalized (
YYYY-MM-DD,YYYY-MM). - Parse
_enterpriseand_api_metadata_consistently in your client models. - For horoscope products, move to canonical
/api/v1/horoscope/reports/*endpoints.
WordPress Plugin Integration¶
Need a no-code path for site delivery? Use the official Dakidarts Numerology Core plugin to embed forms, readings, and reports directly into WordPress pages.