GETTING STARTED

APIs

PAYMENT API

LEGACY API

# API's

We have a couple of different API's. Please view the general notes that apply to all of them, and have a look at the different types of API's to determine which one is correct for you.

# GENERAL NOTES

NON-BREAKING CHANGES

GloBee considers the following types of API changes to be non-breaking and backwards-compatible:

  • Exposing a new resource type

  • Adding a new method to an existing resource type

  • Adding an optional property to an existing resource type

  • Adding an optional query parameter to an existing resource method

  • Deprecating an existing resource method and providing an alternative

CROSS-ORIGIN RESOURCE SHARING

The GloBee REST API supports CORS, so that you may send requests directly from the client, however remember to never expose your private key. If your key becomes compromised, you will want to disable your old Client ID and register a new one.

# Different API's

PAYMENT API

Our payment API is built to allow quick and easy integration with our system for the sole perpose of creating payment requests, needed in the E-Commerce checkout process. All of our plugins make use of this API. If you want to create a custom solution where users can pay you through your website, this is the API you will use.
[ View Documentation ].

LEGACY API's

The legacy api allows users to perform more actions than simply creating payment-requests, but the authorization process is more intense and complicated for security purposes. Each message is signed using Eliptic Curve Cryptography and is verified before any actions are taken.
[ View Documentation ].