Log in Contact
Back to Platform
Platform For organisations 2 min read

Can I integrate Pescheck with my own systems via API?

Yes. Pescheck offers an API for triggering screenings, tracking status, and pulling reports. Used for custom ATS, HRIS, and onboarding integrations.

Last updated

In short: Yes. Pescheck provides an API so you can trigger screenings, track progress, and pull reports programmatically. This is the right path if you build custom HR tooling, run high volumes that benefit from automation, or have a proprietary ATS that is not on our standard integration list.

When API integration is the right choice

Customers typically choose the API over a native ATS integration when:

  • They have built a proprietary HR or onboarding tool internally
  • They use multiple HR tools and need a single integration point
  • They are at a volume where manual screening creation is no longer practical
  • They need to embed screening triggers into a non-HR workflow (e.g. a marketplace platform that vets vendors)

If you use a standard ATS like Workday, Personio, Greenhouse, BambooHR, HiBob, Lever, or Bullhorn, see our integrations first; a native integration is usually faster to deploy.

What the API supports

In practice, customers use the API to cover the full screening lifecycle: starting a screening for a candidate, monitoring progress through each individual check, and retrieving the finished report once available. Webhooks are supported so you do not have to poll for updates.

Full documentation for the current endpoints, authentication, rate limits, and request/response schemas is on the API documentation page. The documentation is the source of truth; we keep it current.

Authentication and security

The API uses standard token-based authentication over TLS. Each customer has separate API credentials with audit logging of every request. Rate limits are generous for normal use but exist to protect the platform from accidental loops. Service accounts can be created so your integration uses its own identity rather than a personal user’s credentials.

Typical integration patterns

Three patterns we see most often:

  1. Triggered from a proprietary ATS or HRIS: when a candidate reaches a hiring stage, your system calls the API to create a screening, then waits for a webhook to fire when the report is ready.
  2. Onboarding flow: when a new hire signs their contract, your onboarding tool kicks off an in-employment screening for regulated roles, then surfaces the result to the manager.
  3. Custom recruitment portal: an internal portal where recruiters submit candidates calls the API to send screenings without a UI handoff to Pescheck.

Sandbox and testing

A sandbox environment is available so you can build and test against the API without affecting real screenings or being billed. Credentials for the sandbox are issued during the integration discussion.

Where to start

Feedback
Was this article helpful?
Still stuck?

Get a personal answer from our team.