Skip to main content

Integration Manager - Getting Started

Evan Nelson avatar
Written by Evan Nelson
Updated over 4 months ago

What we'll review:

Integration Manager Overview

Integration Partnership and Resource Requirements

Configuring Clients in IM

Configuring Packages in IM

Pricing

Submitting an Integration Support Ticket

Integration Manager Overview

In our fast moving world of technology, you will likely come across clients who are dependent on their specific Applicant Tracking Systems (ATS). In order to win the business, you may find a connection to that particular ATS to be non-negotiable, and this is where we step in. Deverus' Integration Manager takes the waiting out of important integrations you need to bring on new business. With our Integration Platform as a Service (I-PAAS), you can DIY standard integrations in a matter of minutes, not weeks! A list of all existing integrations can be found under the Integration tab -> Home (any existing integrations will have a tile in this list with their logo):

Additionally, Integration Manager provides a fully accessible open API that enables partners and clients to create new connections with their systems. Extensive documentation and support are available to ensure seamless implementation of these integrations. For developers and third-party systems, detailed VeroConnect API documentation is available at: https://deverus.stoplight.io/.

Manager Highlights:

  • Seamless Connectivity

  • In-depth dashboard metrics

  • Order details visibility

  • Secure Scalable Platform

  • Self-service standard integrations with new customers

  • Open API

On the Integration Manager home page, you can have at-a-glance insights into integration events in Verocity. The information is presented in different sections including a panel with a list of available applicant tracking systems’ (ATS) connections; aggregate numbers showing statistics on the total reports run for all ATSs, fail attempts, fail rate, and average turnaround time; set of charts representing meaningful integration data, and a table of current clients with integration errors.

Get Started with IM

To get started with Integration Manager:

Verify ATS is available: Any admin that has permissions for Integration Manager can view the list of currently available Applicant Tracking Systems. If the ATS is not available, you are welcome to submit a Support ticket to see if the desired ATS is scheduled to be added or if a discovery call is needed.

Establish a relationship: Next you must establish a relationship with the ATS your client wants to utilize. Each ATS may have different requirements for partnership or other cost involved. For a list of ATS's and contact information, please review ATS Integrations Information.

Ensure integration is standard: Review the ATS standard integration information with your client. Each ATS has a basic workflow and information fields that come with standard with their product.

Receive Credentials - Once you have an established an agreement with the ATS and client, you are ready to utilize the integrations manager! From here you must ensure the ATS has sent you the credentials needed. Please review standard credentials below for specific ATS information.

Enter Client into Integration Manager- You are ready to integrate!

Integration Partnership and Resource Requirements

The table below outlines the current ATS connections that deverus offers via Integration Manager and which ones are known to require a partnership with the ATS and/or other technical resources. Click the embedded links where applicable to visit an ATS's specific Knowledge Base article for more detailed information.

Partnership Required

Non-Partnership or Basic Agreement

Contingent on Requestor's Technical Resource(s)

JazzHR

Apploi

VeroConnect

Avionte

Fountain

TenStreet

ClearCompany

talentReef

SmartRecruiters

Greenhouse

PageUp

Bullhorn

Jobvite

PositionManager

iCIMS

Ceridian

Definitions:

Partnership Required: As a CRA, you must meet certain requirements as dictated by the ATS before being allowed access to utilize the integration.

Non-Partnership or Basic Agreement: The ATS does not require a partnership in order to use the integration. However, some ATS may require an agreement for monthly or annual fees to utilize their API’s.

Contingent on Requestor’s Technical Resource: When coding to the VeroConnect API, the level of difficulty/complexity/project timeline/etc. are determined by their development resource(s)’ technical capability.

Configure Clients in Integration Manager (IM)

Follow these steps to add a client to Integration Manager and configure their ATS integration:

1. Set up the client's account in Verocity.

2. Work with the ATS on any partnership requirements, and ensure no other technical resources are required for the connection to be made (as outlined in the table above). Once these items are completed or confirmed, you are ready to integrate the client with their ATS!

3. Click the Integration tab -> Home:

4. Select the associated ATS tile:

5. Select 'Configure Existing Client:'

6. Use the type-ahead field (minimum of x3 characters) to locate and select the appropriate client you need to configure:

7. Select the type of report results link:

8. To use SwiftHire Mobile, toggle ‘Use SwiftHire’ on. Otherwise, leave toggled off for direct ordering -> click 'Next'

  • Please note: Some ATS connections require the use of Swifthire

9. Save the configurations and close the frame:

10. Locate the account that you just created and select ‘Settings’ → ‘Credentials’ → Toggle on ‘Show Private Credentials’ → Copy API Private Key and Integration URL. The copied API Key and Integration URL can be provided to the client to provide to the ATS.




Configure Packages in Integration Manager (IM)

The Package mapping logic for Integration Manager is based off of two items: Client Type Packages or Designated Client Packages.

The Designated Client is the client that is actually used to generate the specific connection through IM. Usually this is the ClientID that is at the top of a branched structure.

Packages under the Designated ClientID will be available in the IM Mapping Settings.

Any packages saved in the Client Type associated with the Designed ClientID will be available as well.

If packages are saved under a specific branch, those packages will not be available to be mapped.


Integration Connection Pricing

Self-Service Integration (No Cost)

We continue to provide comprehensive resources for self-implementation:

- Detailed integration documentation

- Step-by-step implementation guides

- Access to our knowledge base

These resources remain completely free and are sufficient for most standard integration scenarios.

Premium 14-Day Support Package ($2,250)

For situations requiring direct assistance from our team, we offer a 14-day support package:

- Direct access to our integration specialists

- Technical troubleshooting and guidance

- Implementation assistance

- Configuration help

- Testing support

How the 14-Day Support Package Works

- 14 consecutive business days of support

- Access to our integration team during business hours

- Email and ticket-based support

- Assistance with your specific integration challenges

How to Purchase

1. Create a support ticket

2. Review and sign the Statement of Work (SOW)

3. Submit payment (Net 30 terms available for eligible accounts)

4. Schedule your support period start date

Important Details

- The 14-day period begins on your first day of engagement

- Support access ends after 14 business days

- Additional support requires purchasing a new package

- The package is non-refundable and cannot be paused or extended

Frequently Asked Questions

**Q: Why did you change to a 14-day support model?**

A: This model provides clearer expectations for both parties and eliminates the complexity of tracking individual support hours. It also encourages focused, efficient integration work.

**Q: What if I only need a quick question answered?**

A: Our knowledge base and documentation should address most common questions. For technical questions requiring our team's attention, the support package applies.

**Q: Can I split the 14 days across multiple months?**

A: No, the 14 days must be used consecutively from the start date.

**Q: What happens if my integration takes longer than 14 days?**

A: If you need additional support beyond the initial 14 days, you can purchase another support package.

**Q: Is there a limit to how many questions or issues I can raise during the 14 days?**

A: No, you can submit multiple support requests during your active support period.

## Best Practices for Successful Integration

To maximize the value of your integration experience:

1. Review all documentation before beginning implementation

2. Have your technical resources ready before starting your support period

3. Prepare specific questions or issues in advance

4. Ensure necessary access and permissions are in place

5. Schedule your support period when your team is fully available

Submit Integration Support Ticket

As noted in the Partnership and Resource Requirements chart, most integrations do not require any deverus resources and can be configured and tested by the CRA. However, if direct assistance is required by a deverus resource or could potentially code to VeroConnect, we ask that you submit a Support ticket with the following information for faster service

  1. Is this for a current client or prospect? What is the name of the company?

  2. Please provide the name of the ATS/HRIS.

  3. Is there a desired timeline to go-live?

  4. What is the estimated annual or monthly report volume (number of applicants they expect to run through the integration)?

  5. Do you know which search types may be ordered?

  6. Would ordering be submitted via SwiftHire Mobile?

  7. Do they currently have a consultant who would complete the required configurations in their ATS/HRIS instance?

  8. Is there API documentation publicly available so that we can review internally? If so, please provide a link to the documentation here.

Did this answer your question?