Airbus Catalog API

The Catalog API from Airbus — 1 operation(s) for catalog.

Operations 1

GET /api/v1/opensearch Catalog OpenSearch (Living Library and archives) #

Specifications

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/airbus-catalog-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

airbus-catalog-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Airbus OneAtlas API () Authentication Catalog API
  version: '1.0'
  description: 'Best-effort OpenAPI 3.1 representation of the Airbus OneAtlas developer

    portal authentication and core catalog touch points, derived from

    https://api.oneatlas.airbus.com/. OneAtlas exposes multiple product APIs

    (OAD Living Library, Pay Per Order Archives, Pay Per Order Tasking, Basemap,

    Radar & Elevation) which share a Keycloak-based access token flow. Only

    the authentication endpoint and high-level catalog grouping are documented

    here because the underlying product endpoint paths are not enumerated in

    public introductory material.

    '
  contact:
    name: Airbus OneAtlas
    url: https://api.oneatlas.airbus.com/
servers:
- url: https://authenticate.foundation.api.oneatlas.airbus.com
  description: OneAtlas Keycloak authentication
- url: https://search.foundation.api.oneatlas.airbus.com
  description: OneAtlas catalog search service
- url: https://data.api.oneatlas.airbus.com
  description: OneAtlas data API service
security:
- BearerAuth: []
tags:
- name: Catalog
paths:
  /api/v1/opensearch:
    get:
      tags:
      - Catalog
      summary: Catalog OpenSearch (Living Library and archives)
      description: 'Search OneAtlas satellite imagery catalog using OpenSearch parameters

        such as `bbox`, `startDate`, `endDate`, `productType`, `cloudCover` and

        `constellation`. Requires bearer token authentication.

        '
      operationId: openSearchCatalog
      parameters:
      - name: bbox
        in: query
        schema:
          type: string
      - name: startDate
        in: query
        schema:
          type: string
          format: date-time
      - name: endDate
        in: query
        schema:
          type: string
          format: date-time
      - name: productType
        in: query
        schema:
          type: string
      - name: cloudCover
        in: query
        schema:
          type: string
      - name: constellation
        in: query
        schema:
          type: string
      responses:
        '200':
          description: OK
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: 'Bearer access token obtained via POST

        /auth/realms/IDP/protocol/openid-connect/token with grant_type=api_key.

        '