An API token lets another system (a channel manager, your own website, an automation tool) use the Overviu API on behalf of your team. Each token belongs to the team you’re in, not to you.
Every member of the team can create and revoke its tokens.
Anyone with a token can read your team’s listings, bookings and guests through the API, and change bookings. Keep tokens on servers you trust, never in a web page or an app guests download.
The Scope isn’t enforced yet: a Read-only token can also create, change and cancel bookings.
Create a token
Switch to the team
Use the team switcher to switch to the team the token is for.
Open API tokens
Open the user menu → Settings → API tokens.
Name it
Give it a Name that says where it’s used, like “Channel manager”, pick a Scope (Read-only or Read-write), and click Create token.
Copy it
The token appears under Existing tokens. Click the eye icon to show it and the copy icon to copy it, and paste it into the other system. You can come back and copy it again later.
Revoke a token
Click Revoke next to it. Systems using it stop working straight away. Revoke a token when you stop using a system, or if it may have been seen by someone it shouldn’t.
Next
The API reference shows how to send a token and every endpoint you can call with it.
