First Advantage Authenticate an element Instance

You can authenticate with First Advantage to create your own instance of the First Advantage element through the UI or through APIs. Once authenticated, you can use the element instance to access the different functionalities offered by the First Advantage platform.

Authenticate Through the UI

Use the UI to authenticate with First Advantage and create an element instance. You will need your Account ID, Authorization Key, and the Host Name mentioned in API Provider Setup.

Authenticate Through API

Step 1. Create an Instance

To provision your First Advantage element, use the /instances API.

Below is an example of the provisioning API call.

HTTP Headers: Authorization- User , Organization
HTTP Verb: POST
Request URL: /instances
Request Body: Required – see below

token is returned upon successful execution of this API. This token needs to be retained by the application for all subsequent requests involving this element instance.

A sample request illustrating the /instances API is shown below.

HTTP Headers:

Authorization: User <INSERT_USER_SECRET>, Organization <INSERT_ORGANIZATION_SECRET>

This instance.json file must be included with your instance request. Please fill your information to provision. The “key” into Cloud Elements First Advantage is firstadvantage. This will need to be entered in the “key” field below depending on which element you wish to instantiate.

{
  "element": {
    "key": "firstadvantage"
  },
  "configuration": {
    "filter.response.nulls": "true",
    "accountId": "<ACCOUNT_ID>",
    "hostname": "<HOST_NAME>",
    "authorization.key": "xxxxxxxxxxxxxxxx"
  },
  "name": "<INSTANCE_NAME>"
}

Here is an example cURL command to create an instance using /instances API.

Example Request:

curl -X POST
-H "Authorization: User <INSERT_USER_SECRET>, Organization <INSERT_ORGANIZATION_SECRET>"
-H "Content-Type: application/json"
-d
'{
  "name": "<INSTANCE_NAME>",
  "configuration": {
    "filter.response.nulls": "true",
    "accountId": "xxxxxxxxx",
    "authorization.key": "xxxxxxxxxxxxxxxxxxx",
    "hostname": "<HOST_NAME>"
  }
}'

If the user does not specify a required config entry, an error will result notifying her of which entries she is missing.

Below is a successful JSON response:

{
  "id": 123456,
  "name": "<INSTANCE_NAME>",
  "createdDate": "2019-09-20T05:36:56Z",
  "token": "xxxxxxxxxxxxxxxx",
  "elementId": 123,
  "tags": [
    "<TAGS>"
  ],
  "provisionInteractions": [],
  "valid": true,
  "disabled": false,
  "maxCacheSize": 0,
  "cacheTimeToLive": 0,
  "configuration": {
    "bulk.add_metadata": "false",
    "base.url": "<BASE_URL>",
    "allow.select.fields": "true",
    "event.notification.subscription.id": null,
    "default.select.fields.map": null,
    "event.notification.basic.username": "",
    "bulk.query.field_name": "updatedOn",
    "pagination.max": "100",
    "event.notification.basic.password": "********",
    "event.objects": null,
    "event.objects.map": null,
    "bulk.query.operator": ">=",
    "filter.response.nulls": "true",
    "bulk.query.date_mask": "yyyy-MM-dd'T'HH:mm:ssXXX",
    "bulk.query.download_format": "json",
    "event.notification.instance.finder": "",
    "bulk.relations": "{}",
    "pagination.type": "offset",
    "event.poller.refresh_interval": "",
    "api_key": null,
    "event.poller.urls": null,
    "subdomain": null
  },
  "authenticationType": "custom",
  "eventsEnabled": false,
  "cachingEnabled": false,
  "traceLoggingEnabled": false,
  "organizationId": xxxx,
  "accountId": xxxxx,
  "externalAuthentication": "none",
  "userId": xxxxx,
  "element": {},
  "user": {
    "id": xxxxxx
  }
}

Instance Configuration

The content in the configuration section or nested object in the body posted to the POST /instances or PUT /instances/{id} APIs varies depending on which element is being instantiated. However, some configuration properties are common to all elements and available to be configured for all elements. These properties are -

event.notification.enabled: This property is a boolean property, and determines if event reception (via webhook or polling) is enabled for the element instance. This property defaults to false.
event.vendor.type: When event.notification.enabled property is set to true, this property determines the mechanism to use to receive or fetch changed events from the service endpoint. The supported values are webhook and polling. Most elements support one mechanism or the other, but some like Salesforce.com support both mechanisms. This property is optional.
event.notification.type: This property can be used to determine how an event notification should be sent to the consumer of the element instance, in most cases your application. Currently, webhook is the only supported value for this property. This means that when an event is received by the element instance, it will get forwarded to the provided event.notification.callback.url via a webhook to you. This property is optional.
event.notification.callback.url: As mentioned above, the value of this property is an http or https URL to which we will post the event for consumption by your application. This property is optional.
filter.response.nulls: This property defaults to true, i.e., it's boolean property, and determines if null values in the response JSON should or should not be filtered from the response returned to the consuming application. By default, all null values are filtered from the response before sending the response to the consuming application.