Contact your Gem account team or email support@gem.com to have API access enabled on your account; API keys cannot be created until access is provisioned by Gem.
Once enabled, a Gem admin navigates to Team Settings > Integrations > API Keys and clicks + Create API Key to generate and name a key for the integration.
Use the key as a Bearer token in the Authorization header for all requests to the CRM API at https://api.gem.com/v0/ (reference docs at api.gem.com/v0/reference).
Query candidate records using the documented GET endpoints; the ATS API is separately available at api.gem.com/ats/v0/ and the Job Board API at api.gem.com/job_board/v0/.
Handle paginated responses per the current rate-limit and pagination conventions documented in the Gem API reference, using cursor or page parameters as specified.
Known gotchas
API access is not self-serve; it must be enabled by the Gem account team before any keys can be provisioned — attempting to create keys without activation returns an error.
Three separate API surfaces exist (CRM, ATS, Job Board) with separate base paths and potentially separate keys; confirm with Gem support which APIs your use case requires.
API keys are scoped to the team account, not individual users; rotating or revoking a key in Team Settings immediately invalidates all integrations using it.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp