GuidesAPI Reference
DocumentationLog In

Changelog

These release notes list changes to all Coinbase Exchange and Coinbase Pro products.

2022-NOV-21

🚧

Beta release of a WebSocket endpoint

We released a beta of a WebSocket endpoint with direct access to Coinbase Exchange servers at:
wss://ws-direct.exchange.coinbase.com/

Authentication is required and you can subscribe to multiple endpoints. If ws-direct becomes your primary connection, we recommend using the existing ws-feed as a failover connection.

2022-OCT-26

Updated Get all fills with new response property, market_type, in preparation for the upcoming Request For Quote (RFQ) feature.

2022-OCT-17

Added two new fields to the Ticker Channel: best_bid_size and best_ask_size.

2022-OCT-04

Modify Order Request (G) is live in production. See 2022-JUN-27 for release details.

2022-SEP-22

FIX Logon (A) messages now require that MsgSeqNum (34) be equal to 1. Any other value is rejected.

2022-SEP-19

Added Balance Statement Reports for historical and current crypto/fiat balances, with the Exchange REST API and in the Exchange UI at exchange.coinbase.com/profile/statements.

The Balance Report API:

  • Leverages the existing /reports endpoint.
  • Adds a new report type of balance.
  • Adds a balance object to the request with datetime (and group_by_potfolio_id for the UI only).
  • Keeps the same response schema (with the possibility that "type"="balance").

Example of Balance Report API Request

// Create balance statement for the portfolio tied to the API key
{
    "balance": {
        "datetime": "2022-02-25T05:00:00.000Z",
    },
    "email": "[email protected]",
    "format": "csv",
    "type": "balance"
}

2022-AUG-24

Added a new Wrapped Asset API, comprised of two endpoints:

2022-AUG-16

Added a reason field to the WebSocket Full Channel Change message:

  • "reason":"STP" for Self-Trade Prevention message
  • "reason":"modify_order" for Modify Order Request (See 2022-JUN-27 entry for more.)
{
  "type": "change",
  "reason":"STP",
  "time": "2014-11-07T08:19:27.028459Z",
  "sequence": 80,
  "order_id": "ac928c66-ca53-498f-9c13-a110027a60e8",
  "side": "sell",
  "product_id": "BTC-USD",
  "old_size": "12.234412",
  "new_size": "5.23512",
  "price": "400.23"
}

2022-JUL-27

We added support for multiple blockchain networks. Users can now withdraw USDC on Solana, and ETH, USDC, and MATIC on Polygon.

A new network field was added for select endpoints and in the UI. Affected API endpoints are:

  • /withdrawals/crypto accepts an optional network parameter as part of its POST request parameters.

    This parameter designates which network the currency will be sent on. For example, if the user withdraws USDC on Solana or Ethereum, the withdrawal address is validated against the network, the appropriate fee is calculated based on the network, and the currency is sent over the network. If no network is specified in the POST request, the default network (Ethereum) is used.

  • /address-book validates new addresses against all supported networks for the currency.

  • /address-validation accepts an optional network parameter in the address_info object or source parameter in the body as part of its POST request parameters.

    The address validator uses the network parameter to verify that the address is valid for the designated network. If no network is specified in the POST request, the default network is used.

    The source parameter currently only accepts the value address_book. When source has the value address_book, the address is validated against all supported networks for the currency.

"id": "ATOM",
"name": "Cosmos",
"min_size": "1",
"status": "online",
"message": "",
"max_precision": "0.000001",
"convertible_to": [
  
],
"details": {
  "type": "crypto",
  "symbol": null,
  "network_confirmations": null,
  "sort_order": 51,
  "crypto_address_link": "https://cosmos.bigdipper.live/account/{{address}}",
  "crypto_transaction_link": "https://cosmos.bigdipper.live/transactions/{{txId}}",
  "push_payment_methods": [
    "crypto"
  ],
  "group_types": [
  ],
  "display_name": null,
  "processing_time_seconds": 5,
  "min_withdrawal_amount": 0.1,
  "max_withdrawal_amount": 302000
},
"default_network": "cosmos",
"supported_networks": [
  "id": "ETH",
  "name": "ethereum",
  "status": "offline",
  "contract_address": "0x..",
  "crypto_address_link": "address_link",
  "crypto_transaction_link": "tx_link",
  "network_confirmations": 15,
  "min_withdrawal_amount": 0.001,
  "max_withdrawal_amount": 250
]

2022-JUL-25

We increased the order size for two FIX batched messages from 10 to 15:

2022-JUN-30

The following API parameters were removed per the lifting of maximum and minimum order size limits:

API ParameterDescription
base_max_sizeBase order size max (limit orders)
base_min_sizeBase order size min (limit orders)
max_market_fundsQuote order size max (market orders)

Affected features are:

2022-JUN-27

Modify Order Request (G) is now available for testing in the public sandbox. It will go to production in a few weeks.

Modify Order Request is an implementation of the Order Replace Request outlined in the FIX 4.2 protocol. You can send a single request to modify the price or size of an existing order using the FIX API.

WebSocket Full channel "Change" messages (and by extension the User channel) are also affected. Three fields are being added (new_price, old_price, reason).

πŸ“˜

Modify Order Requests that amend size down will retain queue priority in the Exchange order book.

FIX API

Example FIX Request:

BeginString=FIX.4.2 BodyLength=265 MsgType=ORDER_CANCEL_REPLACE_REQUEST MsgSeqNum=17 SenderCompID=00000000100000000000000000000003 SendingTime=20220609-04:01:48.757 TargetCompID=Coinbase ClOrdID=907b6ae6-bcbe-441a-b7bb-d932afdb9edb OrderID=71de0cdf-938f-495b-9fad-108837bde704 OrderQty=2 OrdType=LIMIT OrigClOrdID=907b6ae6-bcbe-441a-b7bb-d932afdb9eda Price=100.00 Side=BUY Symbol=ETH-USD TransactTime=20220609-04:01:48.757 CheckSum=107
TagNameDescription
37OrderIDUnique identifier of most recent order as assigned by broker
41OrigClOrdIDClOrdID <11> of previous order (NOT initial order of the day) when canceling or replacing an order
11ClOrdIDUnique identifier of replacement order as assigned by institution.
55SymbolMust match original order
54SideMust match original side
38OrderQtyTotal Intended Order Quantity (including the amount already executed for this chain of orders)
60TransactTimeTime this order request was initiated/released by the trader or trading system
40OrdTypeOnly limit orders are supported for now (2)
44PricePrice per share

Websocket Full Channel Change Message

Example of a change message from a Modify Order Request:

🚧

The fields new_price, old_price, and reason are being added. (The reason field was added on 2022-AUG-16.

{
  "type": "change",
  "reason":"modify_order",
  "time": "2022-06-06T22:55:43.433114Z",
  "sequence": 24753,
  "order_id": "c3f16063-77b1-408f-a743-88b7bc20cdcd",
  "side": "buy",
  "product_id": "ETH-USD",
  "old_size": "80",
  "new_size": "80",
  "old_price": "7",
  "new_price": "6"
}

2022-JUN-02

Lifted maximum and minimum order size limits. With this change:

  • Market orders are no longer subject to max or min size checks unless market funds are specified.
  • Limit orders are now subject to notional minimum size checks only. We repurposed the existing API parameter, min_market_funds, to represent this value.

Price Protection Points serve as a dynamic and real-time protection against slippage for large-sized orders.

The following API parameters have been deprecated (and will be removed June 30):

API ParameterDescription
base_max_sizeBase order size max (limit orders)
base_min_sizeBase order size min (limit orders)
max_market_fundsQuote order size max (market orders)

Affected APIs are Get all known trading pairs and Create a new order.

2022-MAY-25

Changes were made to Coinbase Pro:

  • We disabled the Coinbase Pro API, Deposit from Coinbase account, which lets you deposit funds from a Coinbase retail account into Coinbase Pro. The endpoint /deposits/coinbase-account now returns a 403 when called from a Coinbase Pro account.

    All other payment methods into Coinbase Pro remain the same and Coinbase Exchange is not affected.

  • Creating a new API Key on Coinbase Pro with the Transfer permission has new requirements (the use of old API keys will remain the same):

    • You must enable non-SMS 2FA.
    • You must allowlist all receive addresses for your transfers.

    Creating new API Keys on Coinbase Exchange is not affected by this change.

2022-MAY-05

  • Added cancel reason to the FIX and websocket feeds.
  • For FIX, we enhanced the Execution Report to include the cancel reason using the Text field.
  • For the websocket feed, we added a new cancel_reason field for authenticated messages by the user, accessible in the Full and User channels.

Supported cancel reasons are:

101:Time In Force
102:Self Trade Prevention
103:Admin
104:Price Bound Order Protection
105:Insufficient Funds"
106:Insufficient Liquidity
107:Broker

2022-MAY-02

We enabled new TLS/SSL features on the FIX servers for Exchange/Pro to increase security and performance. This includes limiting the supported ciphers and a new SSL certificate. Please check that your FIX SSL client:

  • Can support the new ciphers listed below.
  • Is not validating a specific SSL server certificate. If it is, you must update to the new certificate.

The new infrastructure will support only TLSv1.2 with the following Supported Server Ciphers:

RecommendLengthCipher SuiteElliptic Curve
Preferred128 bitsECDHE-RSA-AES128-GCM-SHA256Curve P-256 DHE 256
Accepted128 bitsECDHE-RSA-AES128-SHA256Curve P-256 DHE 256
Accepted256 bitsECDHE-RSA-AES256-GCM-SHA384Curve P-256 DHE 256
Accepted256 bitsECDHE-RSA-AES256-SHA384Curve P-256 DHE 256

Affected Endpoints:

  • In sandbox

    fix-public.sandbox.pro.coinbase.com:4198
    fix-public.sandbox.exchange.coinbase.com:4198
    
  • In production

    fix.pro.coinbase.com:4198
    fix.exchange.coinbase.com:4198
    

New Production FIX Server SSL Certificate:

-----BEGIN CERTIFICATE-----
MIIEezCCA2OgAwIBAgIQB4BoKHs2w7hI3RLss1nw7DANBgkqhkiG9w0BAQsFADBG
MQswCQYDVQQGEwJVUzEPMA0GA1UEChMGQW1hem9uMRUwEwYDVQQLEwxTZXJ2ZXIg
Q0EgMUIxDzANBgNVBAMTBkFtYXpvbjAeFw0yMjAzMzEwMDAwMDBaFw0yMzA0Mjky
MzU5NTlaMCIxIDAeBgNVBAMMFyouZXhjaGFuZ2UuY29pbmJhc2UuY29tMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnmFkdVt+0k/d+HkZaX/kgjtCU6Ts
5TePVbYCGOjT05ClT7GHu7fSzUjO/BNCkBItp5WwFRdOOkWV8Zeg2WSHpDBOZNJt
cXiQx6BSTRD/myjv0NBxVsKby9BbKmj8df3C1PehakUQPdsiP7DkviYUpXz+T4FQ
PAg8M6PXu7sT7Rfbc6gY49VyyRU6slcij/Xwn4WSVWK+GMYPlsu7M2Vp0rr+sCIZ
uLHh/23TNzlGiYzXgypoZ/F57AIi+ToeRvnLe++ZfIKP37uhNxYfYrr4c3wPBoGc
LIWgSNMK9/Oue6VUCG7AVioCy2yL0CEiTmvS4Eb2urbt3iDWI+6wySW9LwIDAQAB
o4IBhzCCAYMwHwYDVR0jBBgwFoAUWaRmBlKge5WSPKOUByeWdFv5PdAwHQYDVR0O
BBYEFOlcV+BjGTnleq713Nzl4UifIPZCMDkGA1UdEQQyMDCCFyouZXhjaGFuZ2Uu
Y29pbmJhc2UuY29tghVleGNoYW5nZS5jb2luYmFzZS5jb20wDgYDVR0PAQH/BAQD
AgWgMB0GA1UdJQQWMBQGCCsGAQUFBwMBBggrBgEFBQcDAjA9BgNVHR8ENjA0MDKg
MKAuhixodHRwOi8vY3JsLnNjYTFiLmFtYXpvbnRydXN0LmNvbS9zY2ExYi0xLmNy
bDATBgNVHSAEDDAKMAgGBmeBDAECATB1BggrBgEFBQcBAQRpMGcwLQYIKwYBBQUH
MAGGIWh0dHA6Ly9vY3NwLnNjYTFiLmFtYXpvbnRydXN0LmNvbTA2BggrBgEFBQcw
AoYqaHR0cDovL2NydC5zY2ExYi5hbWF6b250cnVzdC5jb20vc2NhMWIuY3J0MAwG
A1UdEwEB/wQCMAAwDQYJKoZIhvcNAQELBQADggEBADemhPMMlRRLMlnSvaVaaSCF
ncdehfDVg3Lmr2UjcMCq2MJxriz8elgu7M6TqVGwiRVrMb4j2kD+3EUc/+V+W1dE
uX8aEzxuV01MKTFEh4R/WihCKM2l0NCfg6O8jYmtKPE9gkHe+5hW4igsM90mK+hA
GlhH7hGSouHDjkwbvlN0yrNFJXaTZE8wHd1VTDtYmzTQXkn8hAR4muesAgEtc22W
B8vbLCt6ZOeoMH/SKh2vsAmWE/3DR7+TIh9Dm+54jEwuUID+nmETaacY2wDT1XU9
eWR4xJMa8QuK1sGuO3TgvYZPCyzAXoXCjR5mVYit8PteMVwfJnTm1nLc73rAiWA=
-----END CERTIFICATE-----

New Sandbox FIX Server SSL Certificate:

-----BEGIN CERTIFICATE-----
MIIEdDCCA1ygAwIBAgIQD03L1cHVypYSDFuvcnpAHzANBgkqhkiG9w0BAQsFADBG
MQswCQYDVQQGEwJVUzEPMA0GA1UEChMGQW1hem9uMRUwEwYDVQQLEwxTZXJ2ZXIg
Q0EgMUIxDzANBgNVBAMTBkFtYXpvbjAeFw0yMjAzMjcwMDAwMDBaFw0yMzA0MjUy
MzU5NTlaMCoxKDAmBgNVBAMMHyouc2FuZGJveC5leGNoYW5nZS5jb2luYmFzZS5j
b20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC8LYRdqMoVNa/0M4MF
+Wkr8SiybZ95JycTE+0ZVmf92DKo4I8m/8fBtOrH0jgrhvamVSJ0lI6VFiAzlTd1
doUbliQ9Xm1aE/YHQO9J64AIP97peysgHBd+g3/Vhz33aaaU2vyHH5kPHiekU8n/
ObXPPoFd/Awul8uxxlXsVFx8oBWL2MeMjLNLLWNiGWq+lQloGKsQYVR/fQZizvpP
vyZO6pCLRId6+Wq3Tcb7NHQZc6+tePVi+5fovE+lm/yQrhjGqDzI7P4rWjJqCPrA
sYJeYFcVJhdSuFY2Ngm8eKeDP14TVEs9pkIWvyMGmB17QBPbRJipdoKu1N6fsx54
N9JDAgMBAAGjggF4MIIBdDAfBgNVHSMEGDAWgBRZpGYGUqB7lZI8o5QHJ5Z0W/k9
0DAdBgNVHQ4EFgQUa5RZ0yvv71YteSuqO1VRvmGGKv0wKgYDVR0RBCMwIYIfKi5z
YW5kYm94LmV4Y2hhbmdlLmNvaW5iYXNlLmNvbTAOBgNVHQ8BAf8EBAMCBaAwHQYD
VR0lBBYwFAYIKwYBBQUHAwEGCCsGAQUFBwMCMD0GA1UdHwQ2MDQwMqAwoC6GLGh0
dHA6Ly9jcmwuc2NhMWIuYW1hem9udHJ1c3QuY29tL3NjYTFiLTEuY3JsMBMGA1Ud
IAQMMAowCAYGZ4EMAQIBMHUGCCsGAQUFBwEBBGkwZzAtBggrBgEFBQcwAYYhaHR0
cDovL29jc3Auc2NhMWIuYW1hem9udHJ1c3QuY29tMDYGCCsGAQUFBzAChipodHRw
Oi8vY3J0LnNjYTFiLmFtYXpvbnRydXN0LmNvbS9zY2ExYi5jcnQwDAYDVR0TAQH/
BAIwADANBgkqhkiG9w0BAQsFAAOCAQEATpjyCMwAOSFKFTA67UaVkDCjz/ULBY6P
L4JwTJ+7kmT+HMvGimx15CsVjne64bT5twWlzqA/l4h25HGj0hD0TU2ktqmFhfAm
DpjGVp4KgIcZpvv7oRIU4e5I422Y++2UVuATwLWdELgpnm4AVq1aqI10XrQlJeHL
gRVfV5qkr9Vsc+fk7HY7YwbNQk2jXbRaj22f6GxiJ/6VmUcCD7zZ1GZtUipv0JEy
PtWD/BbSKNx1GJnLZ6L+QytPs+MW+FEetlU/oqPuyYRhmJUBUiwKkm6yKWRj9tQf
sq0a4uLI3SUgsBv/CQ/Qa9LnRdNjvlWSKLzeIX2LU9rE/3F3oQh7HQ==
-----END CERTIFICATE-----

2022-APR-14

  • Updated the maximum number of portfolios (or profiles) to 25.

2022-MAR-21

  • Updated the maximum number of portfolios (or profiles) to 15.

2022-MAR-17

  • Added FIX message tags: cumQty, leaveQty, AvgPx

2022-FEB-22

  • REST API will enforce case sensitivity for all URLs.
    • Example: https://api.exchange.coinbase.com/products/BTC-USD/Ticker should be https://api.exchange.coinbase.com/products/BTC-USD/ticker. Note the lowercase t in ticker.
    • This does not apply to URL parameters, just the URL itself: https://api.exchange.coinbase.com/orders?product_id=BTC-USD&sortedBy=created_at&sorting=desc&limit=100 is valid as the the URL is lowercase. Query parameters such as product_id can have values with capitals. However https://api.exchange.coinbase.com/Orders?product_id=BTC-USD&sortedBy=created_at&sorting=desc&limit=100 would be invalid as the O in /Orders is not the same URL as specified in its docs.

2022-JAN-31

  • Web Socket API users are notified when the client is actively disconnected for having a full buffer, or for being too slow to consume or read messages.

2022-JAN-25

  • GET and POST responses for the /orders endpoint will return client order id as client_oid if exists.

2021-OCT-25

  • FIX API will now enforce CheckSum validations for incoming FIX messages.

2021-SEP-21

  • All reports can be generated in parallel. Clients are no longer restricted to only have 3 reports being created at a time. Now clients can have up to 3 accounts reports and 3 fills reports per product generating at a time.

2021-SEP-09

  • Return the full aggregated order book for Level 2 queries under the GET /products/<product-id>/book endpoint.

2021-AUG-23

  • Reduced the set of fields returned by orders in "pending" status for GET /orders, GET /orders/<id>, and GET /orders/client:<client_oid> APIs. See List Orders documentation for more details. Orders with non-pending statuses will be unaffected by this change.

2021-AUG-17

  • Return client order ID rather than order ID in successful cancel order response for REST API endpoint DELETE /orders/client:<client_oid>.

2021-AUG-12

  • Require the field Symbol(55) on the following FIX API messages: OrderCancelRequeset(F) and OrderStatusRequest(H). Messages (F) and (H) without Symbol(55) will be rejected.

2021-AUG-06

  • Add pagination support for the GET /fills endpoint.

2021-AUG-01

  • Increased the maximum number of FIX connections allowed per profile from 5 to 7.

2021-JUL-01

  • Added sendingTime 5 minute validation.

2021-JUN-22

  • Added fx_stablecoin to products.

2021-JUN-21

  • Order Cancel Batch Request(U4) will accept optional ClOrdID(11) field for each cancel request. The provided ClOrdID(11) will be included in Order Cancel Reject(9) for partial reject.

2021-JUN-14

  • Order Cancel Batch Request(U4) will now return Order Cancel Reject(9) for partial rejected cancel request.

2021-JUN-10

  • Added failed status to reports.

2021-JUN-03

  • Our API endpoints were moved to exchange.coinbase.com from prime.coinbase.com.

Production URLs

ProductOld URLNew URL
Websitehttps://prime.coinbase.comhttps://exchange.coinbase.com
REST APIhttps://api.prime.coinbase.comhttps://api.exchange.coinbase.com
FIX APItcp+ssl://fix.prime.coinbase.com:4198tcp+ssl://fix.exchange.coinbase.com:4198
Web Socket APIwss://ws-feed.prime.coinbase.comwss://ws-feed.exchange.coinbase.com

Sandbox URLs

ProductOld URLNew URL
Websitehttps://public.sandbox.prime.coinbase.comhttps://public.sandbox.exchange.coinbase.com
REST APIhttps://api-public.sandbox.prime.coinbase.comhttps://api-public.sandbox.exchange.coinbase.com
FIX APItcp+ssl://fix-public.sandbox.prime.coinbase.com:4198tcp+ssl://fix-public.sandbox.exchange.coinbase.com:4198
Web Socket APIwss://ws-feed-public.sandbox.prime.coinbase.comwss://ws-feed-public.sandbox.exchange.coinbase.com

2021-MAY-27

  • API FIX - Order Cancel Request (F) endpoint requires the Symbol field now.

2021-MAY-20

  • /fills custom rate limit.

2021-MAY-14

  • Increased public and private rate limits.

2021-APR-22

  • Increase pagination limit from 100 to 1000.

2021-APR-05

  • Updated max profiles to 10 and max API keys to 200.

2021-FEB-04

  • The Trailing Volume endpoint has been deprecated in favor of the Fees endpoint to get the latest volumes.

2021-JAN-15

  • Now recommending that clients opt to batch cancel orders by profile rather than session due to recent performance optimizations.

2020-DEC-23

  • HandlInst in API FIX is no longer required.

2020-NOV-16

  • Addition of max_withdrawal_amount field in the /currencies endpoint.

2020-OCT-05

  • Authed users subscribed to the Websocket Full or User channel will now receive their order fee rates on match messages. Details can be found in documentation for the Full channel.

2020-OCT-02

  • Addition of cancel_code field on canceled withdrawals.

2020-SEP-17

  • Addition of an endpoint to provide estimates of network fees for crypto withdrawals.
  • Addition of a parameter for crypto withdrawals to specify if the network fee should be added / deducted from the requested amount.
  • 'fee' and 'subtotal' fields added to responses for crypto withdrawals.

2020-SEP-14

  • The candles endpoint no longer has custom rate limits. It now shares the same rate limit with every other public endpoint.

2020-SEP-03

  • The maximum number of open orders (i.e. limit orders + stop orders) per product per profile will be 500. Profiles that exceed this threshold will be unable to place new orders on that product until the number of open orders is below 500.

2020-JUN-18

2020-JUN-17

  • Generate an address for crypto deposits. See reference here.

2020-JUN-15

  • Expose min_market_funds, max_market_funds fields in the /products endpoint.

2020-JUN-12

  • Users can retrieve information regarding their transfer, buy, and sell limits at /users/self/exchange-limits. Refer to the Limits API for more information.

2020-APR-27

  • Fill execution reports will show fee rates associated with the user's order. Please refer to the FIX ExecutionReport API for details on format.

2020-FEB-20

  • Execution Reports from Order Status Requests will return ClOrdID, if it is supplied, even if the order isn't found.

2020-FEB-10

  • Activate messages on the Websocket feed will no longer expose taker_fee_rate.

2019-DEC-16

  • Rate limiting changing from a per user basis to per profile basis.

2019-SEP-30

  • Order Status Request no longer allows the wildcard option.
  • Order Status Request returns pending and done orders when you use OrderID or ClOrdID.
  • Scheduled disconnects are on Mondays and Thursdays at 11 AM Pacific Time.