1. OneAtlas Data Pay-per-order
    1. What Is OneAtlas Data Pay-per-Order?
    2. How do I get Started?
    3. Overview of the ordering sequence
    4. API limitations

OneAtlas Data Pay-Per-Order

Welcome to our OneAtlas Data Pay-Per-Order guides. These guides have been structured to demonstrate the API functionality that OneAtlas Data Pay-Per-Order has to offer. Organised by category, you can find exactly what you are looking for. Whether it is retrieving user information, ordering or tracking your order, we will have the API documentation to help you walk through exactly what you need.

What Is OneAtlas Data Pay-per-Order?

Airbus Defence and Space offers tasking and archive ordering capabilities for all its satellites through API. These capabilities are the exact same as the ones used through the the One Atlas Data portal.

Pléiades Neo vs SPOT / Pléiades

As of today, Pléiades Neo ordering and Pléiades/SPOT ordering are accessible through the same access routes but:

  • are managed through different contrats

  • present some slight differences in the definition of their APIs

This page will provide you with the known limitations of our APIs and give you an overview of the ordering sequence.

Details and specificities are available in dedicated pages:

  • How to retrieve the mandatory information for ordering (contract id, workspace id, product offers, product options)

  • How to order Pléiades Neo archive

  • How to order Pléiades Neo tasking

  • How to order Pléiades & SPOT archive

  • How to order Pléiades & SPOT tasking

How Do I Get Started?

To get started with OneAtlas Data Pay-per-Order, you will require an account and a configured contract. Please contact our Customer Care team

Once set-up, you will need to generate an API key here. Please refer to the dedicated Authentication Guide.
Using you API Key, you will need to get an access token that enables authorization. Authorization refers to the process of determining what permissions an authenticated client has for a set of resources.
For security reasons this access token expires regularly then it’s necessary to renew the authentication process to get a new one.

Overview of the ordering sequence

Step 1: Authenticate
  Retrieve a token using your API key for further actions

Step 2 (for tasking only): Check feasibility
  Know if your request needs to go through manual feasibility study and also get the ‘difficulty’ of your request in case of a automatic OnePlan request:

  • Result of the feasibility can be either AUTOMATIC or MANUAL. If MANUAL, your order will have to go through a quotation process.

  • Difficulty can be either EASY or CHALLENGING (this will impact the price)

Step 3 (for tasking only, limited to OneDay and OneNow offers) : Get attempts
  Get the possible acquisition attempts on the defined areas

Step 4 (optional): Get a price
  Get the price of your order

Note: Price can be calculated ONLY for orders that does not require feasibility study - meaning either archive or AUTOMATIC tasking

Step 5 (optional, for Pléiades Neo only): Request a quotation
  Request a quotation.

Note: Quotations are mandatory only in case of non-AUTOMATIC tasking but can be requested in any cases if necessary

Step 6: Create an order
  Create your order.

Note: You can request quotation even if the result of the feasibility is AUTOMATIC
Note: You can request a manual feasibility study even if the result of the feasibility is AUTOMATIC

Step 7 Access products
  Once delivered, the acquisition will be placed in your private workspace. Images can be downloaded or streamed.

API limitations

Multi-aoi / multi-item

Our order API does support multi-aoi / multi item BUT will be limited to 5 couples aoi / item
Even if it is possible, to simplify the integration and the tracking of your API requests, we suggest to keep 1 order / 1 area / 1 product offer

Note: Note that this limitation is not implemented yet (beta version)

Minimum surface

Our order API does not support production under 5km² nor less than 1km broad

  • This limitation is technical and allows to ensure the quality of the product

  • In any cases, minimal surface for invoicing is 100 km² for tasking, 25km² for archive

Note: Note that this limitation is not implemented yet (beta version)

Complex areas

Our API does not support complex areas. 999 maximum, no intersection.

Note: Note that this limitation is not implemented yet (beta version)


As of today (beta version), our order API does not support well parallel requests

  • We have planned to lift this limitation as soon as possible with the implementation of a new version of our /orders API

  • As a conservative measure, we ask you to perform 1 request at a time

Rate limiting

In order to protect our system, please be aware that we have implemented rate limiting on our APIs.
Rate limiting is 1 req/s with a ban time of 10 minutes for all ordering APIs.

Contact Us