Updating Zapier Middleware – Acme US

What has changed between Rev.io Zapier App Version 2.3.3 and 3.0.0

We are currently adopting additional REST API requirements that will enable enhanced API traffic management and useability through a tool known as APIM. Because the Rev.io Zapier App is built on RESTful API calls, these additional requirements have been accommodated in a new version of the app (3.0.0).

It is important to emphasize that the only difference between the 2.3.3 App version and the new 3.0.0 App version is the base URL and the API Subscription Header Key.

The 3.0.0 version of the Rev.io Zapier App still requires Username, Password, and “domain” or “client code”, and all other functionality remains unchanged.

Updating all Zapier Zaps to use the Rev.io 3.0.0 App version is mandatory, as support for older versions will end sometime in early 2024, and API calls without the correct base URL and subscription header key will fail.

How to Obtain a Rev.io API Subscription Header Key and Base URL

Unless otherwise directed, the base URL for Rev.io Zapier 3.0.0 apps should always be: https://api.revioapi.com/v1/

A set of two subscription headers keys (primary and a secondary) can be obtained by creating an account at: https://developers.revioapi.com.

Create an account
Navigate to Products, then Rev.io API
Request a subscription key under the Subscriptions section.
You will receive a notification email when the keys have been created. They can be viewed under User Profile.

User Profile

How to Migrate a Zapier “Zap” to Rev.io App Version 3.0.0

To migrate an existing Zapier “Zap” to use the new Rev.io 3.0.0 app version that is compliant with the new API header key and base URL, start by clicking on the Edit Step button for each Rev.io step.

Navigate to the App & Event pane for the connector and click on the Change button.

Type Rev.io into the action search box.

Navigate to the Account pane and click the button labeled Choose.

Select +Connect a new Account.

The new Zapier authentication screen with options for the Base URL and Header Key will pop up. Fill out the credentials and select Yes, Continue to Rev.io.

The authentication pop up will close and the Rev.io step will now make calls to the base URL supplied in the authentication screen, and will use the API header key with all API requests to Rev.io.