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-11-19: API keys expire
- Breaking:
createApiKeytakes a newexpiryargument (ApiKeyExpiry:DAYS_30,DAYS_60,DAYS_90,YEAR_1, orNEVER) and defaults toDAYS_90. A call that omitsexpiryused to return a key that never expired and now returns one that stops working after 90 days. Passexpiry: NEVERto keep the old behavior. ApiKey.expiresAtshows when a key stops working, and isnullfor a key that never expires. A request made with an expired key is refused.- A key created by an API key that expires cannot outlive it. A longer
expiryis shortened to end when the calling key does, andNEVERis refused. - Keys created before this change are unaffected and never expire.
2026-10-30: Deletes take an id, and library content must be Lexical
- Breaking: the generated
delete…ByNodeIdanddelete…By<UniqueKey>mutations (for exampledeleteStepToDoByStepIdanddeleteWorkspaceAccountByNodeId) are gone from the schema. They returned success without deleting anything. Call the matchingdelete…mutation with the row'sidinstead, for exampledeleteWorkspaceAccount. createLibraryResource,createLibraryResourceVersion, andupdateLibraryResourceVersionnow rejectcontentthat isn't a Lexical editor state serialized as a JSON string. HTML, Markdown, and plain text were stored before but showed as a blank page in Accord. Sendnullto clear the content.
2026-09-29: Import meetings with importMeeting
- New mutation:
importMeetingstores a meeting, its participants, and its transcript pushed from your own recording or calling system, with the sameAuthorization: Bearer <key>header as every other call. Use it when the recording lives somewhere Accord doesn't sync from. - The response confirms storage only. The meeting is stored unassigned and
matched to accords a few seconds later: by
crmDealIdfirst, thencrmAccountId, then participant email domains. Pass the CRM deal id whenever you have it. - Idempotent on
externalId. Re-sending an id you already imported returns the stored meeting withcreated: falseand writes nothing, so retries are safe. - Limits: 2 to 200 participants, at most 5,000 transcript segments or 1 MB of
transcript, and meetings of 60 seconds or longer. Rejections carry a stable
extensions.code; see Import errors. - Meeting import is enabled per workspace. Until it is on for yours, the
mutation returns
FEATURE_DISABLED. - The generated
createMeeting,updateMeeting,createMeetingAccord,updateMeetingAccord,createMeetingParticipant, andupdateMeetingParticipantmutations are gone from the schema. Those tables are written only by imports and the provider syncs. UseimportMeetingto add a meeting, andimportMeetingFromGongUrl,importMeetingFromZoomUrl, orimportMeetingFromOutreachUrlto pull one from a provider.
2026-09-22: Subscriptions removed from the reference
- The
Subscriptionroot 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
deleteAccordnow takesDeleteAccordInput { accordId }and returnsDeleteAccordPayload { 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.)deleteAccordByNodeIdandDeleteAccordByNodeIdInputwere removed. UsedeleteAccordwithaccordId. (Shipped 2026-05-28.)LibraryResourceFilter.timesUsedwas removed, so library resources can no longer be filtered ontimesUsed. TheLibraryResource.timesUsedfield still works andTIMES_USED_ASC/TIMES_USED_DESCordering is unchanged. (Shipped 2026-06-03.)
Non-breaking
- Several inputs relaxed a required argument to optional:
emailonAssignWorkspacePlaceholderInputandMakeAccordMemberNonInternalInput,dealIdonSearchHubspotDealContactsInput(which also gainedcompanyId), andviewIdondataExportStatus(which also gainedcontextId). Calls that still send these arguments keep working. createOrRecoverAccordDomaingained an optionalisAccordCreationargument.- 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/activitiesreturns every activity event in your workspace, cursor-paginated, with the sameAuthorization: Bearer <key>header and the same field names the GraphQLActivitytype uses. See Activity export, which includes a side-by-side migration for each shape of query we see in use. - The GraphQL
activityandactivitiesConnectionqueries 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
updatedAtrather than by id, andsincefilters onupdatedAt.updatedAtequalscreatedAttoday, so an existingcreatedAthigh-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 moveupdatedAt; the overlap is what makes an incremental sync see the final value. Activity export has the detail. - There is no
offset. FollowpageInfo.endCursor. - The query string is
first,afterandsinceonly. 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/graphqlis now the documented GraphQL endpoint. It serves the same schema, takes the sameAuthorization: Bearer <key>header, and returns the same responses asapi2.inaccord.com/graphql; only the hostname differs.https://api2.inaccord.com/graphqlstill answers, so nothing breaks today, but it will stop accepting HTTP requests. Move your integration toapi.inaccord.comwhen convenient. The retirement date will be announced here in advance.