PanditOne CloudDeveloper platform
Developer API

Public API docs

Integrate chart calculation, report generation, and Kundli matching.

These docs describe the provider API surface. Use the workspace console after sign-in to create keys, inspect usage, and manage limits.

Base URL

https://api.myjyotishi.app/api/v1
Authenticate with a workspace API key using Bearer auth or X-API-Key.
Pass customer references through external_customer_id and idempotency_key.
Keep your own customer pricing, checkout, consent, and delivery flow.

Authentication

Send the workspace API secret as a Bearer token or as X-API-Key. Secrets are shown once when created in the workspace console.

Authorization: Bearer $PANDITONE_API_KEY
X-API-Key: $PANDITONE_API_KEY

Quickstart

This call returns chart facts without creating a report checkout. Use the full report endpoint when you need a saved report link.

curl -X POST https://api.myjyotishi.app/api/v1/developer/api/v1/charts/calculate \
  -H "Authorization: Bearer $PANDITONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "birth": {
    "full_name": "Customer Name",
    "date_of_birth": "1998-01-01",
    "time_of_birth": "02:02:00",
    "time_accuracy": "exact",
    "birth_place_text": "Mumbai, India",
    "latitude": "19.076000",
    "longitude": "72.877700",
    "timezone": "Asia/Kolkata"
  },
  "locale": "en-US",
  "report_type": "detailed_kundli",
  "external_customer_id": "cust_123",
  "idempotency_key": "order_123_chart"
}'

Endpoints

POST

Calculate Chart

chart_calculation

/developer/api/v1/charts/calculate

Return deterministic Kundli chart facts from provider-submitted birth details.

POST

Generate Full Kundli Report

full_kundli_report

/developer/api/v1/reports/full

Create a saved report record, secure report link, and PDF/download reference.

POST

Run Compatibility Match

compatibility_match

/developer/api/v1/compatibility/match

Match two birth profiles with Ashtakoot, dosha review, dasha timing, and reference data.

Birth payload

Use this shape for chart calculation and full report generation. Coordinates are recommended because they reduce ambiguity in place matching and timezone selection.

{
  "birth": {
    "full_name": "Customer Name",
    "date_of_birth": "1998-01-01",
    "time_of_birth": "02:02:00",
    "time_accuracy": "exact",
    "birth_place_text": "Mumbai, India",
    "latitude": "19.076000",
    "longitude": "72.877700",
    "timezone": "Asia/Kolkata"
  },
  "locale": "en-US",
  "report_type": "detailed_kundli",
  "external_customer_id": "cust_123",
  "idempotency_key": "order_123_chart"
}

Compatibility payload

Compatibility matching accepts two complete birth profiles. The response includes deterministic matching output and current usage state.

{
  "partner_a": {
    "full_name": "Partner A",
    "date_of_birth": "1998-01-01",
    "time_of_birth": "02:02:00",
    "time_accuracy": "exact",
    "birth_place_text": "Mumbai, India",
    "latitude": "19.076000",
    "longitude": "72.877700",
    "timezone": "Asia/Kolkata"
  },
  "partner_b": {
    "full_name": "Partner B",
    "date_of_birth": "1996-09-01",
    "time_of_birth": "20:38:00",
    "time_accuracy": "exact",
    "birth_place_text": "New York, United States",
    "latitude": "40.712800",
    "longitude": "-74.006000",
    "timezone": "America/New_York"
  },
  "locale": "en-US",
  "external_customer_id": "match_123",
  "idempotency_key": "match_123_v1"
}

Response shape

Responses include a request id, provider id, workspace id, locale, engine version, calculation details, result payload, warnings, and the relevant usage quota.

{
  "request_id": "req_...",
  "provider": "panditone-developer-api",
  "tenant_id": "workspace_...",
  "locale": "en-US",
  "engine_version": "vedic-engine-...",
  "calculation_config": {
    "ayanamsa": "Lahiri",
    "house_system": "whole_sign"
  },
  "chart": {
    "birth_profile": {},
    "chart_summary": {},
    "planetary_positions": []
  },
  "warnings": [],
  "usage": {
    "unit": "chart_calculation",
    "used": 18,
    "limit": 1000,
    "remaining": 982,
    "period_key": "2026-07"
  }
}

Errors and limits

400

Invalid request or matching input that cannot be calculated.

401

Missing, malformed, revoked, or unknown API key.

402

Workspace API access is not active.

422

Validation error for payload shape, date, time, locale, or plan code.

429

Rate limit or monthly quota exceeded for the requested unit.

5xx

Provider or engine error. Retry with the same idempotency key when safe.

Data and privacy posture

  • The API is intended for provider platforms that already manage their own customer relationship and consent.
  • Full report calls create saved report records so the generated link can be reopened by the customer flow.
  • Store your own customer references in external_customer_id instead of sending unnecessary internal account data.
  • Do not use API output as medical, legal, financial, psychological, or safety advice.
  • Keep API keys server-side. Never expose a workspace API key in mobile app binaries or browser JavaScript.

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.

Read API docsOpen console