Calculate · Integrate · Explore
Astrology API Documentation
Integrate the astrology API with documented endpoints, authentication guides and Node.js, TypeScript or Python SDKs. Explore birth charts, synastry, transits, Vedic calculations and separate readings APIs.
- 78 calculation APIs
- 1000 BCE–2500 CE historical inputs
- Western and Vedic-oriented tools
All 78 documented calculations are live: 77 standard calculations are available on every plan, and Pro adds Nakshatra Timeline. Free includes 500 standard requests per UTC calendar month. Durable jobs execute one at a time across the service.
Learn by building: astrology API tutorials and Node.js examples →
AI documentation (llms.txt) — a concise guide to the API, SDKs and MCP integration for coding assistants.
01 / Start here
Get your first integration working
Credentials, official clients and complete request examples.
- Authentication and API keys
Create a key, keep it on your server, and authenticate calculation requests.
All plans - SDKs & quickstart
Install Node.js / TypeScript or Python. Make your first call, add Tarot or readings, and handle errors safely.
All plans - Birth-chart SVG with Node.js
Generate a chart in one request, download the complete script, and display the SVG in your app.
All plans - Moon-phase calendar
Make a monthly calendar of the four primary Moon phases, then export the events as an iCalendar file. One request returns both the event data and the download.
All plans - Two-person chart comparison
Place two synthetic birth charts on one wheel and show the major aspects between them. Use the result as a visual feature in your relationship or astrology app.
All plans - Birth chart with transits
Combine a natal chart with planetary positions for another date. The script uses today’s UTC date by default, or accepts a date you choose.
All plans - Vedic D1 and D9 charts
Render the same synthetic birth details as a D1 Rashi chart and a D9 Navamsha chart. Keep Lahiri ayanamsa explicit and choose a North or South Indian layout.
All plans - MCP calculation walkthrough
Send one authenticated tools/call request to the Cosmic Ephemeris MCP server and save the structured result. This example uses Node’s built-in fetch and needs no extra package.
All plans - All 78 calculation examples
Copy cURL, Node.js and Python requests, then inspect schema-checked example responses.
Route-specific plans
02 / Foundations
Charts, inputs & relationships
Understand the input conventions, then choose the calculation you need.
- Astrology systems
Tropical defaults, sidereal opt-in behavior, supported ayanamsas, and scope boundaries.
All plans - Places, timezones & context
Resolve places and civil time explicitly, then build deterministic fact bundles for your application.
All plans - Birth chart
Planets, chart angles, supported houses, aspects, nodes, and calculation metadata.
All plans - Houses
Twenty-five explicit choices: 24 twelve-house systems plus Houses-only Gauquelin sectors, with no fallback.
All plans - Aspects
Angular relationships inside one natal chart with full calculation context.
All plans - Synastry
Two natal charts and cross-chart aspects without a compatibility score.
All plans
03 / Timing
Transits, events & calendars
Search bounded intervals and work with documented timing limits.
- Transits
Natal and transit charts plus transit-to-natal angular relationships.
All plans - Moon phases and calendar
Phase geometry, illuminated fraction, bounded primary-phase events and opt-in iCalendar export; explicit time-scale limits.
All plans - Planetary events
Bounded sign ingresses, tropical stations, and exact major-aspect crossings with explicit numerical limits.
All plans - House ingresses
Direct and retrograde transit crossings of fixed Equal or Whole Sign reference-chart cusps.
All plans - Planetary aspect windows
Exact-hit-anchored orb intervals, repeat numbering, clipped boundaries, and optional iCalendar text.
All plans - Nakshatra timeline
Gap-free nakshatra and pada transition windows across a bounded UTC interval.
Pro
04 / Sidereal
Sidereal & Vedic-oriented tools
Explicit conventions and route-specific capabilities—not a claim of complete traditional coverage.
- Sidereal overview
Coordinate conversion rules, date-aware ayanamsas, and the limits of sidereal support.
All plans - Birth chart
Birth-chart requests and response fields in sidereal longitude.
All plans - Houses
The same 25-choice Houses inventory in the selected sidereal frame; Natal SVG supports the 24 twelve-house choices.
All plans - Aspects
Natal aspects after applying the selected ayanamsa.
All plans - Transits
Natal-to-transit relationships calculated in one sidereal frame.
All plans - Synastry
Two sidereal charts and their cross-chart angular relationships.
All plans
05 / Product features
Readings, visuals & advanced tools
Choose structured text, chart graphics, reports or bounded research calculations.
- Readings, Tarot & horoscope
Integrate multilingual reading prose and card draws; distinguish them from the structured horoscope calculation.
All plans - Chart graphics, Western and Vedic calculations
Chart SVGs, Panchang, twenty-four Vargas from D1 through D150, Vimshottari through optional depth 4, composites, Davison, progressions, solar arcs, lunar nodes and returns; explicit documented limits.
All plans - Eclipse geometry, electional filters, astrocartography, and reports
Bounded global eclipse geometry, hourly electional filters, astrocartography, relocation, unified calendars, graphics, reports, sensitivity, and six fixed stars.
All plans
06 / Production
Operate your integration
Team controls, async workflows, agent access and advanced reliability evidence.
- Jobs, teams, webhooks, exports, and controls
Optional saved inputs and team access, key budgets, asynchronous jobs, signed webhooks and serverless integration.
All plans - MCP server
Server-side agent access to all 78 live calculations plus a separate symbolic tool for Tarot, readings and Vedic systems, with the same per-route plan entitlements.
All plans - Electional reliability without hidden scoring weights
Live exact hardening profiles, failure-budget benchmarks, and weight-free minimax regret with bounded sampled evidence.
All plans
Symbolic readings, Tarot and Vedic systems have a separate supplemental HTTP API and the cosmicephemeris_symbolic MCP tool. They complement, rather than change, the 78-operation catalog. Node/Python 0.5.0 supports all three supplemental methods. Reading prose and translations are AI-assisted symbolic reflections, not scientifically validated predictions or professional advice.
Integration reference First request, downloads, endpoint fields, historical dates and limits
Calculation foundations
Build Western, sidereal, and Vedic-oriented astrology applications with documented calculation endpoints and structured JSON responses. Routes with a zodiac option default to tropical; request sidereal mode with Lahiri, Raman, Krishnamurti, Fagan–Bradley, Yukteshwar, Sassanian, True Chitra, True Revati, True Pushya, Galactic Center at 0 Sagittarius, or Galactic Alignment/Mardyks ayanamsa.
Planetary positions are calculated using bundled NASA JPL DE440 and historical DE441 ephemeris data through Skyfield. Our calculation methodology explains the methods for houses, aspects, sidereal conversion, and other calculations, including their known limits. The Vedic-oriented routes and Nakshatra Timeline always use sidereal coordinates; each endpoint documents its exact scope.
Cosmic Ephemeris is a developer-first, server-to-server JSON API. It returns documented calculation data so your application can control interpretation and presentation.
Make your first request
- Create a least-privilege key from the API Keys area of your dashboard.
- Store the key in your server environment as
COSMICEPHEMERIS_KEY. The key is shown only once. - Send a JSON
POSTrequest tohttps://api.cosmicephemeris.com/api/astro/birth-chartwithAuthorization: Bearerauthentication. - Read the returned
chartobject. Setzodiac: "sidereal"andayanamsa: "lahiri"to request a sidereal chart.
Use the HTTP examples below on your server, or start with the official SDKs. Never put the key in browser JavaScript or a mobile application bundle.
// Node.js 22+ — server-side only
const response = await fetch("https://api.cosmicephemeris.com/api/astro/birth-chart", {
method: "POST",
headers: {
"Content-Type": "application/json",
"Authorization": `Bearer ${process.env.COSMICEPHEMERIS_KEY}`
},
signal: AbortSignal.timeout(20000),
body: JSON.stringify({
date: "2000-01-01",
time: "12:00",
timezone: "UTC",
lat: 0.0,
lon: 0.0
})
});
if (!response.ok) throw new Error(`Cosmic Ephemeris HTTP ${response.status}`);
const data = await response.json();
console.log(data.chart);
# Python — server-side only
import os
import requests
url = "https://api.cosmicephemeris.com/api/astro/birth-chart"
payload = {
"date": "2000-01-01",
"time": "12:00",
"timezone": "UTC",
"lat": 0.0,
"lon": 0.0
}
headers = {
"Content-Type": "application/json",
"Authorization": f"Bearer {os.environ['COSMICEPHEMERIS_KEY']}"
}
response = requests.post(url, json=payload, headers=headers, timeout=20)
response.raise_for_status()
print(response.json()["chart"])
Developer downloads
Four integration resources cover all seventy-eight live endpoints with contract status and method limits documented per operation. They describe how to call the API; they do not contain the calculation engine or introduce a new API version.
Complete request and response catalog
The complete API examples catalog provides generated cURL, Node.js SDK, and Python SDK requests plus one schema-validated successful response for each of the 78 live calculations.
Import-ready OpenAPI and Postman files
Import the OpenAPI 3.1 document into a compatible API tool,
or import the Postman collection, set
COSMICEPHEMERIS_KEY in a private, unsynced environment or supported secret store,
and send the included synthetic requests. Never save a real key in a shared collection or export.
Jupyter quickstart and CSV workflow
The downloadable Python notebook installs the pinned public client, reads the API key only from COSMICEPHEMERIS_KEY, runs synthetic birth-chart and event-calendar examples, and writes JSON and CSV files without placing a credential in the notebook.
- Set
COSMICEPHEMERIS_KEYin the notebook server's private environment, then open the downloaded notebook. - Run the installation and setup cells without pasting the key into a cell, output, filename, or shared notebook.
- Run the event-calendar cell with
include_csv: true; it writescosmic-ephemeris-events.csv. - Open that UTF-8 CSV in a spreadsheet. One row represents one ordered event from the bounded request.
CSV is an opt-in output only on documented export-capable operations, including event calendar and selected report or astrocartography formats. It is not a generic request format: normal calculations accept JSON, while bounded batch import accepts NDJSON—not CSV.
Downloading or importing these resources does not use quota. Sending calculation requests does: attempts admitted for processing consume quota even if validation or calculation later fails. Do not configure automatic retries.
Each account can run up to 2 calculations concurrently, maintain 5 active API keys and 50 saved chart profiles, and queue up to 10 active batch jobs containing 10 items each. Monthly plan quotas still apply.
Endpoint and response reference
All endpoints below use POST and the same server API key. Their JSON response wrappers differ; use the documented field for each endpoint.
| Path | Where to read the result |
|---|---|
/api/astro/birth-chart | chart |
/api/astro/aspects | The aspect array is aspects.aspects; its parent contains the full chart. |
/api/astro/houses | houses.systems, with normalized house_system at the top level. |
/api/astro/transits | transits.natal_chart, transits.transit_chart, and transits.aspects |
/api/astro/synastry | charts.personA, charts.personB, and aspects |
/api/astro/nakshatra-timeline | Top-level segments and timeline metadata; Pro required. |
/api/astro/horoscope | interpretation; current. |
/api/astro/natal-svg | svg as a string inside JSON; current. |
/api/astro/vargas | ascendant and bodies; twenty-four supported divisions from D1 through D150, with named conventions and D150 method selection; current. |
/api/astro/vimshottari | birth_balance, cycle, and periods; optional third/fourth levels with depth: 3/4; current. |
/api/astro/davison | midpoint, physical planets, angles, houses and aspects; current uncorrected TT/arithmetic method. |
/api/astro/composite | planets, angles, synthetic houses and aspects; current. |
/api/astro/panchang | tithi, nakshatra, yoga, karana, vara and solar_events; current, latitude [-88,88]. |
/api/astro/ashtakoota | Eight directional koota component scores and total out of 36 without a threshold verdict or interpretation; current. |
/api/astro/ashtakavarga | Seven-planet Bhinnashtakavarga, contributor Prastara, 337-point Sarvashtakavarga, and explicit opt-in reductions/pindas without interpretation; current. |
/api/astro/numerology | Declared Pythagorean date/name arithmetic with reduction traces and explicit calendar-year cycles; symbolic supported, no interpretations or predictions. |
/api/astro/secondary-progressions | progressed_planets, timing and separate natal_context; current, no progressed angles/houses. |
/api/astro/varga-svg | svg and chart (Vargas result), with optional deterministic PNG; North/South Indian layouts for all twenty-four supported divisions; current. |
/api/astro/lunar-nodes | Separate mean and geometric osculating true north/south node pairs with explicit frames; current. |
/api/astro/solar-arcs | Default true-Sun or explicit mean-Naibod solar-arc directed planets and angles, synthetic Equal/Whole Sign houses and explicit timing; current. |
/api/astro/returns | Next Sun/Moon longitude return, return_utc, chart and bounded search metadata; current. |
/api/astro/moon-phases | Instant phase geometry or a bounded primary-phase calendar in result, with explicit model metadata; current. |
/api/astro/planetary-events | Bounded sign ingresses, tropical stations, and exact major-aspect crossings in result.events; current. |
/api/astro/house-ingresses | Direct/retrograde transit crossings of fixed Equal or Whole Sign reference-chart cusps; current. |
/api/astro/aspect-windows | Exact-hit-anchored orb intervals, applying/separating labels, repeats and optional iCalendar text in result; current. |
/api/astro/event-calendar | Unified Moon, ingress, station, exact-aspect and aspect-window events, plus optional grouped aspect passes and iCalendar; current. |
/api/astro/event-rule-search | Bounded customer-defined AND/OR fact rules with validation, cost estimates, matching intervals, saved versions, schedules, and calendar output; current. |
/api/astro/convention-compare | Field-level comparison of two explicit zodiac, ayanamsa, and house-system profiles for the same birth input; current. |
/api/astro/chart-robustness | Sampled stability classifications across unknown or approximate birth time and two or three explicit convention profiles; current, non-exhaustive, never rectification or convention ranking. |
/api/astro/civil-time-audit | Never-guess local-time resolution: both repeated-time chart candidates with exact 22-fact differences, or no chart for a nonexistent time; current. |
/api/astro/chart-input-readiness | Machine-readable exact-route readiness and resolved, candidate, or sampled evidence for exact, ambiguous, nonexistent, approximate, or unknown birth time; current, never rectification. |
/api/astro/house-system-readiness | Fixed 25-system geometry readiness, cusp fingerprints, downstream route readiness, and explicit no-fallback evidence; current. |
/api/astro/house-placement-stability | Unweighted planet-house agreement across comparable systems, deterministic placement groups, and explicit no-fallback evidence; current. |
/api/astro/aspect-policy-stability | Compare 2–4 explicit aspect-orb policies on one chart with reason states, signed margins, set fingerprints, and deterministic equivalence groups; current. |
/api/astro/house-boundary-proximity | Exact two-sided cusp clearance and normalized position for selected planets across every available 12-house system, with explicit failures and no fallback; current. |
/api/astro/location-precision-audit | Nine-point coordinate-radius audit for one explicit 12-house system, with house stability, angle/cusp displacement, explicit failures, and no fallback; current. |
/api/astro/location-transition-scan | Center plus 64 fixed radial checkpoints for observed angle-sign, cusp-sign, and selected planet-house transition brackets, with explicit geometry failures and no full-disk guarantee; current. |
/api/astro/chart-uncertainty-envelope | Full-factorial seven-time by nine-location sampled evidence separating time-axis, location-axis, combined, and interaction-only observed variation; current. |
/api/astro/synastry-svg | Original deterministic double-wheel SVG in JSON, with optional deterministic PNG; current. |
/api/astro/transit-svg | Original deterministic natal/transit double-wheel SVG in JSON, with optional deterministic PNG; current. |
/api/astro/natal-report | Standalone calculation-fact HTML, source-linked facts, and optional integrity-checked download bytes; no interpretation; current. |
/api/astro/birth-time-sensitivity | Observed sensitivity for exact intervals or explicit unknown/approximate birth time; current, non-exhaustive, never rectification. |
/api/astro/fixed-stars | Six independently validated fixed stars only; no minor bodies; current. |
/api/astro/relocation-chart | Same birth instant and geocentric positions with destination angles and selected houses; current. |
/api/astro/astrocartography | Bounded MC/IC and sampled rising/setting geometry; no maps, rankings, or interpretations; current. |
/api/astro/eclipse-geometry | Bounded global solar/lunar eclipse geometry with optional observer snapshot at global maximum; no local contacts or paths; current. |
/api/astro/electional-search | AND-only electional filters on a fixed hourly grid; no ranking, continuous guarantee, or advice; current. |
/api/astro/electional-robustness-audit | Stress-test electional criteria across start-time and venue uncertainty; current, with bounded sampled evidence. |
/api/astro/electional-tolerance-frontier | Measure observed electional rule tolerance in time and venue directions; current, with bounded sampled evidence. |
/api/astro/electional-feasibility-audit | Explain sampled electional feasibility and minimal observed rule relaxations; current, with bounded sampled evidence. |
/api/astro/electional-resolution-audit | Show which observed electional match runs coarser sampling misses; current, with bounded sampled evidence. |
/api/astro/electional-sampling-phase-audit | Show whether electional results change with the sampling anchor; current, with bounded sampled evidence. |
/api/astro/electional-criterion-omission-audit | Measure which selected electional criteria uniquely exclude observed samples; current, with bounded sampled evidence. |
/api/astro/electional-criterion-pair-audit | Expose observed two-criterion electional exclusion interactions; current, with bounded sampled evidence. |
/api/astro/electional-criterion-relation-audit | Expose observed compatibility and redundancy among electional criteria; current, with bounded sampled evidence. |
/api/astro/electional-criterion-budget-audit | Find every optimal electional rule-relaxation combination by exact omission budget; current, with bounded sampled evidence. |
/api/astro/electional-criterion-budget-stability-audit | Audit whether optimal electional rule relaxations survive sampling-grid changes; current, with bounded sampled evidence. |
/api/astro/electional-criterion-budget-regret-audit | Find least sampling-sensitive electional rule relaxations by exact minimax regret; current, with bounded sampled evidence. |
/api/astro/electional-criterion-budget-pareto-audit | Enumerate weight-free Pareto-efficient electional rule relaxations; current, with bounded sampled evidence. |
/api/astro/electional-criterion-shapley-audit | Attribute excluded electional samples fairly across interacting criteria; current, with bounded sampled evidence. |
/api/astro/electional-criterion-conflict-core-audit | Find the smallest electional rule combinations that make a window infeasible; current, with bounded sampled evidence. |
/api/astro/electional-criterion-robust-repair-audit | Find the smallest criterion relaxations that work across every sampling grid; current, with bounded sampled evidence. |
/api/astro/electional-criterion-repair-impact-audit | Audit what every minimal cross-grid criterion repair actually admits; current, with bounded sampled evidence. |
/api/astro/electional-criterion-repair-distinction-audit | Prove how every pair of minimal cross-grid criterion repairs differs; current, with bounded sampled evidence. |
/api/astro/electional-criterion-repair-overlap-audit | Classify exact overlap and containment for every minimal repair pair; current, with bounded sampled evidence. |
/api/astro/electional-criterion-repair-hierarchy-audit | Build the exact containment hierarchy of minimal repair consequences; current, with bounded sampled evidence. |
/api/astro/electional-criterion-repair-coverage-audit | Audit exact observation support and single-repair coverage loss; current, with bounded sampled evidence. |
/api/astro/electional-criterion-repair-resilience-audit | Audit exact multi-repair failure tolerance; current, with bounded sampled evidence. |
/api/astro/electional-criterion-repair-loss-frontier-audit | Audit exact worst-case repair-loss damage; current, with bounded sampled evidence. |
/api/astro/electional-criterion-repair-hardening-audit | Audit exact single-repair hardening effects; current, with bounded sampled evidence. |
/api/astro/electional-criterion-repair-hardening-pareto-audit | Compare exact repair-hardening Pareto tradeoffs; current, with bounded sampled evidence. |
/api/astro/electional-criterion-repair-hardening-pareto-hierarchy-audit | Map the exact hierarchy of repair-hardening Pareto profiles; current, with bounded sampled evidence. |
/api/astro/electional-criterion-repair-hardening-regret-audit | Find every least-worst-regret repair-hardening profile; current, with bounded sampled evidence. |
/api/astro/natal-analysis | Configured aspects, midpoint axes, geometric patterns, and strict opt-in sidereal Parashari graha drishti; no interpretation; current. |
/api/astro/planetary-hours | Twenty-four unequal sunrise-based day/night temporal hours and Chaldean rulers; no advice; current. |
/api/astro/place-search | Deterministic self-hosted GeoNames place candidates with versioned IDs and attribution; current. |
/api/astro/timezone-resolve | Pinned historical IANA civil-time resolution with explicit unique, ambiguous, or nonexistent status; current. |
/api/astro/natal-context | Deterministic fact IDs, source paths, fingerprints, and JSON/XML/Markdown artifacts without generated interpretation; current. |
Choose your calculation settings
Western astrology uses the tropical default. Vedic-oriented applications can use sidereal charts and Moon nakshatra/pada data, plus supported D1/D2/D3/D4/D5/D6/D7/D8/D9/D10/D11/D12/D16/D20/D24/D27/D30/D40/D45/D60/D81/D108/D144/D150, Vimshottari through optional depth 4, Indian chart SVG and instant Panchang APIs. Supplemental Vedic systems add Yogini periods, regional calendar factors and North/South Hindu calendar presets with 18 named observances each. These are not complete regional calendars or complete Jyotish analysis. The Houses endpoint's 25-choice inventory supports both zodiacs; Natal SVG supports its 24 twelve-house systems, while Gauquelin remains Houses-only.
- Supply an IANA timezone, such as
Asia/KolkataorAmerica/New_York, when the date and time are local. Omission means UTC. Ambiguous or nonexistent local clock-change times return HTTP 400; send the known UTC instant instead. - Standard civil date strings support
1800-01-01through2200-12-31, inclusive. All date-bearing operations also accept explicit historical inputs; see the historical boundary below. - Chart latitude must be strictly between −90 and 90; longitude ranges from −180 to 180, inclusive. Exact poles and undefined Ascendant geometry return HTTP 400. The Panchang supported has the narrower latitude limit [-88,88]. Supply coordinates directly or use the separate place-search and historical-timezone onboarding workflow; calculation routes never overwrite explicit inputs.
- Legacy chart routes, natal SVG, composite, secondary-progressed planets, solar arcs, lunar nodes, returns and planetary events default to tropical; sidereal mode defaults to Lahiri when
ayanamsais omitted. Planetary-event stations retain tropical motion timing even when reported longitudes are sidereal. Vargas, Vimshottari, Panchang and Indian varga SVG are always sidereal with Lahiri default. The timeline is always sidereal and requires an explicit ayanamsa.
Review the calculation methodology for house models, mean lunar nodes, aspect orbs, and the ephemeris.
Historical dates: 1000 BCE (BC)–2500 CE (AD)
All 77 date-bearing operations accept explicit historical inputs from 1000 BCE (BC) through 2500 CE (AD). The 78th operation, place-search, is date-independent. This includes Western and Vedic calculations, electional audits, Moon phases, eclipses, fixed stars, maps and rendering. Existing search-window, polar-geometry and resource limits still apply; a historical date range is not a promise that every geographic configuration or export format is valid.
Numerology requires an explicit year_convention: displayed_year_digits (1000 BCE uses 1000) or astronomical_year_digits (1000 BCE uses the digits of −999; 1 BCE uses 0). The minus sign is not a digit. These are symbolic choices, not established ancient practices, and numerology has no astronomical time scale. Timezone and readiness tools require a caller-supplied UT1 convention; modern city data does not establish ancient legal time.
Use era: "BCE" or era: "CE", a positive year with no year zero, and an explicit proleptic_gregorian or proleptic_julian calendar. Historical input requires UT1 or an explicit fixed UT1 offset; UTC and IANA zones are not accepted in this mode. Never assume a modern timezone applied in antiquity.
See the historical input example and timekeeping caveats and each operation's OpenAPI schema. The same bodies work through MCP. DE441 supplies ancient positions and DE440 supplies the later range; ancient timekeeping and model uncertainty remain explicit. Houses may be undefined, searches remain bounded, and coverage is not full-range independent accuracy certification.
Quotas, errors, and retries
Free includes 500 standard requests per UTC calendar month; Developer (the API's
basic plan) includes 10,000; Pro includes 100,000 plus 1,000 separate
timeline units. Quotas reset at the UTC month boundary, independently of the
subscription renewal date. See plans and pricing.
A request consumes a unit once it passes authentication, admission, and plan/quota checks and reserves usage. Later validation failures, engine errors, or timeouts still consume that unit. Limit your account to two simultaneous calculation requests and validate inputs before sending them.
400: correct the input;401: check the key;402: the timeline requires Pro.429: quota, concurrency, or edge rate limit. RespectRetry-Afterwhen present; a monthly quota limit requires the next reset or a plan change.502,503, or504: dependency failure, temporary busy/maintenance state, or timeout. Use bounded retries with backoff, respectingRetry-After; each retry can consume another unit.- Check the HTTP status before parsing a successful response. Proxy errors are not guaranteed to be JSON.
Integration guides
Explore all six developer projects with runnable code and sample results.