> ## Documentation Index > Fetch the complete documentation index at: https://api.leadey.ai/llms.txt > Use this file to discover all available pages before exploring further. # List a lead's contacts > Everyone at this lead's company, across your whole workspace — the same list the Cockpit shows under **Contacts** on a lead profile. This is not the same as `/contacts`. That endpoint lists your canonical people directory; this one answers "who else works here", and returns lead records you can call, email and enrol in a Campaign. Colleagues are matched on the company behind the lead, so someone enrolled in a different Campaign — or in none at all — still appears. The lead you asked about is included, marked `isPrimary`. ## OpenAPI ````yaml /openapi.json get /leads/{id}/contacts openapi: 3.1.0 info: title: Leadey API version: 1.4.0 description: >- The Leadey API gives you programmatic access to your workspace: leads, companies, contacts, campaigns, meetings, opportunities and calls, plus the reporting metrics behind the Cockpit. Every request is authenticated with an organization-scoped API key, and every response is JSON. Reads work with any key. Writes — creating leads, adding notes, logging calls, managing tasks — need a key with write access, and are attributed to the workspace member that key belongs to. See [Writing data](/guides/writing-data). servers: - url: https://backend.leadey.ai/v1 description: Production - url: http://localhost:3001/v1 description: Local development security: - bearerAuth: [] tags: - name: Account description: The organization behind the API key. - name: Leads description: People enrolled in your campaigns. - name: Notes description: >- Free-text notes on a lead. Notes appear in the lead's timeline and in the Cockpit. - name: Tasks description: Follow-ups and reminders, each assigned to a workspace member. - name: Campaigns description: Outreach sequences and their performance. - name: Companies description: Companies in your workspace. - name: Contacts description: The canonical person record behind your leads. - name: Meetings description: Bookings merged across Calendly, Leadey and connected calendars. - name: Opportunities description: Deals, their value, and the pipelines they sit in. - name: Pipelines description: Deal pipelines and the stages inside them. - name: Calls description: Dial history, recordings and transcripts. - name: Metrics description: >- Aggregated reporting — meetings booked, sit rate, dial activity and pipeline value. - name: Reference description: The vocabularies other endpoints return values from. paths: /leads/{id}/contacts: get: tags: - Leads summary: List a lead's contacts description: >- Everyone at this lead's company, across your whole workspace — the same list the Cockpit shows under **Contacts** on a lead profile. This is not the same as `/contacts`. That endpoint lists your canonical people directory; this one answers "who else works here", and returns lead records you can call, email and enrol in a Campaign. Colleagues are matched on the company behind the lead, so someone enrolled in a different Campaign — or in none at all — still appears. The lead you asked about is included, marked `isPrimary`. operationId: getLeadContacts parameters: - $ref: '#/components/parameters/LeadId' - $ref: '#/components/parameters/Page' - $ref: '#/components/parameters/PageSize' responses: '200': description: A page of the lead's colleagues. content: application/json: schema: type: object properties: data: type: array items: $ref: '#/components/schemas/CompanyContact' meta: $ref: '#/components/schemas/PageMeta' example: data: - id: lead_7Kd2mPqR name: Priya Raman title: Head of Revenue Operations email: priya.raman@northwind.co.uk phone: '+442071838750' linkedinUrl: https://www.linkedin.com/in/priyaraman company: Northwind Logistics companyDomain: northwind.co.uk campaignId: cmp_4Xy9tBnW campaignName: UK Logistics — Q3 masterContactId: ct_1Bn5zTqE isPrimary: true doNotCall: false status: interested createdAt: '2026-07-14T09:12:44.000Z' - id: lead_9Fz4kLmT name: Daniel Okafor title: Operations Director email: daniel.okafor@northwind.co.uk phone: null linkedinUrl: https://www.linkedin.com/in/danielokafor company: Northwind Logistics companyDomain: northwind.co.uk campaignId: null campaignName: null masterContactId: null isPrimary: false doNotCall: false status: new createdAt: '2026-08-02T15:38:10.000Z' meta: page: 1 pageSize: 50 totalCount: 2 totalPages: 1 '404': description: No lead with that id in your workspace. components: parameters: LeadId: name: id in: path required: true description: The lead id. schema: type: string Page: name: page in: query description: 1-based page number. schema: type: integer minimum: 1 default: 1 PageSize: name: pageSize in: query description: Items per page (max 100). schema: type: integer minimum: 1 maximum: 100 default: 25 schemas: CompanyContact: type: object description: >- A person at the lead's company. These are lead records, so each one can be called, emailed and worked exactly like the lead you asked about. properties: id: type: string description: Use as `{id}` on any `/leads` endpoint. name: type: string title: type: - string - 'null' email: type: - string - 'null' phone: type: - string - 'null' linkedinUrl: type: - string - 'null' company: type: - string - 'null' companyDomain: type: - string - 'null' campaignId: type: - string - 'null' description: The Campaign this person is enrolled in, if any. campaignName: type: - string - 'null' masterContactId: type: - string - 'null' description: >- The canonical contact record, where one exists — fetch it from `/contacts/{id}`. isPrimary: type: boolean description: True for the lead you asked about. doNotCall: type: boolean status: type: string createdAt: type: string format: date-time PageMeta: type: object properties: page: type: integer example: 1 pageSize: type: integer example: 25 totalCount: type: integer example: 134 totalPages: type: integer example: 6 required: - page - pageSize - totalCount - totalPages securitySchemes: bearerAuth: type: http scheme: bearer description: >- Your API key, created in the Leadey dashboard under Settings → API Keys. Send it as `Authorization: Bearer leadey_sk_live_…`. ````