Company hiring data API
company_hiring
2.5 credits / company returnedOne company's active hiring breakdown from the hiring index (regularly-refreshed LinkedIn + Indeed job postings): open-role counts per role/function and country, plus totals — AND a title-level breakdown of the actual posting titles, so a specific/niche role is visible even when it rolls up into a broad function bucket above. Address the company by org_id (from resolve_company) or domain. Empty roles/titles means no recent postings on record.
Parameters
| param | type | description |
|---|---|---|
| domain | string | Company website domain, e.g. "stripe.com". |
| org_id | string | LinkedIn organization id (from resolve_company). Preferred. |
Call it from your agent (MCP)
Connect once and company_hiring appears in your agent’s toolbox next to every other gtm.dev tool. Claude Code:
claude mcp add --transport http gtm https://mcp.gtm.dev \
--header "Authorization: Bearer YOUR_API_KEY"Under the hood, the client sends:
curl -X POST https://mcp.gtm.dev \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"company_hiring","arguments":{"domain":"hubspot.com"}}}'other clients (cursor, claude desktop, openai agents sdk, langchain): mcp setup
Call it over REST
curl -X POST https://api.gtm.dev/v1/tools/company_hiring \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"domain":"hubspot.com"}'Errors (401, 402, 429, 400) are listed in the REST reference. Calls that error are not billed — see pricing.