Payscale Jobalyzer

What authentication does the Jobalyzer API use?

Jobalyzer uses Bearer token authentication. Include your API token in the Authorization header as 'Bearer {token}' with each request. Through Jentic, bearer tokens are stored encrypted in your Jentic One instance and agents receive scoped access without handling raw credentials.

Can I analyze the salary impact of specific skills?

Yes. The GET /jobalyzer/v2/impact/skills endpoint returns compensation impact data for specific skills associated with a job profile. It shows the pay premium or penalty for each skill, enabling quantitative comparison of how different competencies affect market salary.

How do I generate a compensation report through Jentic?

Use Jentic to search for 'generate salary report', load the schema for POST /jobalyzer/v2/reports with job profile parameters, and execute. Then retrieve pay data via GET /jobalyzer/v2/reports/{ReportId}/pay for median salary, percentiles, and years-of-experience curves.

What is job title matching and how does it work?

The POST /jobalyzer/v2/jobtitlematch endpoint takes a free-text job title or description and returns matching standardized PayScale job titles. This normalization step ensures compensation data is compared against the correct market benchmark rather than custom internal titles.

Can I get location-adjusted salary data?

Yes. Use GET /jobalyzer/v2/locations/{SearchTerm} to find valid location identifiers, then include the location in your report parameters when calling POST /jobalyzer/v2/reports. The generated report reflects geographic pay adjustments for that market.

Can I limit what my agent is allowed to do with the Jobalyzer API?

Yes. Because you run Jentic One yourself, your own rules decide which Jobalyzer operations and credentials the agent may use, so you can grant only the endpoints a given task needs. For example, you can allow read-only calls like matching a job title with POST /jobalyzer/v2/jobtitlematch or reading skills, certification, and education pay impact via the GET /jobalyzer/v2/impact/ operations, while withholding report creation with POST /jobalyzer/v2/reports unless you add it. Since reports are identified by a generated id in the URL path, the agent can only reach the specific operations you have scoped it to call.