Skip to main content

Changelog

This page lists notable additions, removals, and behavioral changes to the Accord GraphQL API.

Schema-level changes are visible in the API reference; the entries below capture changes that are easy to miss from a diff alone: deprecations, breaking changes, new auth flows, rate-limit changes, and so on.

2026-09-22: Subscriptions removed from the reference​

  • The Subscription root type (generateSectionStream, generateDealAlertsStream, listen) and its payload types no longer appear in the API reference. GraphQL subscriptions are an internal transport for the Accord webapp, not a supported integration surface, and we don't intend to keep them stable for external callers. Build on queries and mutations instead; poll where you need freshness.
  • Not a runtime change: nothing about the live endpoint changed in this release. The operations are simply undocumented and unsupported.

2026-09-17: API reference regenerated from the live schema​

The API reference had not been regenerated since 2026-05-26 and was missing several months of schema changes. It now matches the live API. Most of the difference is newly-written field and type descriptions, but a few changes are worth calling out.

Breaking

  • deleteAccord now takes DeleteAccordInput { accordId } and returns DeleteAccordPayload { accord, query }. It replaced the auto-generated mutation, which took { id } and returned the deleted row's edge and relations. Deleting an Accord also cascades a soft delete to its related records. (Shipped 2026-05-28.)
  • deleteAccordByNodeId and DeleteAccordByNodeIdInput were removed. Use deleteAccord with accordId. (Shipped 2026-05-28.)
  • LibraryResourceFilter.timesUsed was removed, so library resources can no longer be filtered on timesUsed. The LibraryResource.timesUsed field still works and TIMES_USED_ASC / TIMES_USED_DESC ordering is unchanged. (Shipped 2026-06-03.)

Non-breaking

  • Several inputs relaxed a required argument to optional: email on AssignWorkspacePlaceholderInput and MakeAccordMemberNonInternalInput, dealId on SearchHubspotDealContactsInput (which also gained companyId), and viewId on dataExportStatus (which also gained contextId). Calls that still send these arguments keep working.
  • createOrRecoverAccordDomain gained an optional isAccordCreation argument.
  • Most types and fields now carry descriptions in the reference.

2026-09-17: Activity moves to GET /1/analytics/activities​

  • New endpoint: GET https://api.inaccord.com/1/analytics/activities returns every activity event in your workspace, cursor-paginated, with the same Authorization: Bearer <key> header and the same field names the GraphQL Activity type uses. See Activity export, which includes a side-by-side migration for each shape of query we see in use.
  • The GraphQL activity and activitiesConnection queries are now marked deprecated in the schema. They still answer, and will keep answering through an announced migration window; the removal date will be posted here in advance.
  • Ordering is by updatedAt rather than by id, and since filters on updatedAt. updatedAt equals createdAt today, so an existing createdAt high-water mark carries over unchanged.
  • If you store duration, overlap your high-water mark by 15 minutes. Dwell time is written onto a row shortly after it is recorded and that write does not move updatedAt; the overlap is what makes an incremental sync see the final value. Activity export has the detail.
  • There is no offset. Follow pageInfo.endCursor.
  • The query string is first, after and since only. There is no filter by event name or accord. Pull the stream and filter your side, or ask us for a server-side filter and we will add one with an index behind it.

2026-09-08: The API endpoint is api.inaccord.com/graphql​

  • https://api.inaccord.com/graphql is now the documented GraphQL endpoint. It serves the same schema, takes the same Authorization: Bearer <key> header, and returns the same responses as api2.inaccord.com/graphql; only the hostname differs.
  • https://api2.inaccord.com/graphql still answers, so nothing breaks today, but it will stop accepting HTTP requests. Move your integration to api.inaccord.com when convenient. The retirement date will be announced here in advance.