ISRO API

Free community ISRO API with no key: lists of Indian spacecraft, launchers, centres and customer satellites as simple JSON. No account, no rate limit, tiny responses.

No API key requiredCORS enabledHTTPSFree tier

Endpoint tested and returned HTTP 200 on 2026-08-21

What is the ISRO API?

The ISRO API is a free, key-free community project serving lists of Indian Space Research Organisation spacecraft, launch vehicles, centres and customer satellites as plain JSON. It is an unofficial mirror of information published on ISRO's website, not an ISRO service.

There is no official ISRO developer API, so this community project fills the gap by transcribing ISRO's published lists into four small JSON endpoints: spacecraft, launchers, centres and customer satellites. The spacecraft list runs from Aryabhata in 1975 through to current missions, each entry just an id and a name — enough to populate a picker, seed a quiz, or drive a timeline, and not much more.

Set expectations accordingly. This is a static dataset maintained by a volunteer and deployed on free hosting, with no versioning, no changelog and no service level. It is genuinely useful for teaching material, hobby dashboards and anything where a hand-curated list beats scraping, and genuinely unsuitable as a dependency for anything that must not break. If you need launch data with dates, outcomes and payloads, a maintained launch-tracking API will serve you far better; if you need an authoritative record of Indian missions, ISRO's own site remains the source.

Quick facts

Base URL: https://isro.vercel.app/api
Authentication: No API key or account. This is an unofficial community project and carries no affiliation with or endorsement from ISRO.
Rate limit: None published. Responses are small and static, so caching them once is the polite approach.
Pricing: Free. The underlying facts are drawn from ISRO's public website.
CORS: Enabled — callable directly from browser JavaScript
Official docs: Read the docs

How to use the ISRO API

Every request below was executed against the live API on 2026-08-21, and the response shown is the real body it returned — not an illustration.

1. List every ISRO spacecraft

GET https://isro.vercel.app/api/spacecrafts

curl

curl 'https://isro.vercel.app/api/spacecrafts'

JavaScript (fetch)

const res = await fetch("https://isro.vercel.app/api/spacecrafts");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();
console.log(data);

Python (requests)

import requests

res = requests.get("https://isro.vercel.app/api/spacecrafts", timeout=20)
res.raise_for_status()
print(res.json())

Response — HTTP 200 (truncated)

{
  "spacecrafts": [
    {
      "id": 1,
      "name": "Aryabhata"
    },
    {
      "id": 2,
      "name": "Bhaskara-I"
    },
    {
      "id": 3,
      "name": "Rohini Technology Payload (RTP)"
    },
    {
      "id": 4,
      "name": "Rohini Satellite RS-1"
    },
    {
      "id": 5,
      "name": "Rohini Satellite RS-D1"
    },
    {
      "id": 6,
      "name": "APPLE"
    },
    {
      "id": 7,
      "name": "Bhaskara-II"
    },
    {
      "id": 8,
      "name": "INSAT-1A"
    },
    {
      "id": 9,
      "name": "Rohini Satellite RS-D2"
    },
    {
      "id": 10,
      "name": "INSAT-1B"
    },
    {
      "id": 11,
      "name": "SROSS-1"
    },
    {
      "id": 12,
      "name": "IRS-1A"
    },
    {
      "id": 13,
      "name": "SROSS-2"
    },
    {
      "id": 14,
      "name": "INSAT-1C"
    },
    {
      "id": 15,
      "name": "INSAT-1D"
    },
    {
      "id": 16,
      "name": "IRS-1B"
    },
    {
      "id": 17,
      "name": "SROSS-C"
    },
    {
      "id": 18,
      "name": "INSAT-2A"
    },
    {
      "id": 19,
      "name": "INSAT-2B"
    },
    {
      "id": 20,
      "name": "IRS-1E"
    },
    {
      "id": 21,
      "name": "SROSS-C2"
    },
    {
      "id": 22,
      "name": "IRS-P2"
    },
    {
      "id": 23,
      "name": "INSAT-2C"
    },
    {
      "id": 24,
      "name": "IRS-1C"
    },
    {
      "id": 25,
      "name": "IRS-P3"
    },
    {
      "id": 26,
      "name": "INSAT-2D"
    },
    {
      "id": 27,
      "name": "IRS-1D"
    },
    {
      "id": 28,
      "name": "INSAT-2E"
    },
    {
      "id": 29,

Parameters

Parameter	Type	Required	Description
`(endpoint) /spacecrafts`	path	Optional	Every ISRO spacecraft as an id and name pair. `/api/spacecrafts`
`(endpoint) /launchers`	path	Optional	Launch vehicles including SLV, ASLV, PSLV, GSLV and LVM3 variants. `/api/launchers`
`(endpoint) /customer_satellites`	path	Optional	Foreign satellites launched by ISRO on a commercial basis. `/api/customer_satellites`
`(endpoint) /centres`	path	Optional	ISRO centres and units with their locations. `/api/centres`

Response fields

spacecrafts[]array: Array of spacecraft objects. The whole payload is this one key.
spacecrafts[].idinteger: Sequential index. Positional, not a stable ISRO identifier — do not treat it as a key across versions.
spacecrafts[].namestring: Mission or satellite name, for example `Aryabhata` or `INSAT-1A`.
launchers[] / centres[] / customer_satellites[]array: The other endpoints follow the same shape with their own fields.

What you can build with the ISRO API

Populate a dropdown of Indian missions in an educational app
Seed a quiz or trivia game about the Indian space programme
Build a simple mission timeline visualisation
Provide autocomplete for a space-history search box
Teach REST basics with a small, predictable JSON payload

Common errors and how to fix them

404

Endpoint path misspelled.

Fix: Note the pluralisation: `/spacecrafts` and `/launchers`, and `/customer_satellites` with an underscore.

Service unavailable

The project runs on free serverless hosting.

Fix: Cache the responses locally. They change rarely enough that a periodic refresh is more than sufficient.

Missing recent missions

The dataset is updated manually and can lag.

Fix: Cross-check against ISRO's own site for anything time-sensitive; this is a convenience mirror, not a live feed.

ISRO API — frequently asked questions

Is this an official ISRO API?

No. ISRO does not publish a developer API. This is an unofficial community project that transcribes ISRO's published lists into JSON, with no affiliation to or endorsement from the agency.

Does the ISRO API need a key?

No key, no account and no rate limit. The endpoints return small static JSON documents that are cheap to fetch and easy to cache.

What data does it actually contain?

Four lists: spacecraft, launch vehicles, ISRO centres and customer satellites launched commercially. Each entry is minimal — typically an id and a name — so it suits pickers and timelines rather than detailed mission analysis.

Is there a better source for Indian launch data?

For launch schedules, outcomes and payload details, a maintained launch-tracking API covers ISRO alongside every other agency and is updated continuously. This API's advantage is simplicity, not depth.

Tools that pair with this API

JSON Formatter

Format, beautify and minify JSON online with 2-space, 4-space or tab indentation. Sort keys alphabetically and catch syntax errors instantly — free and private.

JSON to CSV Converter

Convert a JSON array of objects to CSV online. Automatic column headers from the union of all keys, delimiter choice and proper quoting — all in-browser.

JSON Viewer

View JSON as a collapsible interactive tree online. Expand and collapse nodes, search keys and values, and copy the JSONPath of any node privately.

ISRO API is an independent third-party service and is not affiliated with ByteTools or ByteVancer. Details on this page were verified on 2026-08-21; always check the official documentation before relying on this API in production, as terms and limits can change.