# Allowed websites

> Why the public booking API needs no key, how allowed websites decide which browsers may book, and how to add your website, staging sites and local development.

Source: https://docs.bifrostorbit.com/booking/developers/allowed-websites/

The public booking API is meant to be called by customers' browsers, so it needs no key, and Booking Orbit has no API keys to create. What protects it is where a call comes from, and the manage token that only the customer gets.

## What needs what

| Call | From your server | From a browser on your website |
| --- | --- | --- |
| Read the location, services, people and free times | Always works | Always works, from any website |
| Hold a time, book, join the waitlist | Always works | Only from an allowed website |
| Read, move or cancel an appointment | With its manage token | With its manage token, from an allowed website |
| Show the widget | | Always works, from any website |

A browser sends the page's origin with each call, such as `https://northwilds.com`. A server sends none, so allowed websites don't apply to it. Your server is still limited per address: see the rate limits in the [public booking API](https://docs.bifrostorbit.com/booking/developers/public-api/).

## Add your website

Admins of the location do this:

1. Open the location's **Settings**.
2. Under **Your website**, set **Website** to your main website, such as `https://northwilds.com`.
3. Under **Other websites**, add every other address your booking screens run on, pressing Enter after each one. For example `https://www.northwilds.com`, a staging site such as `https://staging.northwilds.com`, and `http://localhost:5173` while you build.
4. Choose **Save settings**.

Each entry is an origin: the scheme, the host and the port, without a path. `https://northwilds.com` and `https://www.northwilds.com` are different origins, and so are `http://localhost:3000` and `http://localhost:5173`. A location allows up to 20 websites, counting the main website, so up to 19 other websites.

Changes apply at once.

## Websites built with CMS Orbit

Connecting a CMS Orbit website space to a location under **Linked satellites** adds the space's domains and preview addresses to the location's allowed websites for you. If that would take the location over 20 websites, the space is still connected but its addresses aren't added: remove websites you no longer need under **Settings › Your website**, then add the space's addresses there. See [Linked satellites](https://docs.bifrostorbit.com/booking/everyone/orbit-connections/).

## Manage tokens

The manage token is the last part of an appointment's `manageUrl`, such as `https://app.bifrostorbit.com/booking/m/<token>`. Anyone who has it can read, move and cancel that appointment, within the location's rules, so treat it as the customer's password for it:

- Show it only to the customer who booked, such as on your confirmation page or in your own email.
- Don't put it in analytics, logs or links to other websites.
- It's long and random, so it can't be guessed. Every appointment has its own.
