This guide is for agents and custom integrations that call Utin’s HTTP API directly. You create a personal access token and store it in the agent’s secure key storage.
Want the easiest setup? For most agents, use the Utin MCP server. It uses browser sign-in, so there is no API key to create or copy. Continue here if your agent or integration needs direct access to the API endpoints.
What you’ll achieve
You’ll have an authenticated API client that can list the companies, workspaces and accounts available to it.
Before you start
You need a Utin account and an agent or integration that can store an API key securely outside the conversation.
1. Connect your accounts in Utin
Open Add Connections and connect the social or advertising accounts you want to use. Complete the provider sign-in in Utin.
2. Limit access
A Utin token has the same access as the person who creates it. Use a team member whose permissions fit the work you want the agent to do. For example, reporting does not require access to publishing or messages.
3. Create the token
Open Account → View profile → Personal access tokens and select Create token.
Copy the token into the agent’s secure key storage. Do not paste it into a normal chat, email or shared document. You can revoke the token in Utin at any time.
Send the token with direct API requests as an authorization header:
Authorization: Bearer <personal access token>
The current API description is available at https://app.utin.no/openapi, with an interactive explorer at https://app.utin.no/openapi/ui.
4. List what the agent can access
Ask the agent or integration to return the companies, workspaces and connected accounts available to the token owner.
Prompt to copy
List the companies, workspaces and connected accounts available to you in Utin.
5. Choose where to work
Choose a company and workspace from the list, then use that workspace in the next request. If something you expected is missing, check the account under Add Connections in Utin.
Good to know
The token only gives access to what its owner can already see and do in Utin. Social and advertising accounts are connected or reconnected from the Utin interface.
If something does not work
- Not authorized: check that the request uses the complete token with the
Bearerprefix. Create a replacement if the token was revoked or exposed. - A workspace is missing: check that the token owner can access it in Utin.
- An account is missing: check its status under Add Connections, then request the list again.
What to read next
Developers can use the Utin API companion for supported operations and platform details. To continue with a practical workflow, learn how to publish posts with an agent.
Working directly in the app? Read Connect an AI assistant through MCP.