Skip to content
API Reference/Authorization/
Obtain access token

Fondo Partner API (2.0.0)

Overview

This API is intended for registered partners in agreement with Fondo.

The API is subject to change.

Download OpenAPI description
api_3.0.3.json
api_3.0.3.yaml
Overview
E-mail
tech@fondo.se
License
Proprietary
Languages
Servers
Mock server
https://docs.fondo.se/_mock/openapi/api_3.0.3
Production
https://api.fondo.se
Sandbox
https://api.sandbox.fondo.se

Authorization

Obtain and manage access tokens via OAuth 2.0 Client Credentials. Send grant_type=client_credentials with your client_id and client_secret. Use the returned access_token in Authorization: Bearer <token>. Tokens are short-lived—reuse during validity and renew on expiry.

Operations

Obtain access token

Request

Issues a short-lived bearer token using OAuth 2.0 Client Credentials. Send grant_type=client_credentials with your client_id and client_secret (optionally scope, state). Use the returned access_token in the Authorization: Bearer header on subsequent requests. The response also includes expires_in (seconds) and echoes state when provided.

Bodyapplication/x-www-form-urlencoded

An AUTH token request

grant_typestringrequired
Value"client_credentials"
client_idstringrequired

The Client ID provided by Fondo

client_secretstringrequired

The Client Secret provided by Fondo

scopestring

Comma separated list of scopes.

Example: "`account:read, account:write`\n"
statestring

Client state. For example a base64 encoded string of state data.

Example: "VGhpcyBpcyBteSBzdGF0ZS4gVGhlcmUgYXJlIG1hbnkgbGlrZSBpdCwgYnV0IHRoaXMgaXMgb25lIG1pbmUu"
curl -i -X POST \
  https://docs.fondo.se/_mock/openapi/api_3.0.3/v2/partner/auth/token \
  -H 'Content-Type: application/x-www-form-urlencoded' \
  -d grant_type=client_credentials \
  -d client_id=string \
  -d client_secret=string \
  -d 'scope=`account:read, account:write`
' \
  -d state=VGhpcyBpcyBteSBzdGF0ZS4gVGhlcmUgYXJlIG1hbnkgbGlrZSBpdCwgYnV0IHRoaXMgaXMgb25lIG1pbmUu

Responses

Auth token response

Bodyapplication/json
access_tokenstringrequired

access_token to use for subsequent requests

Example: "ffe74ba1-99a8-46e3-9ba2-9c0ef72e13c1"
expires_innumberrequired

The lifetime in seconds of the access token. Default is 432000 (5 days)

Example: 432000
statestring

Client state. For example a base64 encoded string of state data.

Example: "VGhpcyBpcyBteSBzdGF0ZS4gVGhlcmUgYXJlIG1hbnkgbGlrZSBpdCwgYnV0IHRoaXMgaXMgb25lIG1pbmUu"
Response
application/json
{
  "access_token": "ffe74ba1-99a8-46e3-9ba2-9c0ef72e13c1",
  "expires_in": 432000,
  "state": "VGhpcyBpcyBteSBzdGF0ZS4gVGhlcmUgYXJlIG1hbnkgbGlrZSBpdCwgYnV0IHRoaXMgaXMgb25lIG1pbmUu"
}

Accounts

Accounts hold investor positions, balances, and cash movements under a client. Endpoints let you list accounts, fetch details, and close accounts. Responses include status, owner info, currency, linked bank accounts, positions, and timestamps.

Operations

Agreements

Retrieve account agreements and generate PDF documents for account-related contracts.

Operations

AllocationPlan

Allocation plans

Operations

Clients

A client is your legal entity (B2B) or grouping for end-investor accounts. Use these endpoints to list, create, read, and update clients, manage bank accounts and service types, and fetch client-specific resources (instruments, custodians).

Operations

Custodians

Fetch custodians linked to a client—useful for transfer instructions and operational routing. Returns identifiers and names for display and validation.

Operations

Journeys (Hosted Flows)

Journeys are secure, hosted web flows for customer interactions: account opening (e-sign), KYC/KYB questionnaires, fund transfers, and allocation plan setup. Create a Journey via API, redirect customers to the time-limited URL, and poll/callback for results.

Operations

Instruments

The instrument universe consists of mutual funds available for a given client or globally. Retrieve instrument metadata: identifiers (e.g., ISIN), currency, latest price, KIID links, tradability flags, unit decimals, minimums, and cost/fee breakdowns.

Operations

Payment Instructions

Payment instructions (e.g., autogiro) batch one or more payments to accounts. Create instructions, then track the payments under each instruction (amounts, status, and references).

Operations

Orders

Fund orders (subscription/redemption) drive the trading lifecycle. Create, read, list, and cancel orders; track status from received → sent → confirmed → settled. Orders reference accounts and instruments, and map to cash/fund transactions on settlement.

Operations

Transactions

Transactions record movements of money and units.

  • Cash transactions (CT): deposits, withdrawals, cash legs of fund orders (with settlement dates).
  • Fund transactions (FT): unit movements from subscriptions/redemptions (trade & settlement dates). Use these endpoints to reconcile ledgers and statements.
Operations

Subscriptions (WebSocket & Webhooks)

Receive real-time updates from Fondo without polling.

  • WebSocket: open a persistent stream for .create, .update, .delete, and heartbeat events.
  • Webhooks: register a callback URL to get signed POSTs with current/previous payloads. Include replay/retry handling in your consumers.
Operations

System

API Service functions

Operations
© 2026 Fondo Solutions. All rights reserved.