Skip to content
API Reference/
/
Webhook callback

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

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

Get WebSocket connection

Request

Opens a persistent WebSocket channel for the specified client_id and streams real-time events defined in the event schema.

Event types:

.create – includes a current property with the newly created object.

.update – includes a current property with the updated object and a previous property with the object's prior state.

.delete – includes a previous property with the deleted object.

heartbeat – sent at intervals to keep the connection alive.

Use this endpoint to receive live updates (for example on orders, transactions, or journeys) without polling the REST API.

A heartbeat event is sent regularly to keep the connection alive.

Security
oAuth
Path
client_idstring(UUID)^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]...read-onlyrequired

The ID of requested client.

Example: 49ad7378-121c-4a53-9894-dfd14a7b4877
curl -i -X GET \
  https://docs.fondo.se/_mock/openapi/api_3.0.3/v2/partner/client/49ad7378-121c-4a53-9894-dfd14a7b4877/subscribe \
  -H 'Authorization: Bearer <YOUR_Token_HERE>'

Responses

Websocket upgrade

Bodyapplication/json
One of:

Event subscription object

eventTypestring(heartbeat)

Heartbeat to keep connection alive

Value"heartbeat"
Response
application/json
{
  "eventType": "heartbeat"
}

Webhook callback

Request

Your endpoint that Fondo calls whenever an event occurs. The POST body matches one of the event types defined in the event schema:

.create – current contains the newly created object.

.update – current contains the updated object, and previous shows the object's state before the change.

.delete – previous contains the deleted object.

Fondo sends these requests to the callback URL you register, allowing your system to react immediately to updates such as account changes, order executions, or transaction settlements. (This API doc shows it as a POST to Fondo for illustration; in practice, the call is made from Fondo to your server.)

Note that this documentation system does not yet support OpenAPI 3.1 Webhooks spec and the callback is described as a POST to Fondos API. The URL and host is an endpoint on your system.

Bodyapplication/json

Call back to your server with updates

One of:

Account created

currentobject(account)
curl -i -X POST \
  https://docs.fondo.se/_mock/openapi/api_3.0.3/fondo/webhooks/callback \
  -H 'Content-Type: application/json' \
  -d '{
    "current": {
      "ref": "160367146695159",
      "name": "Spar",
      "status": "pending",
      "accountType": "isk",
      "serviceType": "portfolioManagement",
      "owner": {
        "firstName": "Ben",
        "lastName": "Rangel",
        "fullName": "Ben Rangel",
        "ssn": "197001010003"
      },
      "balance": 100,
      "amounts": {
        "deposited": 123.45,
        "withdrawn": 123.45
      },
      "positions": [
        {
          "instrument": "string",
          "units": 0,
          "unitsSettled": 0,
          "value": 0,
          "closePrice": 0,
          "gav": 0
        }
      ],
      "deleted": true,
      "clientId": "string",
      "bankAccounts": [
        {
          "iban": "SE7280000810340009783242",
          "bban": "666 666 666",
          "bank": "Buy n'\'' Large",
          "name": "Lönekonto",
          "createdDate": "2018-12-13T23:59:00.001Z",
          "modifiedDate": "2018-12-13T23:59:00.001Z",
          "deletedDate": "2018-12-13T23:59:00.001Z",
          "validated": true
        }
      ],
      "currency": "SEK"
    }
  }'

Responses

Return a 200 status to indicate that the data was received successfully

System

API Service functions

Operations
© 2026 Fondo Solutions. All rights reserved.