Skip to main content

​
January 30th, 2026

  • The following endpoints are no longer in BETA:
MethodURLSummary
GET/v2/notesGet all Notes
GET/v2/notes/{noteId}Get a Note with a given id
GET/v2/notes/{noteId}/attached-companiesGet directly attached companies for a Note
GET/v2/notes/{noteId}/attached-opportunitiesGet directly attached opportunities for a Note
GET/v2/notes/{noteId}/attached-personsGet directly attached persons for a Note
GET/v2/notes/{noteId}/repliesGet reply notes for a given Note

​
January 26th, 2026

  • Added the following endpoints in BETA:
MethodURLSummary
GET/v2/transcriptsGet All Transcripts
GET/v2/transcripts/{transcriptId}Get Transcript
GET/v2/transcripts/{transcriptId}/fragmentsGet Fragments on a single Transcript

​
January 14th, 2026

  • Rate limit response headers have been updated to use lowercase formatting. This change affects all API endpoints. The new lowercase headers are:
HeaderDescription
x-ratelimit-limit-userNumber of requests allowed per minute for the user
x-ratelimit-limit-user-remainingNumber of requests remaining for the user
x-ratelimit-limit-user-resetTime in seconds before the limit resets for the user
x-ratelimit-limit-orgNumber of requests allowed per month for the account
x-ratelimit-limit-org-remainingNumber of requests remaining for the account
x-ratelimit-limit-org-resetTime in seconds before the limit resets for the account

​
January 1st, 2026

  • Handling timestamps for date fields. Affinity is standardizing how dates are represented across the platform to ensure consistency between the application and the API. Starting January 1st, 2026, the API will change how it handles timestamps for date fields. Today, timestamps sent to date fields over the API are not visible to users in any CRM interface. After this change, the API will ignore any time information included in requests, storing and returning values at midnight Pacific Time (PT) on the submitted date.
Example:
  • API request includes: 2024-04-01T15:30:00Z
  • Affinity will store and return: 2024-04-01T07:00:00.000Z (equivalent to midnight PT)
Any existing date field values that currently include timestamps will also be updated to reflect midnight PT on their stored date. No action is required unless your integration depends on time data within date fields.

​
September 25th, 2025

  • Added the following endpoints in BETA:
MethodURLSummary
GET/v2/company-mergesGet All Company Merge status
POST/v2/company-mergesInitiate Company Merge
GET/v2/company-merges/{mergeId}Get Company Merge status
GET/v2/tasks/company-mergesGet All Company Merge Tasks
GET/v2/tasks/company-merges/{taskId}Get Company Merge Task

​
July 30th, 2025

  • Added the following endpoints in BETA:
MethodURLSummary
GET/v2/person-mergesGet All Person Merge status
POST/v2/person-mergesInitiate Person Merge
GET/v2/person-merges/{mergeId}Get Person Merge status
GET/v2/tasks/person-mergesGet All Person Merge Tasks
GET/v2/tasks/person-merges/{taskId}Get Person Merge Task
GET/v2/notesGet all Notes
GET/v2/notes/{noteId}Get a Note with a given id
GET/v2/notes/{noteId}/attached-companiesGet directly attached companies for a Note
GET/v2/notes/{noteId}/attached-opportunitiesGet directly attached opportunities for a Note
GET/v2/notes/{noteId}/attached-personsGet directly attached persons for a Note
GET/v2/notes/{noteId}/repliesGet reply notes for a given Note

​
May 14th, 2025

  • Renamed all path parameters named simply “id” to a more descriptive name (eg. “personId”). This will not have any effect on the API at runtime, but may impact code relying on the OpenAPI spec doing type generation.

​
April 9th, 2025

  • The following endpoints are no longer in BETA:
MethodURLSummary
GET/v2/lists/{listId}/list-entries/{listEntryId}Get a single List Entry on a List
GET/v2/lists/{listId}/list-entries/{listEntryId}/fieldsGet field values on a single List Entry
PATCH/v2/lists/{listId}/list-entries/{listEntryId}/fieldsPerform batch operations on a list entry’s fields
GET/v2/lists/{listId}/list-entries/{listEntryId}/fields/{fieldId}Get a single field value
POST/v2/lists/{listId}/list-entries/{listEntryId}/fields/{fieldId}Update a single field value on a List Entry

​
March 31st, 2025

  • The following beta endpoints now support updating association fields.
MethodURLSummary
PATCH/v2/lists/{listId}/list-entries/{listEntryId}/fieldsPerform batch operations on a list entry’s fields
POST/v2/lists/{listId}/list-entries/{listEntryId}/fields/{fieldId}Update a single field value on a List Entry

​
February 28th, 2025

  • Added the following endpoints in BETA:
MethodURLSummary
GET/v2/lists/{listId}/list-entries/{listEntryId}Get a single List Entry on a List
GET/v2/lists/{listId}/list-entries/{listEntryId}/fieldsGet field values on a single List Entry
PATCH/v2/lists/{listId}/list-entries/{listEntryId}/fieldsPerform batch operations on a list entry’s fields
GET/v2/lists/{listId}/list-entries/{listEntryId}/fields/{fieldId}Get a single field value
POST/v2/lists/{listId}/list-entries/{listEntryId}/fields/{fieldId}Update a single field value on a List Entry

​
January 17th, 2025

  • Document X-Ratelimit headers in the schema for all endpoints.

​
January 15th, 2025

  • Add default responses to all endpoints to document all possible error codes that can be returned by the API.
  • Updated 400 error responses to correctly include the bad-request error code as a possible error.

​
December 3rd, 2024

  • Properly document listId property on CompanyListEntry, PersonListEntry, and OpportunityListEntry schemas.

​
September 25th, 2024

  • Upgrade schema to OpenAPI 3.1

​
August 5, 2024

  • Correct opp to opportunity to match documentation for the List type property.

​
July 24, 2024

  • More accurate documentation for response properties that are enums — Enums with null as a possible value will have it listed as one.

​
March 25, 2024

  • Added the ability to retrieve the date and other details of your firm’s “First Email”, “Last Email”, “First Event”, “Last Event”, “Next Event”, “First Chat Message”, “Last Chat Message”, and “Last Contact” with a given entity. Use these timestamps to add relationship context to your applications, and to identify founders and companies that need investors’ attention.
  • Endpoints that previously required a fieldIds parameter to return field data, now accept either fieldIds or fieldTypes, and will return field data accordingly. See the Specifying Desired Fields (Field Selection) section of these docs for more information. The new fieldTypes parameter should make field data retrieval easier for users looking to pull data from many similar Fields at a time.

​
January 4, 2023

  • Most endpoints that return field data now require the user to use the fieldIds parameter to specify which Fields they want data for. Without fieldIds specified, these endpoints will return basic entity data but not field data.

​
December 12, 2023

  • Added the ability to retrieve metadata (e.g. ID, name, type, enrichment source, and data type) on Fields. See the Retrieving Field Metadata section of these docs for more information.