How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

LeoLabs catalog API

LeoLabs catalog of tracked LEO objects, their measurements, states and propagations.

LeoLabs catalog API is one of 2 APIs that LeoLabs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Catalog. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 11 operations across 11 paths, and defines 10 schemas. It is described by OpenAPI 3.0.3, at version v1.

Requests are made against a single base URL, https://api.leolabs.space/v1.

11 operations 11 paths 10 schemas 10 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
v1
Base URL
https://api.leolabs.space/v1
Authentication
API Key
Resource Areas
1

Authentication & Security 1

LeoLabs catalog API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (leolabsKeyPair). By default, every request must be authenticated.

  • leolabsKeyPair — LeoLabs access key / secret key pair, sent as Authorization: basic : . Despite the basic prefix this is not RFC 7617 HTTP Basic — the LeoLabs client sends the…

Paths & Operations 11

Across 11 paths, the API surfaces 11 operations — 10 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

catalog 11

LeoLabs catalog of tracked LEO objects, their measurements, states and propagations.

GET
/catalog/objects
List catalog objects
listCatalogObjects → 200401
GET
/catalog/objects/search
Search the catalog by NORAD catalog number
searchCatalogObjects 1 param → 200401
GET
/catalog/objects/{catalogNumber}
Get a catalog object
getCatalogObject 1 param → 200401
GET
/catalog/objects/{catalogNumber}/measurements
List radar measurements for a catalog object
listCatalogObjectMeasurements 3 params → 200401
POST
/catalog/objects/{catalogNumber}/tasks
Request priority tasking for a catalog object
createCatalogObjectTask 1 param body → 200401
GET
/catalog/objects/{catalogNumber}/passes/planned
List planned passes for a catalog object
listCatalogObjectPlannedPasses 1 param → 200401
GET
/catalog/objects/{catalogNumber}/statistics
Get statistics for a catalog object
getCatalogObjectStatistics 1 param → 200401
GET
/catalog/objects/{catalogNumber}/states
List orbital state vectors for a catalog object
listCatalogObjectStates 4 params → 200401
GET
/catalog/objects/{catalogNumber}/states/{stateId}
Get an orbital state vector
getCatalogObjectState 2 params → 200401
GET
/catalog/objects/{catalogNumber}/states/{stateId}/tles
List TLEs associated with a state vector
listCatalogObjectStateTles 2 params → 200401
GET
/catalog/objects/{catalogNumber}/states/{stateId}/propagations
Propagate ephemeris from a state vector
getCatalogObjectStatePropagation 5 params → 200401

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Measurement (17 properties), State (9 properties), MeasurementValues (7 properties), Propagation (6 properties). Each schema is shown below with its type and property counts.

MeasurementCorrection
object
A correction applied to a raw measurement.
4 properties
Propagation
object
A propagated ephemeris derived from a state vector.
6 properties
Tle
object
A two-line element set derived from a LeoLabs state vector.
1 property
StateFrame
object
Position, velocity and covariance in a single reference frame.
4 properties
State
object
An orbital state vector for a catalog object.
9 properties
Measurement
object
A single radar measurement of a catalog object.
17 properties
CatalogObject
object
An object tracked in the LeoLabs LEO catalog.
3 properties
MeasurementValues
object
Raw or corrected radar observables for a measurement.
7 properties
TaskRef
object
A reference to a created tasking request.
1 property
Error
object
Error envelope. The official LeoLabs client falls back to {"error": "unknown"} when a failed response body cannot be parsed as JSON, indicating a top-level err…
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leo-labs-catalog-api-openapi.yml Raw ↑

Other APIs LeoLabs publishes across the network.

LeoLabs instruments API
Where this information came from

This is an independent, third-party profile of LeoLabs catalog API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.