Skip to main content

Authentication

To access the RaiseNow API programmatically HTTP requests must be authenticated with an OAuth Bearer Token in the Authorization header. A token can be obtained by posting your Client Credentials to the Token endpoint.

Client Credentials carry many privileges, so be sure to keep them secure! Do not share your secret in publicly accessible areas such as GitHub, client-side code, and so forth.

Client Credentials can be requested from our Customer-Success Team via customer-success@raisenow.com. The personal username and password credentials can not be used to access the API directly.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

Obtain a Token

A Token can be obtained by posting the following request to the Token endpoint.

{
"grant_type": "client_credentials",
"client_id": "<REPLACE_WITH_YOUR_CLIENT_ID>",
"client_secret": "<REPLACE_WITH_YOUR_CLIENT_SECRET>"
}

The response will look like:

{
"token_type": "Bearer",
"expires_in": 3600,
"access_token": "eyJ...Rl6w"
}

The access_token can now be used to perform API calls against any other endpoint.

Using the Bearer Token

For all API requests the Bearer Token needs to be sent in the Authorization HTTP header.

Example using cUrl:

$ curl --header 'Authorization: Bearer <token>' https://api.raisneow.io/.....

Token lifetime

RaiseNow API Bearer Tokens expire 1 hour after issuing. After the Token has expired, a new one needs to be retrieved via the Token endpoint.

Currently, the RaiseNow API does not support the OAuth Refresh Token grant type.