Skip to content

OKAPI Platform

Product Overview

Our Satellite Operator product offers two packages. The first analysis close approaches for you. Using beyond state-of-the-art algorithms we analyze conjunctions and classify them. The second package safeguards your satellite by suggesting action if needed. The table below highlights the services that are included in the packages.

       Feature        |                   Description                     |         Package
 Space-Track CDMs     | This feature automatically downloads  CDMs from   | Risk Monitoring Service
                      | Space-Track and introduces them into our platform.|
                      | CDMs are grouped into events.                     |
  Add Satellite       | Add satellites to the company. Contains Noard Id, | Risk Monitoring Service
                      | cross section, mass, Info on propulsion system,   |
                      | Info on accepted risk levels.                     |
 Risk estimation      | Re-computes close approach based on user defined  | Risk Monitoring Service
                      | input data. Groups risk based on provided accepted|
                      | risk levels and collision avoidance strategy.     |
 Maneuver Generation  | Computes manoeuvres for critical conjunctions     |   Collision Avoidance Service
                      | based on satellite definition and defined         |
                      | avoidance strategy.                               |
 Avoidance Check      | Checks computed avoidance manoeuvres against      |   Collision Avoidance Service
                      | catalogue for further conjunctions.               |
 Maneuver Check       | Checks any manoeuvre provided aginst catalogue    |   Collision Avoidance Service
   (only API)         | for futher conjunction.                           |
                      |                                                   |
 Orbit propagation    | Propagates an initial state over time using either|   Collision Avoidance Service
   (only API)         | Neptune or Orekit numerical propagators or the    |
                      | analytical orbit theory SGP4.                     |
 Pass Prediction      | Computes the visibility of one object over a      |   Collision Avoidance Service
   (only API)         |  location on ground based on propagated states    |

Web Interface

Sign up

To get access to our platform, you have to create an account. With this account you have access to the endpoints described above. To create the account, go to the sign-up page.

Landing page

You have to sign up once, and confirm your email address. Afterwards, you can start using the OKAPI platform via the GUI and its API.

The OKAPI platform landing page is publically reachable and can be viewed without an account. It displays the most recent space object population around Earth. The source is the public general perturbations catalogue available from It shows the population live and updates the position accordingly.

You can rotate around the center of the coordinate system, which at the start is the Earth.

Each object can be selected with single click and details of the object are viewed.

When clicking twice on an object the camera perspective is changed the object is placed at the center of the coordinate system. You can now rotate the view around the selected object.

On the top right you can log in to the private side of the platform. Choosing Sign Up in the dialog brings you to the sign up page as discussed in the Sign up section. Log in with your credentials for accessing all functionalities.


You can manage your satellites you want safeguarded by our services via the Satellite page. It let's you define your system, which is operational on orbit an already has a Norad Id (= unique identifies for your satellite, also called Satellite Catalogue Number), as assigned to your spacecraft by USSPACECOM.

By clicking Add new you will be able to define the parameters of your spacecraft. The name will be retrieved as the connection is made to our data sources in the background. For the close approach analysis and risk estimation service, as well as the extrapolation of your orbit we ask for your input on the Mass and Cross sectional area of your satellite.

In addition we need to know the thruster's capabilities, starting with the Thrust in N. If you have very detailed information you can also provide the Thrust uncertainties and the Pointing uncertainties you encounter. This will help us to optimize our maneuver suggestions.

Next you need to choose which Maneuver strategy you would like to use. Depending on your thrust capabilities either short-term or long-term strategies can be applied. For the short-term strategy we consider increasing the radial distance in cirtical encounters. For the long-term strategy we will increase the along-track miss distance. This strategy can be applied, when the avialable thrust is low and an early maneuver decision must be made. The next two fields let you customize the classification process based on the Accepted collision probability and Minimum miss distance. Both are considered when analysing close approaches. When either of the limits are reached or exceeded a close approach is classified as critical.

Last we need to know whether you have already a SSA sharing agreement in place with the 18th SPCS. This allows us to interchange orbital data which are made available by USSPACECOM. We assist you in this setup phase.


Once the setup is finished and we receive information on your spacecraft conjunction warnings are avialable. They are colored red, when they are classified as critical and yellow, when the event is under observation.

You can see the details of the conjunction when clicking on it. In the center the Time to closest approach is shown as a count down to the event. Next to it you see the event geometry. No worries, more information will soon be visible in the 3D view. The diagram below shows how the collision probability evolves. It shows our estimation with the information you supplied on your satellite and information from our external partners. It also shows the original estimation as provided by 18th SPCS.

Below you find suggested maneuvers, which you can download for review. They have been screened by us against the SP catalogue 18th SPCS. If you choose to perform a maneuver we will upload the data also them so that other operators are also aware of your actions.


All features you can observe in the web interface are also available via API, so your operation systems can directly be interfaced in a machine-to-machine manner with our platform. Our services are accessible via a REST API. This means that you can communicate with it via http commands. Currently supported are POST, GET, UPDATE and DELETE methods. Send a POST request to our server to start a calculation, e.g. an orbit propagation or pass prediction computation. Once the computation is done, the results are collected by sending a GET request. All available endoints can be found in our API documentation.

OKAPI provides connectors to simplify the communication with the platform. They are provided as open source software hosted on GitHub. They enable an easy access to the platform services. They are avialable for Python, Java, C++ and Matlab. Using the connectors simplifies the API use, as they take over all REST-API communications and also provide convenience methods. Examples are also given for using OKAPI orbits via wget from bash or Powershell.

Prerequisites: Before going though the introductions below, make sure that you have an OKAPI account.

Security and Privacy

The OKAPI platform uses auth0 as identity provider. All registered user data reside in a safe database. The OKAPI services use an OAuth 2.0 password grant type, which results in an access token based on your credentials. It is then used by applications to authenticate to gain access to the platform and use OKAPI services.

During the sign up for our platform and services you have to take notice of our privacy policy. The Auth0 statement can be found in the Data protection provisions about the application and use of Auth0