---
title: "How Do Assessments Integrate With Your ATS or HRIS in the Gulf?"
description: "The four ways a score reaches your ATS — a native connector, middleware, a REST API with signed webhooks, or a share link that needs no integration at all — with what AssessAll actually ships, what it does not, and what Saudi PDPL transfer rules mean when results leave the Kingdom. Verified 5 September 2026."
canonical: https://www.assessall.com/solutions/hr-systems-integration-gulf
source: AssessAll
---

# Most assessment programmes in the Gulf never need an ATS integration. Here is how to tell whether yours does.

An assessment integration is the mechanism that carries a candidate from your ATS into a test and the score back again. Four mechanisms exist: a vendor-built native connector, a middleware flow, a REST API with signed webhooks, and a share link that needs no integration at all. Which one you need is decided by volume and data location, not by the vendor.

## What goes wrong today

- **Procurement asks for a connector before anyone has counted the hires** — The integration line item is usually written from a feature checklist rather than from volume. A connector that carries 60 candidates a year costs more to build and maintain than the sittings it delivers.
- **The word integration covers four very different things** — A native connector, a middleware recipe, a REST API you build against, and a CSV export are all sold under one word. They differ by an order of magnitude in effort and in what they can actually keep in sync.
- **The integration quietly moves personal data across a border** — The moment a result is pushed to a cloud ATS, someone has made a cross-border transfer decision. In Saudi Arabia that decision has a named legal basis and a documented risk assessment attached to it, and it is usually discovered late.
- **A long connector list answers a question you did not ask** — A published list of eighty systems tells you the vendor has partner engineering. It does not tell you whether the connector writes scores back, whether it carries the report or only a number, or whether it works with your version of the ATS.

## What AssessAll does

- **Share-link and QR delivery, no participant accounts** — A cohort link or QR code opens a proctored sitting directly. Candidates never create an account, so there is nothing to provision, nothing to de-provision, and no integration to build for a one-off drive or a campus day.
- **Assessment API v1 over REST** — List the assessments available to your organisation, create a sitting for a named candidate, read the sitting back, and fetch the scored result. Bearer-token authentication against a key issued in your workspace.
- **Signed webhooks for the four lifecycle events** — Receive sitting.started, sitting.scored, credential.issued, agent_sitting.scored, component.result and enrolment.updated at your own endpoint, and replay a missed window from GET /api/v1/events — the last seven days by default, 100 per page, oldest first, in exactly the envelope that was delivered. Verify the HMAC-SHA256 signature over the raw bytes before parsing; deliveries never carry an API key or the webhook secret.
- **A public OpenAPI 3.1 description** — The spec at /api/v1/openapi.json is served without authentication so a client generator — or an integration platform, or an LLM writing the first draft of your middleware recipe — can work from it directly.
- **Badges and credentials as an API resource** — Issued credentials are readable over the same API, so a verified capability record can be written into an HRIS profile or a national-programme dashboard without a person re-keying it.
- **Reports and exports for the systems that never integrate** — Scored reports download from the console, which is the correct answer for a government entity or a training provider whose system of record cannot accept an inbound call at all.

## Use cases

- Deciding whether an assessment integration belongs in this year's HR technology scope at all
- Answering an IT or procurement questionnaire that asks which ATS connectors a vendor ships
- Designing a volume hiring drive in Riyadh, Dubai or Doha that has to start before any integration could be built
- Connecting scored results to an HRIS or national-programme dashboard over the public API
- Establishing the cross-border transfer basis for assessment data before an integration goes live
- Retiring an integration that turned out to carry fewer candidates than the build cost

---

Source: https://www.assessall.com/solutions/hr-systems-integration-gulf