Credence Global Bank Invest API Documentation

Authentication

Overview

Given the sensitive nature of investing online there are inherent risks in exposing brokerage services to the public. These risks can be mitigated by using a strong authentication strategy.

While some of the authentication methods we use may be more difficult to implement, it is with our customers’ security and privacy in mind that we enforce strict standards on account access. With that in mind, we require that each request to a critical brokerage function be encrypted, signed and verified (See Security).

Authenticated Calls

Every call made to the API must be signed using credentials from both the application and the user (See the Security section for more information). If you have improperly implemented the request headers, the API will respond with an authentication error.

Error Handling

The API will respond accordingly when a call lacks the proper authentication for it to be successful. In the event that a user has revoked access to your application, or if you attempt to perform an action against an account that does not belong to the user you are authenticated as, the API will respond with an authentication error. OAuth

We support the OAuth protocol for authentication. You must use OAuth to authenticate with the API.

Creating an Application

To create an application, you can visit https://www.credenceinc.org/api/invest/documentation. Once there you can sign-in and register your account for access to the API. Once properly registered and agreements have been signed, you can create applications associated with your account. This will give you everything you need to begin making requests on behalf of your own account.

Authenticating a User

In order to access a user's information and make calls on a user's behalf (or your own), your application will need to obtain that user's credentials. We support the OAuth Core 1.0 Revision A standard and you can find more information about our implementation in the OAuth section.