Integration of SpringVerify with RazorpayX

Integration of SpringVerify with RazorpayX

SpringVerify has built the external add candidate API and the Report API.
Clients can now generate JWT tokens from the security page and immediately begin utilizing our external APIs. Additionally, we've introduced a new page called 'Integrations' for Client Access (CA), where all these integrations will be listed.

On this page (https://portal.in.springverify.com/integrations), clients will find a comprehensive list of available integrations along with step-by-step instructions for each integration process. 

RazorpayX integration:

  • This page includes a card specifically for RazorpayX, featuring a 'Connect RazorpayX' call-to-action (CTA).

  • Clicking on this button directs users to a screen where step-by-step instructions are provided on how to generate an API key from the RazorpayX dashboard.

  • Users are also presented with a field to input the API key.

  • After entering the API key and clicking 'Connect', the integration will be activated.

(PS: There is no provision to individually select a package for each employee. Therefore, it is necessary to associate a designation or department with each employee to establish a package mapping. Without this association, the integration will not function properly.)

When the user clicks on "Connect":

  • The user will not be able to edit the API key field.

  • The "phone number" field in the external Add Candidate API will become optional for this company.

  • Upon clicking the "Connect" button, it changes to "Remove Connection," enabling the user to disconnect the integration if needed.


When the user clicks on the "Remove Connection" button:

  • The API key is deleted, and the API key field becomes enabled, allowing the user to add a new API key.

  • The "phone number" field in the external Add Candidate API becomes mandatory for this company.



When a company enables RazorpayX integration, the behavior of the External Add Candidate API regarding the Phone Number field should follow these rules:

  • If RazorpayX (RZP) integration is enabled:

    • The Phone Number field becomes optional for this company.

  • If RazorpayX (RZP) integration is disabled:

    • The Phone Number field is mandatory for this company.



    • Related Articles

    • Integration of SpringVerify with Lever

      Available For: User Roles Super Admin, Admin, Team Member, Limited Team Member Can only be configured by Super Admins Packages All Packages Lever's SpringVerify integration allows you to send candidates from Lever to SpringVerify in order to run a ...

    • A Guide to ‘Security Settings’ on SpringVerify

      What are the ‘Security Settings’ features on SpringVerify? ‘Security Settings’ features are the second layer authentication mechanism available to SpringVerify customers to improve protection against threats to the access and usage of ...

    • Integration of SpringVerify with Fountain

      Overview SpringVerify IN has developed integrations with Fountain, allowing users to use API Key from the Fountain platform. This integration streamlines and automates background verification processes within the Fountain environment. Note: Data will ...

    • Integration of SpringVerify with JobScore

      Overview SpringVerify IN has developed integrations with JobScore, allowing clients to use the API Key from the JobScore platform. This integration streamlines and automates background verification processes within the JobScore environment. Note: ...

    • Integration of SpringVerify with Factorial

      Overview: SpringVerify IN has developed integrations with Factorial, enabling clients to utilize the API key and API base URL from the Factorial platform. This integration facilitates a streamlined and automated approach to conducting background ...