---
title: "Set job title eligibility verdict"
method: POST
path: "/v1/sandbox/employments/{employment_id}/job-title-eligibility-check"
tags: ["Sandbox"]
---

# Set job title eligibility verdict

`POST /v1/sandbox/employments/{employment_id}/job-title-eligibility-check`

## Request

- Base URL: `https://gateway.remote.com`
- URL: `https://gateway.remote.com/v1/sandbox/employments/{employment_id}/job-title-eligibility-check`
- Auth: one of:
  - OAuth 2
    - Authorization code: `/auth/oauth2/authorize`
    - Token URL: `/auth/oauth2/token`
  - OAuth 2
    - Client credentials
    - Token URL: `/auth/oauth2/token`
  - HTTP bearer

Sets the job title eligibility verdict the employment's next contract-details submission
will act on, so the flow that verdict drives can be tested without an AI call deciding
the outcome.

Use it to reach an outcome on demand: a submission that passes, one rejected as not
eligible, one that must carry `employer_acknowledges_risk`, or one that places the
employment into a human review and emits the review webhooks.

The response is the same as the real [job title eligibility check
endpoint](#operation/post_create_employment_job_title_eligibility_check). Send the
returned `check_id` back as `additional_job_title_eligibility_check_slug` when submitting
contract details, exactly as you would in production.

`role_description`, `role_is_onsite` and `role_requires_license` must be the answers the
job title eligibility check and the submission will carry, since both reuse the recorded
verdict only while it still describes what was sent. A role question the employment's
country does not ask is ignored.

A `not_assessed` verdict means the check does not apply to this employment at all — not a
draft, a PEO employment, a country or hiring model that does not screen job titles, or an
integration that bypasses the check — and nothing was recorded.

The stage of the check that screens the job title alone is shared by every company in the
environment, so setting a verdict takes over that job title's screen for all of them.

This endpoint is only available in Sandbox, otherwise it will respond with a 404.

## Authentication

This endpoint accepts any one of the following token types:

- **Company-scoped access token** (`OAuth2AuthorizationCode`) — obtained by a company manager through the Authorization Code flow or the Refresh Token flow. See [Authentication for partners](https://developer.remote.com/docs/authentication-for-partners).
- **Company-scoped access token (assertion)** (`OAuth2CompanyManagerAssertion`) — obtained through the `urn:ietf:params:oauth:grant-type:jwt-bearer` grant for a company manager. See [OAuth Assertion](https://developer.remote.com/docs/authorization-method-oauth-assertion).
- **Customer API token** (`CustomerAPIToken`) — generated by the customer on their Integration Settings page, with the scopes they choose there. See [Authorization for customers](https://developer.remote.com/docs/authorization-for-customers).

## Path parameters

- `employment_id` string, required

## Request body

- SetJobTitleEligibilityVerdictParams
  - `job_title` string: The job title to record the verdict against. Defaults to the employment's current one.
  - `role_description` string, required: The role description the submission will carry. A submission carrying a different one is rejected, because the recorded verdict no longer describes what was sent.
  - `role_is_onsite` 'yes' | 'no': The answer the job title eligibility check will be sent for whether the role is onsite. Required when the employment's country asks the question, and ignored when it does not.
  - `role_requires_license` 'yes' | 'no': The answer the job title eligibility check will be sent for whether the role requires a license. Required when the employment's country asks the question, and ignored when it does not.
  - `verdict` 'eligible' | 'not_eligible' | 'needs_review' | 'eligible_with_risk_acknowledgement', required: The verdict the employment's next contract-details submission should act on.

## Response `200`

Success

- JobTitleEligibilityCheckResponse
  - `data` object, required
    - `job_title_eligibility_check` JobTitleEligibilityCheck, required
      - `check_id` string, nullable: The identifier of the recorded check. When present it is **required**: send it back as `additional_job_title_eligibility_check_slug` when submitting contract details, or the submission is rejected. Run this check again if the job title or any role answer changes, since the identifier only vouches for the answers it was given. `null` when the job title alone settled the verdict and there is nothing to send.
      - `verdict` 'eligible' | 'not_eligible' | 'needs_review' | 'eligible_with_risk_acknowledgement' | 'not_assessed', required: The eligibility verdict for the submitted job title and role. `eligible` means contract details can be submitted as normal. `not_eligible` means Remote cannot employ this role: the title has to change. `needs_review` means submitting will place the employment in a human review before the employee can be invited. `eligible_with_risk_acknowledgement` means the submission must carry `employer_acknowledges_risk` set to `acknowledged`. `not_assessed` means the check did not run for this employment and no verdict was formed, so treat it as unknown rather than as a pass: submitting is not blocked, but nothing has screened the title. When the verdict is `eligible_with_risk_acknowledgement`, present Remote's responsibility statement to the employer and obtain their acceptance before sending `employer_acknowledges_risk`. Sending it asserts that the employer was informed of, and accepted, responsibility for, as applicable, employee safety, training, health checks, any incidents connected to the employee's work environment, and the employee holding the licensing the role requires.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `404`: Not Found
- `422`: Unprocessable Entity
- `429`: Too many requests

---

[API](https://skmtc.dev/remote-com/apis/testing-sandbox.md) - [All operations](https://skmtc.dev/remote-com/apis/testing-sandbox/llms.txt) - [OpenAPI document](https://skmtc.dev/remote-com/apis/testing-sandbox/revisions/94f6859e2604?raw)