What authentication does the PayScale API use?

The PayScale API uses a two-step authentication flow. First, you submit your API key to POST /auth/token to receive an access token. Then you use that token in subsequent requests to the resource endpoints. Through Jentic, API keys are stored encrypted in your Jentic One instance and token generation is handled automatically.

How do I retrieve compensation data through Jentic?

Use Jentic to search for 'access PayScale salary data', which loads the authentication and resource retrieval flow. Jentic handles token generation via POST /auth/token automatically, then you can list resources via GET /resources or retrieve specific data via GET /resources/{id}.

What data is available through the PayScale API resources endpoint?

The GET /resources endpoint returns a catalog of available compensation data resources. Each resource has an identifier that can be used with GET /resources/{id} to retrieve the full dataset. Available resources cover salary benchmarks, compensation ranges, and market rate data.

How does the PayScale API differ from Jobalyzer?

The PayScale API provides general access to compensation data resources through a simple list-and-retrieve pattern. Jobalyzer is a specialized service that generates custom compensation reports with job title matching, skills impact analysis, and education premium calculations. Use PayScale API for bulk data access and Jobalyzer for targeted job-specific analysis.

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

Yes. Because you run Jentic One yourself, your own rules decide which PayScale operations the agent can call, and the PayScale API only exposes compensation resource lookups. You can allow the agent to list available resources via GET /resources or fetch a single dataset via GET /resources/{id} while withholding anything you have not approved. Only the operations you grant are callable, so the agent stays limited to read access over benchmarking data.