Skip to main content
Bebop exposes three WebSocket endpoints for maker integrations.
All WebSocket messages must be sent as bytes, not text. Most WebSocket libraries expose this as a setting.

Endpoints

EndpointURLMessages
Pricingwss://api.bebop.xyz/pmm/<chain>/v3/maker/pricing?format=protobufStream levels to Bebop (Protobuf)
Quoteswss://api.bebop.xyz/pmm/<chain>/v3/maker/quoteRespond to taker_quote requests
Tradeswss://api.bebop.xyz/pmm/<chain>/v3/maker/tradesReceive trades executed against your quotes
<chain> is the lowercase slug of a supported chain (ethereum, arbitrum, base, and so on). See Settlement contract for the full list.

Auth

Include your API key as a Bearer token in the Authorization header on every WebSocket connection:
Authorization: Bearer xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Your key comes from Bebop. Request it via the support page; Bebop issues test credentials first and production credentials once /maker-status passes. See Credentials and environments.