VidCruiter

VidCruiter Partner Integration API

The real, documented programmatic surface. VidCruiter provisions each institution a unique web-services API endpoint (obtained from a VidCruiter account representative) used for bidirectional integration with a system of record. In the documented Slate pattern, the ATS pushes application records to VidCruiter via a web-service export authenticated with a user token passed as a query string, and VidCruiter returns a ShareableProfileUrl for each completed interview via an API call, using a timestamp parameter so only new records are retrieved. Endpoints are per-tenant and account provisioned; no public base URL or reference is published.

GitHub

Documentation

📖
Documentation
https://vidcruiter.com/integrations/

Other Resources

🔗
IntegrationGuide
https://knowledge.technolutions.net/docs/vidcruiter-integration
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/vidcruiter/refs/heads/main/apis.yml

API entry from apis.yml

apis.yml Raw ↑ 
aid: vidcruiter:vidcruiter-partner-integration-api
name: VidCruiter Partner Integration API
tags:
- Integration
- Web Services
- ATS
- Partner
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://vidcruiter.com/integrations/
endpointsModeled: true
accessModel: partner-gated
properties:
- url: https://vidcruiter.com/integrations/
  type: Documentation
- url: https://knowledge.technolutions.net/docs/vidcruiter-integration
  type: IntegrationGuide
description: The real, documented programmatic surface. VidCruiter provisions each institution a unique
  web-services API endpoint (obtained from a VidCruiter account representative) used for bidirectional
  integration with a system of record. In the documented Slate pattern, the ATS pushes application records
  to VidCruiter via a web-service export authenticated with a user token passed as a query string, and
  VidCruiter returns a ShareableProfileUrl for each completed interview via an API call, using a timestamp
  parameter so only new records are retrieved. Endpoints are per-tenant and account provisioned; no public
  base URL or reference is published.