# API Reference

Use API Reference when you already know which technical interface you need. Start with a protocol, then choose the product and capability documented by that interface.

## Scope labels

<ApiScopeTag scope="core">
  Start here. Core APIs provide the shared protocol, request shape, and behavior used across supported trading products.
</ApiScopeTag>

<ApiScopeTag scope="perpetuals">
  These pages document perpetuals-specific positions, margin, funding, and risk behavior.
</ApiScopeTag>

<ApiScopeTag scope="prediction-markets">
  These pages document the few additions that apply only to Prediction Markets.
</ApiScopeTag>

An untagged reference may still have product or account requirements. Confirm the applicability stated on the operation or stream before integrating it.

## REST

REST covers public market data and supported authenticated account and trading operations. Each operation page defines its request, authentication requirements, permissions, and response.

- [REST API overview](/rest-api/rest-api)
- [Trading REST API](/trading/rest-api/market-data)
- [Margin REST API](/trading/rest-api/margin)
- [Perpetuals REST API](/trading/rest-api/derivatives)
- [Prediction Markets REST API](/rest-api/prediction-markets)
- [Common administration REST API](/rest-api/common)

## WebSocket

The WebSocket API has one core protocol. Connection, authentication, message envelopes, standard streams, and methods are shared across supported products. Prediction Market order events use the same order stream and add an outcome field.

### Core protocol

- [Connection and session behavior](/websocket/introduction)
- [Authentication](/websocket/authentication)
- [Message format](/websocket/message-format)
- [Shared market data and account streams](/websocket/streams)
- [Position updates](/prediction-markets/websocket/streams#position-updates)
- [Shared methods playground](/trading/websocket/playground)

### Prediction-market extensions

- [Contract status](/prediction-markets/websocket/streams#contract-status)
- [Combo RFQ streams](/prediction-markets/combos-rfq/websocket-streams)

## FIX

Use the FIX reference for provisioned sessions, order entry, market data, drop copy, and message dictionaries. FIX session credentials and account mapping are interface-specific.

- [FIX API overview](/fix-api/fix-api)

## Authentication and account context

Before calling a private operation, verify all three separately:

1. The credential type is supported by the protocol and operation.
2. The credential has the required API-key role or OAuth scope.
3. The operation is resolved to the intended account using that interface's documented mechanism.

- [API key authentication](/authentication/api-key)
- [OAuth](/authentication/oauth)
- [Roles and permissions](/roles)
- [Accounts and subaccounts](/rest-api/common/admin/subaccounts)

The reference remains organized under current public routes while canonical `/api-reference/...` operation URLs are introduced in later migration phases.