Skip to main content
All Superagents API requests authenticate with a personal access token. Include it as a Bearer token in the Authorization header with every request:
What the token needs:
  • It has to reach the agent, either through All apps and Superagents or by choosing this agent under One app or Superagent.
  • It needs Full access for most endpoints. A Read-only token works only with Get Superagent conversation.
  • Workspace API keys aren’t accepted.
A personal access token acts as you, so you see your own conversation and memories with the agent. Managing the agent’s webhooks also needs editor access to the agent.
Moving from an account API key?Personal access tokens replace account API keys, and from October 15, 2026 you can no longer use an account API key. Replace the api_key: YOUR_API_KEY header with Authorization: Bearer YOUR_PERSONAL_ACCESS_TOKEN. See moving from account API keys.

​
Get an access token

You can create a token from the agent’s developer settings. To create a personal access token for your Superagent:
  1. Open your Superagent.
  2. Click Agent Settings in the sidebar.
  3. Click Developer.
  4. Click Create access token, then follow the steps to create a token that can reach this agent.
See Creating an access token for every option.
Your personal access token acts as your Base44 account. Treat it like a password, don’t share it, and don’t commit it to version control.

​
Example request

This returns your conversation with the agent, creating it the first time you call it. Use its id to send a message.