> ## 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 notes on a lead > Returns the lead's notes, newest first. ## OpenAPI ````yaml /openapi.json get /leads/{id}/notes 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}/notes: get: tags: - Notes summary: List notes on a lead description: Returns the lead's notes, newest first. operationId: listLeadNotes parameters: - $ref: '#/components/parameters/LeadId' - $ref: '#/components/parameters/Page' - $ref: '#/components/parameters/PageSize' responses: '200': description: A page of notes. content: application/json: schema: type: object properties: data: type: array items: $ref: '#/components/schemas/Note' meta: $ref: '#/components/schemas/PageMeta' required: - data - meta example: data: - id: event_6Tk9wRmB type: note outcome: null stepIndex: 0 meta: text: Left a voicemail. Trying again Thursday morning. userId: user_2pXn4Rk timestamp: '2026-08-03T11:09:20.000Z' meta: page: 1 pageSize: 25 totalCount: 4 totalPages: 1 '401': $ref: '#/components/responses/Unauthorized' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/RateLimited' 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: Note: type: object properties: id: type: string description: Unique note id. type: type: string description: Always `note`. enum: - note outcome: type: - string - 'null' description: >- Always null for notes. Present so a note has the same shape as any other timeline event. stepIndex: type: integer description: Always 0 for notes. meta: description: The note body and its author. type: object properties: text: type: string description: The note body. userId: type: - string - 'null' description: >- The workspace member who wrote it. For a note created through the API this is the member the key belongs to. attachments: type: array description: >- Documents attached to the note. Attachments are uploaded in the Cockpit; the API does not accept file uploads. items: type: object properties: id: type: string description: Document id. fileName: type: string description: Original file name. mimeType: type: string description: Content type. size: type: integer description: Size in bytes. required: - id - fileName - mimeType - size required: - text timestamp: type: string description: When the note was written. format: date-time required: - id - type - meta - timestamp 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 Error: type: object properties: error: type: object properties: message: type: string description: Human-readable error message. details: type: - object - array - string - 'null' description: Optional structured detail. required: - message responses: Unauthorized: description: The API key is missing, invalid, or revoked. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: message: Invalid or revoked API key. details: null NotFound: description: The resource does not exist or is not in your workspace. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: message: Lead not found details: null RateLimited: description: Too many requests. Retry after the period in the `Retry-After` header. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: message: Rate limit exceeded. Retry in 42s. details: null 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_…`. ````