Credence Global Bank Invest API Documentation

Request Structure

Overview

The request structure of an API is pretty simple for most calls. Most user and account-based brokerage calls can be made without a request body at all. We've done our best to make the API as restful as possible. This means that resources and their corresponding operations have an identifiable pattern to their use.

While many of the calls are simply requests for information (GET) there are circumstances which require sending information (POST) or removing resources on the server (DELETE).

For examples of each request, visit the specific page pertaining to the API call you are interested in.

We are exploring new ways to generate requests to our API. If you have a specific need for an alternate request format, let us know.

Format

All requests made to the Credence Global Bank Invest API must be valid HTTP requests sent over using the proper request method. For instance, a POST to create a new watchlist will include form parameters.

*Note: Due to the complex nature of trade calls, we ask that you POST in FIXML to an order submission (or preview) operation.

Headers

For authenticated calls we require that you send over a valid OAuth header. For unauthenticated requests, there aren't any required headers.

URI

Some requests require parameters within the URI. An example of this functionality as an accounts/:id/balances{.format} call. This call has multiple parameters handled on the command line. So to make a request to this operation your request URL would be:

https://api.tradeking.com/v1/accounts/12345678/balances.json

Which would result in the balances response for account number 12345678 sent back in JSON format.