AsyncAPI channel · Fortnox · Fortnox Topics WebSocket API

/topics-v1

The single WebSocket channel. The client publishes control commands (currently `add-tenants-v1`) to subscribe tenants and set replay offsets, and subscribes to the resulting change-notification events pushed by Fortnox across all subscribed topics.

Open source AsyncAPI → All Fortnox channels Fortnox provider profile
Provider: Fortnox AsyncAPI: v2.6.0 Spec: Fortnox Topics WebSocket API Operations: 2 Messages: 2

Channel address

/topics-v1

Operations

publish
sendCommand
Send a control command to the WebSocket (e.g. add tenants).
receiveTopicEvent
Receive pushed change-notification events.

Messages

AddTenantsCommand
Subscribe one or more tenants (integration keys) to the stream.
Content-Type: application/json
TopicEvent
A minimal "what changed" event on a domain topic.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.