AsyncAPI channel · 1Forge
· 1Forge Forex Stream API
stream
Single bidirectional channel for control and price-update frames.
Channel address
stream
Operations
publish
sendStreamFrames
Send control frames (login, subscribe/unsubscribe, heartbeat) to the 1Forge server.
subscribe
receiveStreamFrames
Receive incoming control or update frames from the 1Forge server.
Messages
LoginCommand
Client sends API key for authentication.
Content-Type:
SubscribeTo
Subscribe to updates for a single currency pair.
Content-Type:
UnsubscribeFrom
Unsubscribe from updates for a single currency pair.
Content-Type:
SubscribeToAll
Subscribe to updates for every available pair.
Content-Type:
UnsubscribeFromAll
Unsubscribe from every pair currently subscribed.
Content-Type:
Beat
Client keep-alive response to a server `heart` frame.
Content-Type:
LoginPrompt
Server requests the client send its API key.
Content-Type:
PostLoginSuccess
Server confirms authentication succeeded.
Content-Type:
Heart
Server keep-alive prompt; clients respond with `beat`.
Content-Type:
Update
Real-time bid/ask/price update for a subscribed currency pair.
Content-Type:
ForceClose
Server instructs the client to close the connection.
Content-Type:
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.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.