Api Spec 7 2
ApiSpec72GDAX API Reference. Introduction. Welcome to GDAX trader and developer documentation. These documents outline exchange functionality, market details, and APIs. APIs are separated into two categories trading and feed. Trading APIs require authentication and provide access to placing orders and other account information. Api Spec 7 2' title='Api Spec 7 2' />
Feed APIs provide market data and are public. General. Market overview and general information. Matching Engine. GDAX operates a continuous first come, first serve order book. Orders are executed in price time priority as received by the matching engine. Self Trade Prevention. Self trading is not allowed on GDAX. Two orders from the same user will not fill one another. When placing an order, you can specify the self trade prevention behavior. Decrement and cancel. The default behavior is decrement and cancel. When two orders from the same user cross, the smaller order will be canceled and the larger order size will be decremented by the smaller order size. If the two orders are the same size, both will be canceled. Cancel oldest. Cancel the older resting order in full. The new order continues to execute. Cancel newest. Cancel the newer taking order in full. Api Spec 7 2' title='Api Spec 7 2' />2. Terminology and Algorithms. When this specification says to terminate an algorithm the user agent must terminate the algorithm after finishing the step it is on. The home page for SPEC, the Standards Performance Evaluation Corporation, a standards body for performance benchmarks. Design your OpenAPI spec in SwaggerHubs cloudbased API development platform. The W3C Geolocation API is an effort by the World Wide Web Consortium W3C to standardize an interface to retrieve the geographical location information for a client. Standard Edition Section Inquiry Question Reply 16A 3rd Edition June 2004 5. AI0108 Background Section 5. The CORBA23 package defines additions to existing CORBA interfaces in the Javatm Standard Edition 6. These changes occurred in recent revisions to the CORBA API. List of J2EE 1. 2 specifications Developers Guide. Technology Version JDBC Standard Extension API 2. Java Naming and Directory Interface Specification JNDI. This document defines APIs for a database of records holding simple values and hierarchical objects. Each record consists of a key and some value. Moreover, the. 
The old resting order remains on the order book. Cancel both. Immediately cancel both orders. Notes for Market Orders. When a market order using dc self trade prevention encounters an open limit order, the behavior depends on which fields for the market order message were specified. If funds and size are specified for a buy order, then size for the market order will be decremented internally within the matching engine and funds will remain unchanged. The intent is to offset your target size without limiting your buying power. Api Spec 7 2' title='Api Spec 7 2' />If size is not specified, then funds will be decremented. For a market sell, the size will be decremented when encountering existing limit orders. Price Improvement. Orders are matched against existing order book orders at the price of the order on the book, not at the price of the taker order. Example. User A places a Buy order for 1 BTC at 1. USD. User B then wishes to sell 1 BTC at 8. USD. Because User As order was first to the trading engine, they will have price priority and the trade will occur at 1. USD. Order Lifecycle. Valid orders sent to the matching engine are confirmed immediately and are in the received state. If an order executes against another order immediately, the order is considered done. An order can execute in part or whole. Any part of the order not filled immediately, will be considered open. Orders will stay in the open state until canceled or subsequently filled by new orders. Orders that are no longer eligible for matching filled or canceled are in the done state. Fees. Trading Fees. GDAX operates a maker taker model. Orders which provide liquidity are charged different fees from orders taking liquidity. The fee is assessed as a percentage of the match amount price size. User 3. 0 day volume Taker fee. Maker fee 0 0. A 0. At the end of the day UTC 0. The amount of the rebate issued is calculated on the percentage of total exchange volume, in bitcoin, that a trader has participated in over the past 3. ETH LTC markets have a 0. Example. There is an existing SELL order for 5 BTC at 1. Abs Diagnostic Software For Pc. USD on the order book. You enter a BUY order for 7 BTC at 1. USD. 5 BTC of your BUY order are immediately matched and you are charged the taker fee because you are taking liquidity from the order book. The remaining 2 BTC of your order are now sitting on the BID side of the order book. A SELL order for 2 BTC at 1. USD arrives and matches against your 2 BTC BUY order. In this case you provided liquidity and are not charged any fees. Rebate example. If 1. BTC was traded on Coinbases USD order book in the last thirty days and you accounted for 1. The rebate is issued in the quote currency. DepositWithdraw Fees. GDAX does not charge any additional deposit or withdraw fees for moving funds between your Coinbase accounts and your Exchange accounts. Colocation. GDAX primary data sources and servers run in the Amazon US East N. Virginia data center. To minimize latency for API access, we recommend making requests from servers located near the AWS us east 1 data center. Sandbox. A public sandbox is available for testing API connectivity and web trading. The sandbox provides all of the functionality of the production exchange but allows you to add fake funds for testing. Login sessions and API keys are separate from production. Use the sandbox web interface to create keys in the sandbox environment. To add funds, use the web interface deposit and withdraw buttons as you would on the production web interface. Sandbox URLs. When testing your API connectivity, make sure to use the following URLs. Websitehttps public. REST APIhttps api public. Websocket Feedwss ws feed public. FIX APIhttps fix public. Note on FIX APIvarhttpsrequirehttps varrequesthttps. GET,url https fix public. Upgrade fix,Connection Upgrade request. Pass socket to FIX client request. When connecting to the FIX API in Sandbox, you must start with an HTTP Upgrade request and set the Upgrade header to fix. After receiving a 1. Switching Protocols response from the server, you may continue using the connection as a regular FIX connection. Remember to use HTTPS for this. Client Libraries. Client libraries can help you integrate with our API quickly. Official. Unofficial. APIThe REST API has endpoints for account and order management as well as public market data. REST API Endpoint URLhttps api. There is also a FIX API for order management. Requests. All requests and responses are applicationjson content type and follow typical HTTP response status codes for success and failure. Errorsmessage Invalid PriceUnless otherwise stated, errors to bad requests will respond with HTTP 4xx or status codes. The body will also contain a message parameter indicating the cause. Your languages http library should be configured to provide message bodies for non 2xx requests so that you can read the message field from the body. Common error codes. Status Code. Reason. Bad Request Invalid request format. Unauthorized Invalid API Key. Forbidden You do not have access to the requested resource. Not Found. 50. 0Internal Server Error We had a problem with our server. Success. A successful response is indicated by HTTP status code 2. If the response has a body it will be documented under each resource below. GDAX uses cursor pagination for all REST requests which return arrays. Cursor pagination allows for fetching results before and after the current page of results and is well suited for realtime data. Endpoints like trades, fills, orders, return the latest items by default. To retrieve more results subsequent requests should specify which direction to paginate based on the data previously returned. CB BEFORE and CB AFTER. Your requests should use these cursor values when making requests for pages after the initial request. Parameters. Parameter. Default. Descriptionbefore. Request page before newer this pagination id. Request page after older this pagination id. Number of results per request. Maximum 1. 00. default 1. Example. GET ordersBefore and After cursors. The before cursor references the first item in a results page and the after cursor references the last item in a set of results. To request a page of records before the current one, use the before query parameter.