Partner Integration Intake Form - Screening Direct

Partner Integration Intake Form - ScreeningDirect

Thank you for your interest in integrating with the Sterling API. Please complete this form to provide all necessary information for our Product Management team to review and support your integration.

ATS Partner(Required)

Name of the Partner Integration built to Sterling API.

Platform/Product Name(Required)

Name of the Platform or Product building to Sterling API.

Supported Workflow(Required)

Please confirm which workflow is supported by your integration.
Documentation Link: Learn More
[Post Screenings Workflows]

Seamless Advanced: Candidate receives an email invite to ScreeningDirect for data collection before order submission.

Seamless: Candidate data is collected up front, allowing for the customer user to initiate the screening without additional candidate data submission.

Recruiter Interactive: Determine at time of order submission which of the above workflows each order should take.

Other

SMS Invites(Required)

Optional enhancement to support capturing candidate's consent to receive SMS messages (to support this functionality, please pass the 'candidateConsentedForSMS' field as part of the Order Request, as well as candidate's mobile phone number).
Documentation Link: Learn More
[Post /screenings (Sterling Data Collection) Headers > Body raw]
Please confirm if supported.

Yes

Location of Employment(Required)

Optional enhancement to support downstream workflows by capturing the City, State, and Country values of the job being applied to (to support this functionality, please pass the 'locationOfEmploymentCity', 'locationOfEmploymentState', and 'locationOfEmploymentCountry' values as part of the Order Request).
Documentation Link: Learn More
[Post /screenings (Sterling Data Collection) Request Body Fields]
Please confirm if supported.

Yes

Language Translation(Required)

Optional enhancement to support translation of First Advantage candidate-facing materials to meet candidate's preferred language needs (to support this functionality, please pass the 'primaryLanguage' field as part of the initial Order Request).
Documentation Link: Learn More
[Post /Candidates > Required Fields > Request Body Fields table]
Please confirm if supported.

Yes

A-la-Carte Ordering(Required)

Please confirm if orders for specific products can be submitted through the integration without an associated package.
Documentation Link: Learn More
[NOTE: Supported through ScreeningDirect by standard.]

Yes

Regionalization(Required)

Please provide a list of the Regions (and Region definitions) supported for this integration.
Documentation Link: Learn More
[NOTE: Sterling API Data will be stored in regional data centers]

Multi-Region Support(Required)

Can orders be routed between different regions?

Yes

Authentication Method (Request & Response)(Required)

The Sterling API uses an OAuth2 ("OAuth") authentication scheme. It supports the US, EMEA, Canada and APAC regions. Requests to the Sterling API must be authenticated using short-lived bearer token in the Authorization header.
Documentation Link: Learn More
Please confirm whether the customer will be configured to use OAuth.

Yes

Order Level Status(Required)

Are status callbacks of the entire background check order supported, and is mapping present?
Documentation Link: Learn More

Yes, with mapping

Yes, without mapping

Please provide a mapping table (Order Level Status).(Required)

Max. file size: 15 MB.

Order Level Results(Required)

Are score/result callbacks of the entire background check order supported, and is mapping present?
Documentation Link: Learn More

Yes, with mapping

Yes, without mapping

Please provide a mapping table (Order Level Results).(Required)

Max. file size: 15 MB.

Search/Component Level Status(Required)

Are status callbacks of individual components within the entire order supported, and is mapping present?

Yes, with mapping

Yes, without mapping

Please provide a mapping table (Search/Component Level Status).(Required)

Max. file size: 15 MB.

Search/Component Level Results(Required)

Are score/result callbacks of individual components within the entire order supported, and is mapping present?

Yes, with mapping

Yes, without mapping

Please provide a mapping table (Search/Component Level Results).(Required)

Max. file size: 15 MB.

Callbacks/Webhooks(Required)

Has this integration implemented callbacks for status updates?

Yes

Real-Time Order Status Callbacks(Required)

Are real-time status callbacks of individual components within the order supported?
Documentation Link: Learn More

Yes, for Order Statuses only

Yes, for Search Level only

Yes, for both Order Statuses and Search Level

Adjudicated Statuses and Results(Required)

Can this integration support other results being returned from First Advantage platforms (besides Clear/Consider), and is mapping in place?
Documentation Link: Learn More
[NOTE: This functionality should be supported by default.]

Yes, with mapping

Yes, without mapping

Please provide a mapping table (Adjudicated Statuses and Results).(Required)

Max. file size: 15 MB.

Enhanced Adverse Action(Required)

Please confirm if this integration can receive Enhanced Adverse Action Statuses.

Final Report Access(Required)

How can customers access the final First Advantage Report?

Document Upload

Report URL

Both

Enable Candidate Data Postback to ATS(Required)

Does this integration retrieve any candidate data? If so, please specify which data points are included and the method used to retrieve them.

Document Retrieval(Required)

Which documents, if any, are being retrieved through the API?

Billcodes(Required)

Differentiate between the customer's various billing departments (identifiers for finance purposes).
Documentation Link: Learn More
[Post /Screenings Request Body Fields]
Please confirm if supported.

Yes

Subaccounts(Required)

Differentiate between different locations within a customer organization (identifiers for various purposes).
Documentation Link: Learn More
Please confirm if supported.

Yes

Package Sync(Required)

Does this integration support Package Sync functionality?
Documentation Link: Learn More
Please confirm if supported.

Yes

User Management(Required)

Will this integration support multiple distinct customer users, or only a single default user?

Multiple unique customer users

One default user

Additional Functionality(Required)

Is there any additional functionality we should be aware of for training or marketing purposes?

Available Partner Sandbox Environment(Required)

Is there a sandbox environment for First Advantage team to access?

Yes

Known Limitations(Required)

Are there any limitations we should be aware of for marketing or training purposes?

Deployment Environment(Required)

Are customers able to test the integration in a QA/Test environment prior to production deployment?

Yes

Onboarding Process(Required)

Please provide some visibility into your onboarding process.

Available Documentation(Required)

Please indicate whether any existing or planned internal collateral is available for this integration (e.g., User Guide, Deployment Guide, demos, training videos, etc.).

FAQ(Required)

Please note any frequently asked questions related to this integration, if applicable.

Integration Marketing Promotion(Required)

Is there any need for the First Advantage team to submit training/marketplace materials separately? If yes, please provide more information.

Technical Contact Information(Required)

Please provide the email address of the primary Technical Contact for this integration.

Product Contact Information(Required)

Please provide the email address of the primary Product Contact for this integration.

Pre-Hire: Screen & Verify

Onboard: Engage & Empower

Post-Hire: Monitor & Protect

Additional Solutions

Audience Spotlight

By Business Size

Industry Expertise

Integrations

Overall Digital Identity Solution Provider of the Year

About First Advantage

Newsweek’s World's Most Trustworthy Companies 2025 Winner

Background Check Resources

Get Help