Use the Finch Directory endpoint to retrieve each individual's department and manager relationship and reconstruct employee reporting lines for an org-chart integration.

domain: developer.tryfinch.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Run Finch Connect for the employer requesting the 'directory' product scope specifically (distinct from the 'company', 'individual', or 'employment' scopes) so the resulting token can read directory data.
  2. Exchange the Finch Connect authorization code for an access token.
  3. Call GET https://api.tryfinch.com/employer/directory with header Authorization: Bearer <access token> and the required Finch-API-Version header (date-formatted, current version 2020-09-17).
  4. Page through the individuals array using the limit and offset query parameters; each record includes id, first_name, last_name, is_active, a department object (name), and a manager object (manager's Finch id).
  5. For multi-entity employers, pass entity_ids (exactly one UUID) to scope the request to a single legal entity.
  6. Join each individual's manager.id back to another individual's id in the same response set to reconstruct reporting lines, since Directory exposes manager relationships rather than a nested org tree.

Known gotchas

Related routes

Enroll an employee in benefits via the Finch unified /employer/benefits endpoints
finch.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans