canonical: https://jentic.com/apis/getro.com/getro

# Getro Job Board and Network API

Getro powers talent networks and job boards for venture capital firms, accelerators, and ecosystem operators that want to surface jobs from their portfolio companies in one place. The v2 API exposes 15 endpoints covering networks, member companies, job listings including removed-job audit, contact records with notes, and reference data for job functions, locations, and industry tags. It is the integration surface for embedding portfolio job feeds in member sites, exporting talent data for back-office reporting, and syncing contacts into a CRM.

## For AI agents

Search jobs and companies inside a Getro talent network, retrieve contacts with notes, and import contact records for VC and accelerator portfolio platforms.

## Scope

Does not handle interview scheduling, candidate sourcing inboxes, or in-app messaging - use for talent-network jobs, companies, and contacts only.

## Capabilities

- Search jobs across a network filtered by job function, location, or company
- Retrieve a network's member companies with their metadata and industry tags
- List contacts in a network and attach notes to a contact's profile
- Import a batch of contacts via POST `/contacts/import`
- Pull removed jobs to audit listings that have been taken down
- Look up reference data such as job functions, locations, and industry tags for filter UIs

## Use cases

### VC portfolio job board

Venture firms aggregate every open role across portfolio companies into a single talent destination for their network. The API returns jobs filtered by function, location, and tag, so the firm's website renders a fresh, searchable feed without each company posting manually.

Example prompt: Fetch all jobs in network 42 with job_function 'engineering' and location 'San Francisco' and render them as a paginated list

### Talent CRM sync

Operations teams keep their CRM in sync with the talent network's contact database, copying company affiliations and any notes captured during intros. The contacts endpoints support pagination and the import endpoint accepts batches, so the daily sync stays bounded even on large networks.

Example prompt: List contacts in network 42 modified in the last 24 hours and upsert each into the team's HubSpot CRM

### Removed-listing compliance audit

Operators run periodic audits of jobs that have been removed to understand churn and ensure no archived role is still surfacing publicly. The `/networks/{id}/jobs/removed` endpoint returns the audit trail so a compliance report can be generated without manual scraping.

Example prompt: List removed jobs in network 42 between two dates and write a CSV with company, role, and removed_at

### AI agent for portfolio talent matching

An AI agent connected through Jentic accepts a candidate's profile, queries Getro for jobs matching their function and location preferences, and returns a ranked shortlist. Jentic injects the bearer token so the agent never directly handles the network credential.

Example prompt: Given candidate skills 'python, ml' and location 'remote', search jobs in network 42 and return the top 10 ranked matches

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/networks` | List talent networks |
| GET | `/networks/{id}/companies` | List companies in a network |
| GET | `/networks/{id}/jobs` | Search jobs in a network |
| GET | `/networks/{id}/jobs/removed` | Audit removed job listings |
| GET | `/networks/{id}/contacts` | Search contacts |
| POST | `/contacts/import` | Import contacts in batch |
| POST | `/networks/{network_id}/contacts/notes` | Create a contact note |

## Key resources

- **Networks** — Talent network containers and their metadata
- **Companies** — Member companies in a network with industry tags and locations
- **Jobs** — Open and removed job listings searchable by function and location
- **Contacts** — People in the network with notes and import support
- **Reference data** — Job functions, industry tags, and location lists for filter UIs

## Why Jentic

- **Setup:** Wiring Getro by hand means setting its bearer auth, threading the network id through the jobs, companies, and contacts paths, and paging over talent-network data yourself. Through Jentic you install once, import the Getro Job Board and Network API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Getro puts the network id in the URL path (`/networks/{id}/jobs`), so a rule can pin your agent to one network: it reads jobs, companies, and contacts there and touches no other network. You choose the operations it may call, so importing contacts or adding a note is not included unless you add it.
- **Credential handling:** Your Getro token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search portfolio jobs in a network' or 'list network companies', and Jentic returns the matching Getro operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse API** — Full-featured ATS for in-house hiring rather than a portfolio-wide job board
- **Lever API** — Modern ATS with strong CRM-style sourcing features
- **Ashby API** — ATS for individual portfolio companies whose jobs may flow up into a Getro network

## FAQ

### What authentication does the Getro API use?

Getro uses bearer-token authentication: send the token issued by your Getro account in the Authorization header. Through Jentic the token is vaulted and injected per request, so the raw bearer never enters agent context.

### Can I search jobs across a network through the API?

Yes. GET `/networks/{id}/jobs` accepts filter parameters for function, location, and company so you can build a faceted job feed. The companion `/networks/{id}/jobs/removed` endpoint returns jobs that have been taken down for audit purposes.

### What are the rate limits for the Getro API?

The OpenAPI spec does not declare explicit rate limits. Practical guidance is to paginate large lists, cache reference data such as job functions and industry tags, and back off on any 429 response rather than retrying immediately.

### How do I import a batch of contacts through Jentic?

Search Jentic for 'import getro contacts', load the POST `/contacts/import` schema, then execute with your contact array. Jentic handles the bearer-token injection and surfaces any per-row import errors in the response.

### Can I attach a note to a contact?

Yes. POST `/networks/{network_id}/contacts/notes` creates a note tied to a contact, useful for logging intros, follow-ups, or feedback after a portfolio meeting.

### Is the Getro API free?

API access is included with paid Getro plans and is not metered separately. Higher-volume integrations and more network-level features unlock at higher tiers - check getro.com for current plan details.

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

Yes. Jentic One runs self-hosted, so your own rules decide which Getro operations and credentials the agent may use. Because Getro carries the network id in the path (GET `/networks/{id}/jobs`), you can pin the agent to a single network and let it read only jobs, companies, and contacts there. Write operations such as POST `/contacts/import` and POST `/networks/{network_id}/contacts/notes` stay off unless you explicitly grant them.