Makini
User Guide
API ReferenceMCPPlatforms
User Guide
API ReferenceMCPPlatforms
Website
  1. Getting Started
  • Changelog
  • Getting Started
    • On-premise systems
    • Authentication
    • Testing with API Tools
    • Account setup
    • Connection Credits
  • Core Concepts
    • Connections
    • Unified Data Model
    • Custom mappings
    • Data mappings
    • Sync schedules and history
  • Admin API
  • Account & Team
    • Team access and SSO
  • Makini Link
    • Embedded connection settings
    • Launching Makini Link
    • Magic links
  • Management API
    • Management API authentication
    • Managing connections
    • Managing your application
  • Webhooks
    • Signatures and retries
    • Webhook events
  • Working with the API
    • Access tokens
    • Errors
    • Filtering
    • Makini Query Language
    • Raw data and passthrough
    • Reading data
    • Relations and expand
    • Writing data
  1. Getting Started

Authentication

Makini uses standard OAuth 2.0 bearer tokens. Every request carries one in the Authorization header, and the kind of token decides what it can reach.

Two kinds of token#

Connection token
Reads and writes the data of one connection on https://api.makini.io/v4. The connection comes from the token, so a request never names one.
Get it through the Makini Link OAuth flow (authorization_code, with a refresh token), or from the dashboard: Connections, then the Generate a token icon on a connected row.
Management API token
Manages your account through the Management API at https://api.makini.io/mgmt: create and list connections, register webhooks, and more.
Get it with the client_credentials grant, using your client ID and secret.
Least privilege by design: a connection token reaches only its own connection, and a Management API token manages your account but never reads connection data.

Your client credentials#

Open Settings → Application in the dashboard. You'll find:
Client ID: your application's public identifier.
Client secrets: click Generate secret to create one. A secret is shown once, when you create it, so store it right away. You can hold several at a time: generate a new one, switch your integration over, then revoke the old one.
Redirect URIs: where Makini Link sends your users back with an authorization code. Makini matches them exactly. A URI may use * for a whole subdomain or path segment, such as https://*.example.com/callback.
Keep client secrets on your server. Never put them in browser code, mobile apps or public repositories.

Token lifetimes#

Access tokens last 1 hour. An expired token answers 401.
A Makini Link token comes with a refresh token that rotates on every use. Always store the newest one.
A dashboard token is for testing: it lasts 1 hour and has no refresh token. Generate a new one when it expires.
A client_credentials token has no refresh token. Request a new one when it expires.

Next steps#

Access tokens: grants, refresh rotation and revocation in detail.
Launching Makini Link: send your users through the connect flow.
Management API authentication: get a token for the Management API.
Modified at 2026-10-16 14:20:36
Previous
On-premise systems
Next
Testing with API Tools
Built with