A disposition feed provides real-time updates on the status of applications.
It allows external providers to retrieve application status changes for applications that they have submitted via a Disposition feed, with the data filtered to display only those applicants submitted by that particular provider.
Why use a disposition feed?
Sharing disposition data with job boards and providers of applications can:
Improve candidate experience
- Third parties can now provide candidates with updates on their application progress via their own platforms, leading to a better candidate journey and reducing uncertainty.
Better reporting and analytics for job boards
- Job boards can gather more accurate and comprehensive data on application outcomes, ultimately leading to improved sourcing strategies for clients.
ATS Control setup
NOTE: Not all Jobtrain Staff will have access to Disposition Feeds in ATS Control – if you do not have access – please use the ‘Disposition Feed Ticket Template’ to raise a request for a new Disposition Feed to be created.
- In ATS Control, select Client > Disposition feed
- Select Add New
- Name your feed & select a format for the feed output (either JSON or XML)
- In the Source field, add the Application Tracking Source for which the feed will include application status updates.
- If the provider is retrieving the details of which job vacancies to post from a Jobtrain feed, ensure that the source matches the tracking identifier used in the Apply URL.
- Check the “&Source=” parameter to confirm the correct value.
In the Operator dropdown, select whether the Source Tracking label is:
- Exact (=) or
- Like (%)
- For Exact (=), applications will only appear if the Source Tracking tag used is in the same format and casing.
- Click Save at the bottom right.
- Copy the Identifier value e.g. "4ec3dd16-d029-43d4-bb89-cbfb8652d56e"
- The feed can be accessed using the following URL format:-
<<clientname>>/feed/data/disposition?identifier=<<identifier>>
- Client Name = candidate URL for that client e.g. https://beta.jobtrain.co.uk
- Identifier = the GUID Identifier created automatically in ATS Control when the Disposition feed is created.
Example:
https://beta.jobtrain.co.uk/feed/data/disposition?identifier=9d5b1efc-0384-4f45-86b3-d868880406f7
- The disposition feed is designed to display only application status changes from the previous day for candidates where the Source Tracking matches the ATS Control configuration.
- Only applications submitted using that Source Tracking tag & where a status change occurred on the previous day will be displayed.
- The feed should look something like this:-
Fields included in the disposition feed
|
Field Name (Feed) |
Field Description |
|
application_timestamp |
Date/time the candidate submitted their application (in UTC format). |
|
status |
The current application status. |
|
status_update_timestamp |
Date/time the candidate's status was updated to the current application status. |
| application_id | Unique identifier for the specific application. |
| job_id | Unique identifier for the job. |
Note: If an applicant experiences multiple status changes within the same day, all of these changes will be included in the feed for that application. The Application ID will remain the same, indicating it is the same candidate, but the Status and Status Update Timestamp will vary to reflect each change.
FAQs
What is the purpose of a disposition feed?
A disposition feed automates the process of updating external systems with application status changes from your ATS. This allows external partners or systems to have the latest data on candidates' application status without manual intervention.
How often is the disposition feed updated?
The disposition feed is updated at midnight and shows application status changes from the previous calendar date. It ensures that external systems always have the most recent application status data.
Can I include multiple application tracking sources in a single feed?
Yes, you can configure a disposition feed to include multiple application tracking sources. However, each source needs to be clearly defined during the feed setup process to ensure accuracy.
What happens if no status change occurs for an application?
If there is no change in an application’s status for the specified time period (e.g., the previous day), that application will not appear in the disposition feed. Only applications with status updates are included.
What about incomplete applications?
Disposition feeds only include applications that have been fully submitted. Any applications that remain incomplete, regardless of being linked to the application source, will not appear in the feed. This ensures that only actionable and finalised application data is shared with 3rd party providers.
Why is the same candidate ID included twice in the feed?
The same candidate ID may appear more than once if the applicant has undergone multiple status changes within the same day. Each entry reflects a distinct status update, where the application ID stays the same, but the status and status update timestamp will differ. Alternatively, the candidate may have applied to multiple jobs, in which case you can check the Job ID for different applications.
Can I change the output format of the feed after creation?
Yes, in ATS Control you can toggle the output format between JSON and XML as required.
How do I ensure that the data feed matches the exact application source?
During setup, you can use the Exact (=) operator in the Source field to ensure that only applications from the exact source (matching the source tracking label and format) are included. If needed, the Like (%) operator can allow for more flexible matching.
How do I troubleshoot if the feed doesn’t seem to be working?
- Ensure the Identifier in the URL is correct.
- Verify that the Source Tracking label matches the one used in the Apply URL.
- Check that there are status changes for applications from the previous day.
Can providers request changes to the disposition feed contents?
No – the disposition feed is standardised across all clients and cannot be customised for individual providers.
If there are common themes in change requests from clients or providers, then please raise as a Continuous Improvement Request with Product.