Chart engine
Submit structured birth details and receive chart facts, calculation config, warnings, and usage state.
PanditOne Cloud Developer API
Build astrology products on top of the PanditOne Cloud chart engine.
Use provider APIs for deterministic birth-chart calculation, saved full Kundli reports, and compatibility matching while your product owns the customer account, checkout, branding, and delivery experience.
Report generation
Create a full saved Kundli report link from your own customer flow without sending users through PanditOne Cloud checkout.
Compatibility
Run deterministic matching with Ashtakoot, dosha review, dasha timing, and pundit reference data.
Workspace security
Create and revoke API keys privately; secrets are shown once and then stored only as hashes.
Integration model
Public docs, private operations.
Providers should be able to evaluate the API without a sales call. Operational access still belongs inside an authenticated workspace.
Public
API concepts, auth model, endpoint examples, response shapes, error handling, and integration workflow.
Private
API keys, active plan, quota usage, request history, key rotation, and workspace account settings.
Your product
Customer pricing, checkout, account identity, consent capture, support, and fulfillment status.
PanditOne Cloud
Chart calculation, full report generation, compatibility matching, limits, and API-key validation.
Provider endpoints
The public surface stays intentionally small.
POST
Calculate Chart
/developer/api/v1/charts/calculate
Return deterministic Kundli chart facts from provider-submitted birth details.
POST
Generate Full Kundli Report
/developer/api/v1/reports/full
Create a saved report record, secure report link, and PDF/download reference.
POST
Run Compatibility Match
/developer/api/v1/compatibility/match
Match two birth profiles with Ashtakoot, dosha review, dasha timing, and reference data.
Private API operations
Manage keys, limits, and usage from the workspace console.
The docs are public so providers can evaluate the integration. API keys, active subscriptions, quota usage, and request history stay behind workspace sign-in.