Enhanced job ID
Updated at October 15th, 2026
Table of Contents
Paradox's enhanced job IDs give Conversational ATS customers a shorter, versioned format that is easier to use across My Jobs, career sites, job boards, and agencies. Each job posting can have its own distinct ID, and the version segment updates when a job is reposted so your hiring teams can track changes without losing the core job reference.
Logic from after October's release (2.6.7) and migration timelines are covered in the Frequently asked questions (FAQ) section and in the October 2026, 2.6.7 Release Notes (under Updates to Enhanced Job ID).
Use cases
- Job identification: Distinguish each job posting in My Jobs with its own shortened enhanced job ID
- Job boards, career sites, and agencies: Reference a stable, readable Job ID for distribution and mapping.
- Reporting and integrations: Safely activate the Unique and Versioned Job IDs toggle for new job postings while preserving the historical integrity of existing records.
Configuration
This feature is enabled by default in new accounts. If it is disabled in the account, it must first be enabled in Client Setup. Users with full access to Client Setup can complete the below steps to turn on this feature.
- Select the All Apps menu in the upper-left corner of the header and then Settings in its drop-down menu.
- When the Settings page opens, select Client Setup under the Paradox Tools section.
- Client Setup will then open. Scroll down to and open the Job Management section from the left panel.
- Enable the Unique and Versioned Job ID toggle.
- Ensure to save.
Enabling this toggle does not immediately change all job and candidate IDs on your account. Existing jobs will update to the enhanced job ID format the next time they are reposted in My Jobs, and candidates will retain the Job ID from when they originally applied.
Once enabled, do not turn off the Unique and Version Job ID toggle. Disabling this setting can cause unexpected data behavior. If you need assistance with this feature, please reach out to your CS Manager.
Enhanced job IDs
Paradox introduced enhanced job IDs because the previous legacy job ID lacked unique job identifiers. For multi-location jobs, we had to append the location ID to the end of the job ID, which created challenges when evaluating candidates and their data.
Our customers requested a solution where each job posting in My Jobs has its own unique job ID, making it easier to reference and track jobs independently. Every job posting now has its own distinct job ID, improving clarity and data management.
The legacy job ID (the previous job ID format) is a long Paradox-generated string (PDX_XXX_XXXXXXXX-XXXX-XXXX-XXXX), often with a location suffix.
Example: In the Job Builder, the Crew Team Member job is created and assigned 5 locations. In My Jobs, each postings displays today as:
-
Location 1:
PDX_JTC_B2C3BA90-3A15-441D-AFD9-96D17E0CFEC2_001 -
Location 2:
PDX_JTC_B2C3BA90-3A15-441D-AFD9-96D17E0CFEC2_002 -
Location 3:
PDX_JTC_B2C3BA90-3A15-441D-AFD9-96D17E0CFEC2_003 -
Location 4:
PDX_JTC_B2C3BA90-3A15-441D-AFD9-96D17E0CFEC2_004 -
Location 5:
PDX_JTC_B2C3BA90-3A15-441D-AFD9-96D17E0CFEC2_005
The enhanced job ID is a shorter Paradox-generated string (PX-XXXXX-X) that includes a core segment that identifies the posting and a version segment that can update when the job is reposted.
Example: In the Job Builder, the Crew Team Member job is created and assigned 5 locations. In My Jobs, each posting will now display as:
-
Location 1:
P1-10862-1 -
Location 2:
P1-38484-1 -
Location 3:
P1-58673-1 -
Location 4:
P1-45775-1 -
Location 5:
P1-55757-1
Benefits of enhanced job IDs
-
Unique & Shortened IDs:
The new job ID format is easier for clients to reference internally within My Jobs and can also be used externally on career sites and job boards. -
Consistent Core ID:
The core part of the Job ID remains the same, providing consistency, while the versioned part of the ID allows flexibility. -
Version Logic:
The Version ID is appended to the core Job ID and updates each time the job is toggled open or closed. This ensures that updates (such as status changes) are tracked without creating a completely new job ID, simplifying job management and reporting.
Job attributes
You can use the following job attributes with the enhanced job ID format:
-
Paradox Job ID (
job_req_id): The Paradox job ID (PDX or PX) for all job types. -
Job ID (
requisition_id): The Paradox job ID for Conversational ATS jobs and the Feed ID for Integrated jobs.
Customer considerations
To prepare for this change, work with your Paradox CS Manager to:
- Identify where Job IDs are used today: Review your internal processes, reports, feeds, and integrations that reference Job IDs to understand where the ID is currently used and how the transition may affect the experience.
- Coordinate with your partners: Share this change with your external partners (agencies, career site provider, job boards like Indeed, etc.) so they can plan and implement any updates needed on their side. For example, agencies may need to make mapping updates to ensure jobs do not fall off from their connection.
- Align on your transition timeline: Work with your Paradox team to confirm a transition date that best fits your organization and partners, ahead of the automatic opt-in date.
Enhanced job IDs in platform
Once the configuration is complete, the following updates will be reflected across the platform, including (but not limited to):
-
CEM platform
- Candidate profile
- My Jobs
- Job Manager
-
Candidate experience
- Job Posting pages
- Apply URLs
-
Reporting & Analytics
- Standard or custom reports
- Dashboards
- Any filters or fields referencing Job ID
-
Job Feeds
- Custom feeds
- Master feed
- Paradox standard feeds
-
Integrations
- Agency partners
- Job boards
- Career sites
- Any third-party systems that rely on Job ID
Customer one-pager
Frequently asked questions (FAQs)
If we turn on the Unique and Version Job ID toggle, will our existing legacy Job IDs change?
No. Starting with the October 2026 release (2.6.7), Paradox updated how this setting works so you can adopt Enhanced Job IDs without a blanket ID change across your account.
When you turn on Unique and Version Job ID in Client Setup, your open jobs and your current applicants keep the Job IDs they use today. A job keeps its legacy ID until your team posts that job in My Jobs after enablement. Anyone who already applied keeps the Job ID from their application in the CEM, reporting, and analytics.
In the past, turning this setting on could retroactively update Job and Candidate IDs. That made it hard to align job boards, career sites, and internal reports before go-live. The October update is designed so you can enable Enhanced Job IDs on your timeline and move jobs forward as you post them, without rewriting historical applicant data.
If your account already had Unique and Version Job ID on before 2.6.7, Paradox also restores applicant Job IDs for candidates who applied before you first enabled the setting. Your job records are not rolled back to legacy format. Read October 2026, 2.6.7 Release Notes (Transition to Paradox Enhanced Job IDs) for rollout details and work with your CS Representative before you enable the toggle on a live account.
Are all new clients required to use the new job ID structure?
Yes, all new clients should automatically use the new, unique, and versioned job ID format. This will allow for a more seamless transition and experience for your clients.
Are all new clients required to use the new job ID structure?
Yes, all new clients should automatically use the new, unique, and versioned job ID format. This will allow for a more seamless transition and experience for your clients.
Can existing clients migrate to the new job ID format?
Yes, but you must confirm that the client does not have any third-party or internal dependencies on the old job ID structure before making the switch.
As noted above, when migrating existing clients, it is essential to evaluate any dependencies that may rely on the old Job ID (PDX value). This includes third-party systems such as job boards, career sites, or advertising platforms. If these dependencies are not properly accounted for, the client’s job mapping may break, disrupting ongoing job campaigns and processes.
Where will the job ID be updated in the system?
The new job ID will be reflected in the Candidate Profile, My Jobs, Apply URLs, Job Feeds, Reporting, Analytics, and any other areas that reference job IDs.
What should I do if a client has dependencies on the old job ID structure?
If there are dependencies, you must create a migration plan and work with the client to adjust any affected systems or workflows before enabling the new job ID structure. If you have any questions, please reach out to Solutions or Product for assistance.
How does the versioned job ID work?
The versioned job ID allows changes to job postings when the job is toggled on/off without generating a completely new job ID. This helps clients track changes while maintaining consistency in job references.
How can we verify that no job postings will break on external sites like Indeed or LinkedIn?
Before making any changes, ensure that external job boards are not reliant on the old Job ID structure by consulting with the client. It may also be good for the client to review the Job ID change with their contact at the job board. If ad campaigns or job feeds depend on the old structure, those systems will need updates to accommodate the new Job ID.
The update will likely also result in a new job posting. Please inform your clients this change will need to be made in accordance to the job boards reposting policies.
Will there be any impact on analytics or reporting?
Yes, the new Job ID will be reflected in all analytics and reporting tools, providing a more streamlined and consistent structure across data points.
What happens if the new job ID isn’t compatible with a client’s current system?
If incompatibility is detected, work closely with the client to update their system or create a workaround. In some cases, clients may opt to stay on the legacy ID format if necessary, but migration should be encouraged when possible.
Can a client revert to the old Job ID structure after migration?
No, once the migration to the new Job ID structure is complete, reverting to the old format should not be allowed. Please ensure the client is fully prepared before initiating the change.
Will the new job ID affect existing candidates?
No, existing candidate applications tied to jobs with the old Job ID will remain associated to the job and legacy job id. The new structure applies moving forward for future jobs and postings.
Will Filters and Segments that are currently configured using the Req ID migrate with the new Job ID structure?
Segments built today may be supported, but they will not sync new candidates associated to the new job ID appropriately. It is recommended that segments are re-configured because the Job ID structure that existed previously was the same for multiple postings.