Employee Data API: `jobProfileId` now available (Job Catalog 2.0)

Employee Data API now supports the new Job Catalog 2.0 ↗.

What's new?

The Employee Data API now reflects the structure of the new Job Catalog 2.0, where employees are linked to job profiles instead of job levels.

When retrieving an employee's job via the API:

• employee.jobProfileId:
  • New field that returns the identifier of the job profile assigned to the employee.
  • Available only for customers using Job Catalog 2.0 ↗.
  • Use it to fetch full job details via the Job Catalog API.
• employee.jobLevelId:
  • Previously returned the job from the old job catalog.
  • For customers on Job Catalog 2.0, this now actually returns the new job profile ID.
  • ⚠️ This field will be deprecated in the future. Update your integrations to use jobProfile.

To learn more, see Employee data access.

Who does this affect?

This change applies to any customer using the Job Catalog 2.0 in case:

• You did not use the old Job Catalog before February 9, 2025, or
• You've upgraded from the old catalog to version 2.0.

To learn more, see Getting started with the new job catalog ↗.

Upgrade notes

If you've upgraded to the Job Catalog 2.0 ↗:

• The employee.jobLevelId now returns the job profile id.
• The full job profile data includes level, title, and additional metadata.
• The human-readable value remains familiar: e.g., "Lead (3) Account Executive (J-6329338628)"
• The employee.jobLevelId field continues to work for now, but should be replaced with jobProfileId in your code.

🚧

Deprecation note:

The employee.jobLevelId field will be deprecated in the future. We recommend switching to jobProfileId in your integrations as soon as possible.