Numerology API v1.0.1 Changelog¶
Release date: 2026-06-08
Version: v1.0.1
Scope: Numerology API endpoint expansion, multi-system numerology support, extended JSON meaning localization, route cleanup, and documentation parity.
General Release Overview¶
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.
Validation completed for this release:
- Full Python test suite:
137 passed - OpenAPI route check: all 10 clean routes present
- New
/api/v1/extended/*routes: not mounted - JSON translation validation: 8 language folders, 444 files each, no structure mismatch
- Live JSON meaning folders: 8 languages × 444 files each
New¶
New Endpoint Families¶
v1.0.1 adds 10 new endpoint families and 20 operations.
| Endpoint | Methods | Path |
|---|---|---|
| Career Path Numerology | GET, POST | /api/v1/career-path-numerology |
| Wealth Code Reading | GET, POST | /api/v1/wealth-code-reading |
| Home Address Numerology | GET, POST | /api/v1/home-address-numerology |
| Baby Name Forecast | GET, POST | /api/v1/baby-name-forecast |
| Team Dynamics Numerology | GET, POST | /api/v1/team-dynamics-numerology |
| Domain Name Numerology | GET, POST | /api/v1/domain-name-numerology |
| Product Name Numerology | GET, POST | /api/v1/product-name-numerology |
| Decision Crossroads Reading | GET, POST | /api/v1/decision-crossroads-reading |
| Launch Timing Numerology | GET, POST | /api/v1/launch-timing-numerology |
| Personal Archetype Stack | GET, POST | /api/v1/personal-archetype-stack |
New Shared Endpoint Infrastructure¶
v1.0.1 adds shared helper logic for the new extended numerology endpoints, including:
- localized JSON loading
- endpoint config lookup
- meaning and detailed-meaning lookup
- name profile calculation
- birth-date numerology helpers
- scoring helpers
- usage tracking
- enterprise response wrapping
- request authorization reuse
Numerology System Hardening¶
The shared numerology-system helper now includes explicit, validated letter tables for all supported systems:
pythagoreanchaldeanvedic
The Vedic table is supported for Latin-transliterated names and is kept separate from Chaldean even though both systems use the same A-Z values in v1.0.1. Common Latin diacritics and ligatures are normalized before name calculation, and missing-name-value helpers now respect each system's actual alphabet value range.
New Test Coverage¶
New tests cover:
- calculator behavior for the 10 endpoint families
chaldeanandvedicnumerology system support- 8-language policy support
- localized meaning lookup
- OpenAPI route visibility
- canonical route shape without
/extended
Fixes¶
Route Cleanup¶
The new endpoint families now use clean public paths only:
- Correct:
/api/v1/career-path-numerology - Correct:
/api/v1/wealth-code-reading - Correct:
/api/v1/personal-archetype-stack
The draft /api/v1/extended/* route shape for these 10 new endpoint families is not mounted and does not appear in OpenAPI.
Language Policy Fixes¶
The shared language policy now includes all 8 supported languages:
enesdefrptarhija
The existing horoscope report exception remains unchanged: engine-backed /api/v1/horoscope/reports/* routes continue to support en only.
Translation and JSON Validation Fixes¶
The translation workflow was hardened before endpoint rollout:
- protected placeholders, URLs, endpoints, filenames, emails, and API tokens are preserved
- large JSON strings are chunked safely
- exact English leftovers are flagged during QA
- translated JSON structure is compared against English source structure
- atomic output writing prevents partial JSON writes
- resume logic skips only structurally valid translated files
The new endpoint meaning bundle was validated before copying into live language folders.
Documentation Fixes¶
Documentation was aligned with the implemented API surface:
- Added
num_systo relevant GET and POST examples. - Documented 8-language support for the new pages.
- Added the 10 new pages to the Extended Endpoints index.
- Normalized Markdown parameter tables so nullable types render correctly.
Production Validation Fixes¶
Validation was rerun using the workspace Python standard:
- Python:
/opt/homebrew/bin/python3.11 - Full tests:
137 passed - OpenAPI sanity check: clean routes present
- Hidden/draft
/extendedroutes for the new endpoints: absent
Deprecated¶
No existing production endpoint is formally deprecated in v1.0.1.
| Endpoint | Status in v1.0.1 | Replacement | Notes |
|---|---|---|---|
| None | Not applicable | Not applicable | v1.0.1 is additive for production clients. |
Non-Public Draft Route Note¶
The draft /api/v1/extended/* route shape for the 10 new endpoint families is not part of the v1.0.1 public API surface.
Use the clean routes instead:
/api/v1/career-path-numerology/api/v1/wealth-code-reading/api/v1/home-address-numerology/api/v1/baby-name-forecast/api/v1/team-dynamics-numerology/api/v1/domain-name-numerology/api/v1/product-name-numerology/api/v1/decision-crossroads-reading/api/v1/launch-timing-numerology/api/v1/personal-archetype-stack
Note
These v1.0.1 additions are available through direct API access at https://api.numerologyapi.com using your API key. They are currently not supported via the RapidAPI gateway.