Skip to content

Adverse Actions

Adverse Actions are initiated by Checkr customers if something is returned on a Candidate’s report that requires further investigation. When an Adverse Action is initiated, the candidate must be informed, and given time to address the issues raised.

National and local laws control the Adverse Action process and define the sequence and timing with which it must process. Please work with your legal council to ensure that your process is compliant.

For more information, see The Adverse Actions Process in the Checkr Help Center.

Operations

Retrieve an existing Adverse Action

Request

Returns an existing Adverse Action with the input ID.

Security
basic_auth
Path
idstringrequired

ID of the Adverse Action.

curl -i -X GET \
  -u '<username>:<password>' \
  'https://docs.checkr.com/_mock/apis/openapi/adverse_actions/{id}'

Responses

Adverse Action details

Bodyapplication/json
idstring(ResourceId)read-only

ID of the resource.

Example:"e44aa283528e6fde7d542194"
objectstringread-only
Value:"adverse_action"
uristring(ResourceURI)read-only

URI of the resource.

Example:"/v1/adverse_actions/57ed51e57619e8002a6683f2"
created_atstring, (date-time)

Time at which the Adverse Action was created.

Example:"2016-09-29T17:39:49Z"
deliveryobject

Details about the delivery state of the Adverse Action.

statusstring

Status of the Adverse Action.

Enum:"pending""complete""dispute""canceled"
Example:"pending"
report_idstring

ID of the Report causing this adverse action.

Example:"b861a56db1b1b89692dd6118"
post_notice_scheduled_atstring or null, (date-time)

Timestamp at which the post Adverse Action notification will be sent. This time is dependent on the time at which the Pre-Adverse Action was created, and related settings within your Checkr system.

Example:"2016-10-07T12:34:00Z"
post_notice_ready_atstring, (date-time)

Timestamp after which the post notice can be sent. (Often 7 days after created_at.)

Example:"2016-10-06T17:39:48Z"
canceled_atstring or null, (date-time)

Time at which the Adverse Action was canceled.

Example:null
adverse_itemsArray of objects(AdverseItem)

Array of Adverse Items on which the Action is based.

individualized_assessment_engagedboolean
Default:false
contextstring or null

A customizable. semi-unique scoping identifier. Adverse Actions with a context have some special behaviors that do not affect the report adjudication and are not affected by most report adjudication actions. Multiple Adverse Actions can exist for a report as long as the context is unique for the report. Defaults to null.

Example:null
eventsArray of objects

A list of important lifecycle events.

Response
{
  "id": "e44aa283528e6fde7d542194",
  "object": "adverse_action",
  "uri": "/v1/adverse_actions/57ed51e57619e8002a6683f2",
  "created_at": "2016-09-29T17:39:49Z",
  "delivery": {
    "state": "delivered",
    "reason": "The email account that you tried to reach does not exist. Please double-check the recipient's email address for typos or unnecessary spaces.",
    "updated_at": "2016-09-29T17:39:49Z"
  },
  "status": "pending",
  "report_id": "b861a56db1b1b89692dd6118",
  "post_notice_scheduled_at": "2016-10-07T12:34:00Z",
  "post_notice_ready_at": "2016-10-06T17:39:48Z",
  "canceled_at": null,
  "adverse_items": [
    { … }
  ],
  "individualized_assessment_engaged": false,
  "context": null,
  "events": [
    { … }
  ]
}
© Checkr, Inc.