API Updates

We are thrilled to announce an important update to our API that will enhance its performance, scalability, and security. In this release, we are introducing changes to the API URL, implementing a rate limit of 500 calls per minute, and enforcing a quota limit of 150,000 calls per day. Additionally, we will be introducing a new key that must be included in the header for authentication purposes.

Please be on the lookout for communication from our Client Success team with instructions on how to generate a key and the timelines of this update.

Here are the details of the upcoming changes:

1️⃣ API URL Update:
To streamline our infrastructure and align with industry best practices, we will be updating the API URL. The new URL will be as follows: api.revioapi.com. Please update your code and applications to utilize the new URL.

2️⃣ Rate Limit and Quota Limit:
To ensure balanced usage and maintain optimal performance, we will be introducing rate limiting and quota limiting measures. These limits will help prevent abuse and guarantee a reliable experience for all users. Please take note of the following:

Rate Limit: Each account will have a rate limit of 500 API calls per minute. Any requests exceeding this limit will receive a "429 Too Many Requests" response until the rate limit resets.
Quota Limit: To provide flexibility and accommodate different usage scenarios, we will be implementing a quota limit of 150,000 API calls per day for each account. Once the quota limit is reached, further requests will be denied until the quota resets.

3️⃣ New Key for Header Authentication:
To enhance the security of your API calls, we will be introducing a new key that must be included in the header of your requests. This key will serve as an additional authentication mechanism. Please make sure to update your code accordingly with the following information:

New Key: A unique API key will be associated with your account. Instructions on how to generate this key will come from our Client Success team.
Header Key Name: To authenticate your requests, include the "Ocp-Apim-Subscription-Key" header with the provided key value.

Here is a couple of examples of what your request should look like:

cURL Example:
curl --location 'https://api.revioapi.com/v1/Customers'
--header 'Accept: application/json'
--header 'Ocp-Apim-Subscription-Key: ##############

HTTP Example:
GET /v1/Customers HTTP/1.1
Host: api.revioapi.com
Accept: application/json
Ocp-Apim-Subscription-Key: #################

Introduction

API Basics

API Documentation

API How-To

Webhooks

Portal Documentation

SOAP Resources and Endpoints