See what the Revel integration can do →
Integrate iPaaS.com with Revel to enable seamless data synchronization for employee and timesheet records.
How to Connect
Prerequisites
Before setting up the Revel integration in iPaaS.com, ensure you have the following:
API credentials
Contact Revel to request REST API access for your account. Revel provides an API Key and an API Secret during that setup. Revel does not publish a self-service flow for generating REST API credentials, so these must be requested rather than created in the management console.
A Revel user for record attribution
Revel records the user that created and last updated every record it stores. Identify the Revel user that the integration should write records as, and note its user ID. This value is entered in iPaaS.com as the AgentId setting.
Your Revel site address
Revel hosts each customer on their own subdomain rather than a single shared address. Note the address you use to sign in to Revel — it takes the form https://yoursubdomain.revelup.com — as this is the value entered as the API Url setting.
Configuration Details
The following values are needed to complete the connection:
API Url: the base address of your Revel site, in the form https://yoursubdomain.revelup.com. Use the same subdomain you sign in with. Example: https://acmerestaurants.revelup.com
API Key: the key Revel provides with your API access. Example: ead9cbb8327c40c7b7ea7c7d243ac26e
API Secret: the secret Revel provides alongside the key. Treat it as a password and do not share it.
AgentId: the identifier of the Revel user that records created by the integration are attributed to. Example: 1234
Configure Subscription Settings
Navigate to the Revel subscription settings in iPaaS.com and provide the following information:
Field | Description | Required | Example |
Name | A unique name identifying this subscription in iPaaS.com. | Yes | Revel Production |
Versions | The integration version to use. | Yes | v1.0 |
Create Default Mappings | Creates the standard set of mapping collections when the subscription is saved. Leave selected unless you intend to build every mapping collection yourself. | No | Selected |
AgentId | The Revel user ID that records created by the integration are attributed to. Must be a valid Revel user. | Yes | 1234 |
API Secret | The secret provided by Revel with your API access. | Yes | Provided by Revel |
API Key | The key provided by Revel with your API access. | Yes | Provided by Revel |
API Url | The base address of your Revel site, including your subdomain. | Yes |
Authentication Methods
Revel authenticates each request with a key and secret sent together in a single header. iPaaS.com constructs that header from the values you enter, so there is no separate sign-in step, token exchange, or consent screen to complete.
To authenticate the integration:
Navigate to the Revel subscription settings in iPaaS.com.
Enter the following details:
API Url
API Key
API Secret
AgentId
Save the configuration and test the connection. iPaaS.com verifies the credentials by retrieving your Revel company record.
Upon successful authentication, a confirmation message is displayed.
If the test fails, the most common causes are an API Url pointing at the wrong subdomain, or a key and secret that have not yet been enabled for REST API access by Revel.
Note: AgentId is not part of authentication. It identifies the Revel user that records are attributed to, and it is used when the integration writes employees and timesheets into Revel. A connection can authenticate successfully with an invalid AgentId, but writes into Revel will then fail. Confirm the value is a valid Revel user before enabling any outbound collection.
Initialization Support
Currently, initialization is not supported for Revel in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process.
Because there is no bulk import on first connect, existing employee and timesheet history is not loaded automatically. Subscribers or their MiSP who need to seed historical records should use bulk sync using Postman.
Throttling
Throttling ensures that Revel's API isn't overwhelmed by excessive API calls, preserving system performance during heavy data transfers.
While the throttling fields are required, the values are pre-populated by the integration settings. For more details, refer to Subscription Configuration – Edit.
Revel does not publish a numeric rate limit or call quota. Revel does enforce a daily call allowance, and requests that exceed it are rejected until the allowance resets; those rejections appear in Dashboard / Integration Monitoring / Error Logs. Because the published limit is unspecified, stagger large transfers rather than running several intensive jobs at the same time.