Information Direct
Documentation

API and integration readiness

Programmatic ordering, report handoff, and webhook workflows are available only by approved implementation path. This guide explains what we can scope today and what details we need before enabling automation.

Current availability

Information Direct does not currently offer anonymous self-serve API keys from the website. API and integration work is scoped with operations so we can confirm permissible purpose, release-form handling, security controls, billing, and provider requirements before any automated fulfillment begins.

For most clients, the first step is the client dashboard: submit order requests, attach release forms, request report access, and create an audit trail. Automation can be layered in after account setup and provider sign-off.

What we can scope

  • Order intake. Structured order requests from an ATS, HRIS, internal form, or approved dashboard workflow.
  • Status handoff. Status updates back to your team by dashboard, email, secure report access, or approved webhook pattern.
  • Report access. Report viewing through approved credentials or provider SSO where enabled for your account.
  • Batch workflows. CSV or structured batch intake for staffing, seasonal hiring, and high-volume programs.
  • Webhook planning. Event design for order received, release form reviewed, in research, report ready, dispute, and adverse-action support requests.

Security requirements

Any API or automated integration must keep provider credentials server-side, avoid logging raw SSNs or dates of birth, use TLS, restrict access by role, and maintain an audit trail. Webhook endpoints must be validated before production use. If a third-party provider does not support signed webhooks, we use compensating controls such as IP allowlisting, credential matching, rate limiting, and queue-based processing.

Information needed before API work

  • Business entity, billing contact, and authorized technical contact.
  • Permissible purpose and screening use case.
  • Expected monthly volume and peak batch size.
  • Package or search matrix by role.
  • Release-form and candidate-consent process.
  • Target system: ATS, HRIS, internal app, or procurement platform.
  • Security requirements such as SSO, IP allowlists, data retention, and audit export.

Typical integration phases

  1. Discovery. Confirm legal use case, data flow, package matrix, billing, and security requirements.
  2. Staging. Validate non-production payloads, order references, report handoff, and failure handling.
  3. Limited launch. Run a small set of approved orders with operations monitoring every step.
  4. Production rollout. Expand volume after turnaround, reporting, and support workflows are stable.

Request integration scoping

Email support@informationdirect.us or contact your account manager with the system you want to connect, the packages you need, and your expected monthly volume. We will confirm whether dashboard workflow, batch intake, provider SSO, or a custom integration is the right next step.

Was this helpful? Tell us what's missing
Create Account