# Portal session token

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](https://docs.bunny.com/developer/getting-started/api#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](https://docs.bunny.com/developer/integrate/enable-upgrades-and-payments/standalone-customer-portal). The account is baked into the portal session token, therefore there is no `accountId` is needed when making requests.

### Differences

|                      | Data Access    | Can use scopes?      |
| -------------------- | -------------- | -------------------- |
| API Token            | Entire entity  | :white\_check\_mark: |
| Portal Session Token | Entire account | :x:                  |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bunny.com/developer/portal-session-token.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.