Portal session token
Use a portal session token instead of an API token to limit Bunny Components to a single account's data, and compare the two token types.
So far we have covered how to use a regular api token. But what if you want to restrict api access to just a single account? Then you should use a portal session token.
Two kinds of tokens:
- API token: Use an API token when you want all of your Bunny data to be accessible to the components. Create an API Client.
- Portal Session Token: Use a portal session token when you only want data for a single Bunny account to be accessible to the components. Create a Portal Session. The account is baked into the portal session token, therefore there is no
accountIdis needed when making requests.
Differences
| Data Access | Can use scopes? | |
|---|---|---|
| API Token | Entire entity | :white_check_mark: |
| Portal Session Token | Entire account | :x: |