Workforce planning API: `jobProfile` now available (Job Catalog 2.0)

Workforce Planning API now supports the new Job Catalog 2.0.

What's new?

The Workforce Planning API now reflects the structure of the new Job Catalog 2.0, where positions are linked to job profiles instead of job levels.

When retrieving a position's job via the API:

• /position/jobProfile:
  • New field that returns the job profile assigned to the position.
  • Available only for customers using Job Catalog 2.0.
  • Use it to fetch full job details via the Job Catalog API.
• /position/job:
  • Previously returned a job level.
  • For customers on Job Catalog 2.0, this now returns the job profile for backward compatibility.
  • ⚠️ This field will be deprecated in the future. Update your integrations to use jobProfile.

To learn more, see Read company positions.

Who does this affect?

This change applies to any customer using Job Catalog 2.0:

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

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

Migration notes

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

• The job level previously stored in /position/job now returns the job profile.
• The job profile includes level, title, and additional metadata.
• The human-readable label remains familiar: e.g., "Lead (3) Account Executive (J-6329338628)"
• The /position/job field continues to work for now, but should be replaced with jobProfile in your code.

🚧

Deprecation note:

The /position/job field will be deprecated in the future. We recommend switching to jobProfile in your integrations as soon as possible.