Bullhorn Data Replication Amplify Data Payloads

This article outlines Amplify data payloads accessible via Bullhorn Data Replication. You can import Amplify data, both internally and externally, through Bullhorn Data Replication, allowing you to customize your reporting and meet specific requirements.

Understanding Amplify Data in Data Replication

Data Replication includes four key tables. Three of these (EdsSourceSystem, EdsEntityType, and EdsEntityTypeSchemaVersion) are metadata tables that catalog available data sources, entity types, and schema versions.

These metadata tables do not contain the data itself. Instead, they describe what data exists and how it is structured. You’ll find entries for Amplify in these metadata tables.

The actual data payloads are stored in the EdsData table. This is the table you’ll query when retrieving Amplify data for reporting.

Example Use Cases

• Measuring screening metrics, such as completions in the last 7 days

• Identifying candidates screened in the last seven days with screening scores over 80

• Evaluating candidate performance based on experience ratings

Requirements

Data Replication is not supported for Bullhorn Recruitment Cloud clients.

To use Amplify data payloads, you must have:

• Bullhorn Amplify Edition
• Bullhorn Data Replication or Bullhorn Analytics Enterprise

Data Structure

Screener Payload Example

{
  "transcriptNoteId": 5001,
  "candidateId": 1001,
  "jobOrderId": 2001,
  "jobSubmissionId": 3001,
  "status": "Complete",
  "durationInMinutes": 30,
  "score": 85,
  "rating": 4,
  "comments": "Strong candidate with relevant experience",
  "screeningStats": {
    "questions": 10,
    "answered": 9,
    "skipped": 1
  },
  "interactionType": "Voice",
  "userChoseInteractionType": true
}

Data Payloads

Bullhorn Data Replication receives Amplify data in structured JSON payloads. Each payload represents one entity, and the structure varies depending on the data type.

• Data is delivered as a single JSON entity field per payload.

• Each data type has its own structure.

• Use source IDs to link records to Bullhorn entities.

• If you're new to JSON, refer to this Microsoft article for an introduction.

  This is a third-party resource provided for convenience. Bullhorn does not endorse or manage its content.

Amplify payloads comprise of the following:

Data Fields

Screener Data Fields

Screener Payload Example

{
  "transcriptNoteId": 5001,
  "candidateId": 1001,
  "jobOrderId": 2001,
  "jobSubmissionId": 3001,
  "status": "Complete",
  "durationInMinutes": 30,
  "score": 85,
  "rating": 4,
  "comments": "Strong candidate with relevant experience",
  "screeningStats": {
    "questions": 10,
    "answered": 9,
    "skipped": 1
  },
  "interactionType": "Voice",
  "userChoseInteractionType": true
}

Outreach Data Fields

Outreach Payload Example

{
    "sourceSystem": "Amplify",
    "entityType": "Events",
    "schemaVersion": "1",
    "items": [
      {
        "sourceId": 123456,
        "payload": "{\"Customer_Id\":42,\"Id\":123456,\"Type\":\"Send\",\"Url\":null,\"PageTitle\":null,\"Description\":\"Email sent via outreach automation\",\"AutomationId\":789,\"SurveyId\":null,\"EmailTemplate_Id\":101,\"TextMessageTemplate_Id\":null,\"IsAmplify\":true,\"OwnerId\":55,\"BullhornCandidateId\":98765,\"BullhornSalesContactId\":null,\"BullhornLeadId\":null,\"BullhornJobId\":null,\"DateCreated\":\"2025-01-15T14:30:00Z\",\"DateModified\":null}",
        "isDeleted": false,
        "candidateId": 98765,
        "leadId": null,
        "jobOrderId": null,
        "clientContactId": null,
        "corporateUserId": 55,
        "dateAddedInSourceSystem": 1736952600000,
        "dateLastModifiedInSourceSystem": null
      }
    ]
  }

FAQ

What do the different date fields represent?

• dateAdded: The date the record was added to the EDS table.

  This may not match the event date if replication was delayed.

• dateAddedInSourceSystem: The date and time the event originally occurred. For example, this captures when a candidate started a screener, even if they did not finish it.

• dateLastModifiedInSourceSystem: The date and time the event was last updated. For example, this will update when a candidate completes a previously incomplete screener and the status changes from Incomplete to Complete.

For reporting, use dateAddedInSourceSystem or dateLastModifiedInSourceSystem depending on your use case. Avoid using dateAdded, as this reflects when data reached EDS rather than when the event occurred.

Why are dateAddedInSourceSystem and dateLastModifiedInSourceSystem sometimes the same?

They match when you’re viewing an event that has not been updated since it was created.

If the event changes later, dateLastModifiedInSourceSystem will update while dateAddedInSourceSystem remains the same.

What timezone are events sent to EDS in?

All Amplify systems (i.e. Screening, Outreach, etc) send events to EDS in UTC.