Step 1: Authentication
The API uses Bearer (Token) Authentication to authenticate requests. The value of this bearer token is a JSON Web Token (JWT), which is passed in the Authorization HTTP header and signed by your private API Key.
Create a new API key
To use the API you will need to generate a new API key. Head over to your dashboard and visit the Integrations page.
On this page, click the Add API key button and select a name for your key. The name is purely for you to track what key is for what integration. You will need to store the downloaded key securely as we will not store this key for you.
Using an SDK is the most simple way to call and authenticate with our API. When using one of our SDKs to call the API, authentication is handled by the SDK client. You will only need to initialize the SDK with your private to handle authentication.
Install a server-side SDK
Use the package manager in your preferred programming language to install our server-side SDK. Token generation can only be done server side and we do not recommend doing this client side as it will expose your API key to your customers.
Please install the latest release of your preferred SDK.
Initialize the SDK client
Next, initialize the SDK with the ID of your instance and the private key.
The Gr4vy ID is the unique identifier for your instance. Together with the environment (sandbox or production) it is used to connect to the right APIs.
The possible values for your ID are one of wpay, wpay1, wpay2, or wpay3. We will inform you
in which instance your account has been set up.
This assumes the key you created in the previous step is kept in a file called
private_key.pem that is kept in the same folder next to the code. You could
store this key in an environment variable or a secure vault.
Summary
In this step you:
- Learned about API authentication
- Created a new private key for the API
- Used an SDK to authenticate or manually created a token
Was this page helpful?