# Get started as a developer

> How Bifröst Orbit fits together for developers: one sign-in, organisations, satellites with their own APIs and keys, and where each satellite's developer docs are.

Source: https://docs.bifrostorbit.com/orbit/developers/get-started/

Bifröst Orbit is a set of tools, called satellites, behind one sign-in. Orbit itself holds the people, the organisations and how they sign in. Each satellite, such as CMS Orbit or Commerce Orbit, holds its own data and has its own APIs.

As a developer you mostly work with one satellite at a time: you read Northwilds' pages from CMS Orbit, list its trips from Travel Orbit, or send its orders to an ERP from Commerce Orbit. This section covers what is the same across all of them.

## How it fits together

| Part | What it is | What it means for you |
| --- | --- | --- |
| **Orbit** | The platform at `app.bifrostorbit.com`. People sign in here once, with an email code, Microsoft or Google. | Orbit has no public API of its own. Your code talks to satellites. |
| **Organisation** | A company using Bifröst Orbit, such as Northwilds. Each has an id (24 hexadecimal characters) and a short name used in its sign-in address, such as `northwilds`. | Every key, token and event belongs to one organisation. |
| **Satellites** | CMS, Careers, Commerce, Travel, Booking, Presence and Insights Orbit. Each runs at its own path, such as `app.bifrostorbit.com/cms`. | Each has its own keys, roles, limits and docs. A key from one satellite never works in another. |
| **Inside a satellite** | Most satellites divide an organisation further: CMS Orbit into spaces and environments, Commerce Orbit into shops, Travel Orbit into brands, Booking Orbit into locations. | A key usually belongs to one of these, not to the whole organisation. |
| **Orbit Exchange** | The hub that carries events between satellites, such as `commerce.order.paid`. | You can't read from it directly. Webhooks in Orbit send its events to your systems. See [Webhooks from Orbit](https://docs.bifrostorbit.com/orbit/developers/orbit-webhooks/). |

An organisation's owners and admins decide in Orbit who may open which satellite. Each satellite then has its own roles, such as Developer in CMS Orbit, which decide who may create keys. See [How access works](https://docs.bifrostorbit.com/orbit/everyone/how-access-works/).

## Where each satellite's developer docs are

| Satellite | What you can build | Start here |
| --- | --- | --- |
| CMS Orbit | Websites and apps that read pages, menus and campaigns, with SDKs for JavaScript, PHP, Swift and Kotlin | [How CMS Orbit works](https://docs.bifrostorbit.com/cms/developers/how-it-works/) |
| Careers Orbit | Job lists and applications on your website, and connections to HR systems | [Get started](https://docs.bifrostorbit.com/careers/developers/get-started/) |
| Commerce Orbit | Shops on your own website, checkout through your Stripe, and orders sent to your systems | [Get started](https://docs.bifrostorbit.com/commerce/developers/get-started/) |
| Travel Orbit | Trips and bookings on your own website | [Get started](https://docs.bifrostorbit.com/travel/developers/get-started/) |
| Booking Orbit | Appointment booking on your website or through an AI assistant | [Booking Orbit for developers](https://docs.bifrostorbit.com/booking/developers/mcp/) |
| Insights Orbit | Analytics on your website and app, events from your servers, and the numbers through an API | [Get started](https://docs.bifrostorbit.com/insights/developers/get-started/) |
| Presence Orbit | Reviews on your website with the review widget | [Widgets](https://docs.bifrostorbit.com/presence/everyone/widgets/) |

## What is the same everywhere

- **Keys are per satellite.** Admins create them in the satellite, under **API keys**. Each is shown once. See [API keys and organisations](https://docs.bifrostorbit.com/orbit/developers/api-keys-and-organisations/).
- **Addresses follow one pattern.** The website APIs of CMS, Careers and Insights Orbit are on `api.bifrostorbit.com`; everything else is on `app.bifrostorbit.com` under the satellite's path. Staging has its own addresses. See [API addresses](https://docs.bifrostorbit.com/orbit/developers/api-addresses/).
- **Errors are JSON.** REST answers carry `{ "error": { "code": "…", "message": "…" } }`; GraphQL answers carry `errors` with `extensions.code`.
- **Too many requests answer `429`**, with the code `rate_limited`. Each satellite sets its own limits. See [Rate limits](https://docs.bifrostorbit.com/orbit/developers/rate-limits/).
- **Webhooks are signed with HMAC-SHA256.** CMS, Careers and Commerce Orbit send them, in two header styles. See [Verify webhooks from Bifröst Orbit](https://docs.bifrostorbit.com/orbit/developers/verify-webhooks/).
- **AI assistants sign in with OAuth.** Every satellite has an MCP server that an assistant connects to as a person on the team. See [Sign in with Orbit](https://docs.bifrostorbit.com/orbit/developers/sign-in-with-orbit/).

## Your first request

1. Ask an admin of your organisation to open CMS Orbit, choose the space and environment for your website, and create a public key under **API keys**. It starts with `cms_pk_`.
2. Read the home page:

```bash
curl -H "Authorization: Bearer cms_pk_…" \
  "https://api.bifrostorbit.com/cms/v1/content?url=/"
```

3. Carry on in [Connect a website](https://docs.bifrostorbit.com/cms/developers/connect-a-website/), or in the developer docs of the satellite you are building for.
