Trio Job Sync Integration Guide

Introduction

This guide outlines the process for agencies to integrate with Trio VMS to maintain a synchronized list of availabe jobs. The integration uses both the Trio API for initial data retrieval and periodic syncs as well as Trio webhooks for real-time updates.

Authentication

Before accessing the Trio API, you need to set up authentication and obtain an API Key to use in the X-API-KEY header in each request.

Integration

Retrieve Initial Job List

To get the initial list of jobs, use the /api/v3/Job endpoint:

This endpoint returns a list of all open jobs available to your agency.

You can use the modifiedDate query parameter to limit the response to jobs that were modfied after a specific date. A simple date will be accepted and the time will default to midnight UTC.

IMPORTANT
Updates to the NumberOfCurrentOpenPositions does not trigger an update to a Job's ModifiedDateUtc or a Job Update webhook event. If this is a critical piece of data to keep updated in your system, use the api/v3/Job endpoint without a modifiedDate parameter.

Register Job Update Webhook

To receive real-time updates about job changes, register a webhook listener and an endpoint on your server to receive webhook payloads. See Webhook Registration for detailed instructions on registering webhooks within Trio.

Implement Webhook Endpoint

Create an endpoint on your server to receive webhook payloads:

Set up a secure HTTPS endpoint (e.g., https://your-agency-domain.com/trio-webhooks/jobs)

Implement request validation to ensure the webhook is from Trio.

Process the incoming webhook payload and update your local job data accordingly.

Job Sync Implementation

To maintain a synchronized job list:

Perform an initial fully sync using the API:

Retrieve all jobs using the /Job endpoint.

Store the jobs in your database.

Record the timestamp of this sync.

Set up a periodic sync (e.g., daily) to catch any missed updates:

Use the /Job endpoint with the modifiedDate parameter set to your last sync timestamp.

Update your local database with any changed or new jobs.

Record the timestamp of this sync.

Process incoming webhooks in real-time:

Use the Job Number as the unique identifier to determine if the job is new (not in your database) or update an existing Job.

IMPORTANT
The /api/v3/Job endpoint only returns Open or OnHold jobs. Your job ingestion process will need to account for jobs no longer returned from then endpoint as Closed.
Implementing webhooks will notify when a Job becomes Closed.

Best Practices

Implement error handling and retries for API requests and webhook processing.

Use a queueing system for webhook processing to handle high volumes of updates.

Implement logging for all API interactions and webhook events for troubleshooting.

Regularly check the /webhooks endpoint to ensure your webhooks are still active and properly configured.

Implement a way to perform a full re-sync if you suspect your job data has become out of sync.

By following this guide, you should be able to implement a robust job sync integration with Trio VMS, keeping your agency's job listings up-to-date using both API and webhook mechanisms.

Introduction#

Authentication#

Integration#

Retrieve Initial Job List#

Register Job Update Webhook#

Implement Webhook Endpoint#

Job Sync Implementation#

Best Practices#