# API changelog

Showing the latest 50 of 945 matching changes.
Source: https://raw.githubusercontent.com/apideck-libraries/openapi-specs/main/CHANGELOG.md
Fields: date, release, API, change type, connectors, resources, description.

## 2026-10-26 — Unified Apis — other

- Release: 10.73.1
- ID: 10.73.1-0
- API: unified-apis
- Change type: other
- Connectors: hubspot, pipedrive, activecampaign, folk
- Resources: pipelines
- Description: name on Pipelines no longer carries a minLength: 1 constraint and may be an empty string. It is now always returned: HubSpot, Pipedrive, ActiveCampaign and folk return an empty string for a pipeline without a name, where the field used to be left out.
- Details: https://developers.apideck.com/changelog?api=unified-apis&search=10.73.1

## 2026-10-26 — Unified Apis — other

- Release: 10.73.1
- ID: 10.73.1-1
- API: unified-apis
- Change type: other
- Connectors: act, adp-ihcm, adp-run, adp-workforce-now, exact-online, exact-online-nl, exact-online-uk, folks-hr, freshsales, intuit-bank-feeds, jumpcloud, liantis, microsoft-dynamics-hr, odoo, paylocity, plaid-exchange, salesflare, sap-s4hana-cloud, sap-successfactors, ukg-pro, wix, workday, zoho-people, lightspeed
- Resources: Not specified
- Description: Contact lists (phonenumbers, emails, websites and sociallinks) no longer include entries without a value on Act, ADP iHCM, ADP run, ADP Workforce Now, Exact Online, Exact Online (NL), Exact Online (UK), Folks HR, Freshsales, Intuit Bank Feeds, JumpCloud, Liantis, Microsoft Dynamics HR, Odoo, Paylocity, Plaid Core Exchange, Salesflare, SAP S/4HANA Cloud, SAP SuccessFactors, UKG Pro, Wix, Workday and Zoho People. These connectors could return an entry such as { "id": "primary" } without its email, or a phone entry with an extension but no number, which made strict clients reject the whole response; a record with none now returns an empty list. Lightspeed order phone numbers are now returned in number.
- Details: https://developers.apideck.com/changelog?api=unified-apis&search=10.73.1

## 2026-10-26 — Accounting — other

- Release: 10.73.0
- ID: 10.73.0-0
- API: accounting
- Change type: other
- Connectors: myob
- Resources: suppliers
- Description: MYOB now supports Suppliers: list, get, create, update and delete. Suppliers return their purchase tax code (taxrate), ABN or tax number (taxnumber), default expense account (account), remittance bank account (bankaccounts), up to five addresses and their contact details. Create requires taxrate.id. taxnumber is saved as the ABN when it has 11 digits, otherwise as the Tax ID number. An update changes only the fields you send and keeps the rest of the supplier, including details the unified model does not expose; it reads the supplier first, so it also needs read consent on suppliers. rowversion is optional and a stale one returns 409. MYOB keeps no address type, so addresses read back by position (primary, secondary, then other). Each address has an id (its position, "1" to "5") to update it in place; addresses cannot be removed, and requests MYOB cannot store, such as more than five addresses or more than one bank account, are rejected with a 400.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.73.0

## 2026-10-26 — Accounting — fix

- Release: 10.73.0
- ID: 10.73.0-1
- API: accounting
- Change type: fix
- Connectors: myob
- Resources: customers
- Description: Fixed MYOB Customers never returning displayid. It now returns the MYOB card ID (for example CUS00011); writes were unaffected.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.73.0

## 2026-10-26 — Accounting — other

- Release: 10.72.1
- ID: 10.72.1-0
- API: accounting
- Change type: other
- Connectors: sap-s4hana-cloud
- Resources: invoice-items, invoices
- Description: SAP S/4HANA Cloud Invoice Items now return unitprice and purchasedetails.unitprice from the product's valuation (cost) price, with its currency, and quantity from unrestricted-use stock (needs the SAPCOM0164 communication scenario, otherwise quantity is null and the response carries a warning). Invoices now also lists invoices created by SAP billing (financial accounting document type RV); billing credit memos and cancellations are not listed. For those invoices lineitems are the billing items, with item, quantity, unitprice and unitofmeasure (needs the SAPCOM0120 communication scenario, otherwise the lines stay G/L account lines and the response carries a warning), and line ids are <billing document>:<item>.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.72.1

## 2026-10-23 — Accounting — other

- Release: 10.72.0
- ID: 10.72.0-0
- API: accounting
- Change type: other
- Connectors: netsuite
- Resources: Not specified
- Description: NetSuite virtual webhooks now send accounting..deleted events for customers, suppliers, invoices, invoice items, ledger accounts, bills, bill payments, payments, purchase orders, projects, credit notes, quotes and expenses, so these events are advertised in supportedevents again. Deletes are detected from NetSuite's deleted-records log after each sync, so delete events arrive with the sync cadence, starting from each resource's second sync. Connections scoped to a subsidiary receive delete events for the whole account, because NetSuite does not record the subsidiary of a deleted record. Tax rates are not covered. Delete events need the Deleted Records and SuiteAnalytics Workbook permissions on the connection's role (both are in the Apideck NetSuite bundle; Deleted Records from v1.5.0); without them, created and updated events keep arriving and no delete events are sent.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.72.0

## 2026-10-22 — Platform — other

- Release: 10.71.1
- ID: 10.71.1-0
- API: platform
- Change type: other
- Connectors: netsuite, sage-intacct, sage-intacct-rest, zoho-books, workday, magento, prestashop, wix
- Resources: connectors
- Description: Connectors supportedevents no longer lists .deleted events for NetSuite, Sage Intacct, Sage Intacct REST, Zoho Books, Workday, Magento, PrestaShop and Wix. These connectors use virtual (polling) webhooks, which detect created and updated records but not deletions, so these events were never sent. Existing webhook subscriptions are unchanged, and created and updated events keep arriving as before.
- Details: https://developers.apideck.com/changelog?api=platform&search=10.71.1

## 2026-10-22 — Vault — other

- Release: 10.71.0
- ID: 10.71.0-0
- API: vault
- Change type: other
- Connectors: Not specified
- Resources: Not specified
- Description: Applications can now hide connection form fields they don't use from their consumers in Vault. In the dashboard, under Configuration → the unified API → the connector, untick fields in Fields visible in Vault: those fields come back with hidden: true in the connection's formfields, so Vault no longer shows them. Only optional fields can be hidden; required and required-for-authorization fields always stay visible, so consumers can always complete the connection. Hiding only affects the form: a value already saved on a connection keeps applying. Other applications using the same connector are unaffected.
- Details: https://developers.apideck.com/changelog?api=vault&search=10.71.0

## 2026-10-22 — Platform — other

- Release: 10.71.0
- ID: 10.71.0-1
- API: platform
- Change type: other
- Connectors: Not specified
- Resources: connectors
- Description: Connectors settings[] now include required, requiredforauthorization, hidden and, when present, description, so you can tell which connection settings can be hidden from Vault and what each one is for.
- Details: https://developers.apideck.com/changelog?api=platform&search=10.71.0

## 2026-10-22 — Accounting — other

- Release: 10.70.0
- ID: 10.70.0-0
- API: accounting
- Change type: other
- Connectors: zoho-books
- Resources: general-ledger-transactions, journal-entries
- Description: Zoho Books now supports General Ledger Transactions (list only). It returns every posting in the ledger, including invoices, payments, credit notes, expenses and manual journals, not only the manual journals that Journal Entries returns. Each transaction comes back whole with its balanced lines, and sourcetype and sourceid identify the document that posted it; id is the document id plus the posting date, because a document can post on more than one date (for example a payment received in advance and applied to an invoice later). The list covers the organization's full history; narrow it with passthrough[fromdate] and passthrough[todate], and use passthrough[cashbased]=true for cash basis. filter[...] is not supported, a single transaction cannot be read by id, and a page can hold fewer records than limit because limit counts ledger lines: follow next until it is null.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.70.0

## 2026-10-21 — HRIS — other

- Release: 10.69.10
- ID: 10.69.10-0
- API: hris
- Change type: other
- Connectors: workday
- Resources: employees
- Description: Workday Employees lists now support filter[asofdate] (YYYY-MM-DD) to return workers as of that date. Workday answers as of today by default, so future-dated hires were never returned; passing a future date includes them. The date applies to every worker in the list, so future-dated job and compensation changes are also returned as of that date. Lists without the filter are unchanged, and Get Employee does not accept it and always returns the worker as of today.
- Details: https://developers.apideck.com/changelog?api=hris&search=10.69.10

## 2026-10-21 — HRIS — fix

- Release: 10.69.9
- ID: 10.69.9-0
- API: hris
- Change type: fix
- Connectors: workday
- Resources: employees
- Description: Fixed Workday Employees dropping every address line when Workday returns more than one address component. addresses[].line1, line2 and line3 were null for such addresses (most non-US formats, for example France, Germany, the Netherlands, Sweden, Singapore and Japan), with only string populated. line1 now holds the street line with the house number appended when Workday's country format has a separate house-number component, that number is returned as streetnumber, and further components (building, unit, floor) fill line2 to line5 in Workday's order. jobs[].location follows the same rules and now also returns streetnumber. Addresses with a single ADDRESSLINE1 component, such as US ones, are unchanged apart from trimming of surrounding whitespace.
- Details: https://developers.apideck.com/changelog?api=hris&search=10.69.9

## 2026-10-21 — ATS — fix

- Release: 10.69.9
- ID: 10.69.9-1
- API: ats
- Change type: fix
- Connectors: workday
- Resources: applicants
- Description: Fixed Workday Applicants dropping every address line when Workday returns more than one address component. addresses[].line1 now holds the street line with the house number appended when the country format has a separate house-number component, streetnumber holds that number, and further components fill line2 to line5. Addresses with a single ADDRESSLINE1 component, such as US ones, are unchanged apart from trimming of surrounding whitespace.
- Details: https://developers.apideck.com/changelog?api=ats&search=10.69.9

## 2026-10-21 — Accounting — fix

- Release: 10.69.9
- ID: 10.69.9-2
- API: accounting
- Change type: fix
- Connectors: workday
- Resources: customers, suppliers
- Description: Fixed Workday Customers and Suppliers returning an empty addresses[].line1 when Workday returns more than one address component. line1 now holds the street line with the house number appended when the country format has a separate house-number component, and line2 to line5 and streetnumber are now returned. Addresses with a single ADDRESSLINE1 component, such as US ones, are unchanged apart from trimming of surrounding whitespace.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.69.9

## 2026-10-20 — Accounting — fix

- Release: 10.69.8
- ID: 10.69.8-0
- API: accounting
- Change type: fix
- Connectors: odoo
- Resources: bills, invoices, credit-notes, bill-credit-notes, purchase-orders, goods-receipts, bank-feed-statements, payments, bill-payments, journals
- Description: Fixed missing nested data on Odoo connections using data scopes. Requested and consented lineitems are now returned on Bills, Invoices, Credit Notes, Bill Credit Notes, Purchase Orders and Goods Receipts; transactions on Bank Feed Statements, allocations on Payments and Bill Payments, and defaultaccount on Journals are also retained. These fields could previously be empty or missing. Applications without data scopes are unchanged, and consent is not widened.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.69.8

## 2026-10-19 — CRM — other

- Release: 10.69.7
- ID: 10.69.7-0
- API: crm
- Change type: other
- Connectors: hubspot
- Resources: Not specified
- Description: HubSpot webhooks now deliver events from HubSpot's object. subscription format (object.creation, object.propertyChange, object.deletion), the default in HubSpot's current developer UI, for contacts, companies and deals, as crm.contact., crm.company. and crm.opportunity. created, updated and deleted events. Previously these events were accepted and dropped without an error, so only subscriptions using the classic names (contact.creation, …) delivered. Subscribing to the same event in both formats delivers it twice; both deliveries carry the same x-apideck-idempotency-key header. Merge, restore and association-change events are not delivered in either format.
- Details: https://developers.apideck.com/changelog?api=crm&search=10.69.7

## 2026-10-16 — Webhooks — other

- Release: 10.69.6
- ID: 10.69.6-0
- API: webhooks
- Change type: other
- Connectors: quickbooks, intuit-enterprise-suite
- Resources: Not specified
- Description: One Intuit webhook URL now delivers events for companies connected through either QuickBooks or Intuit Enterprise Suite. When the company (realm) of an incoming event has no connection under the connector the URL belongs to, the event is delivered through its connection under the other connector, with that connector's serviceid. A company connected through both receives the event only through the URL's connector. A disabled or invalid connection under the URL's connector still counts, so when a company moves between the two connectors, remove the old connection rather than disabling it. Delivery for companies that have a connection under the URL's connector is unchanged.
- Details: https://developers.apideck.com/changelog?api=webhooks&search=10.69.6

## 2026-10-16 — Platform — other

- Release: 10.69.6
- ID: 10.69.6-1
- API: platform
- Change type: other
- Connectors: quickbooks, intuit-enterprise-suite
- Resources: Not specified
- Description: webhooksupport on connectors now includes sharedwith: the service IDs of connectors whose connections also receive events from this connector's webhook URL. QuickBooks and Intuit Enterprise Suite list each other.
- Details: https://developers.apideck.com/changelog?api=platform&search=10.69.6

## 2026-10-16 — Unified Apis — other

- Release: 10.69.5
- ID: 10.69.5-0
- API: unified-apis
- Change type: other
- Connectors: Not specified
- Resources: Not specified
- Description: Application success and error responses now return the existing parent Logs ID in the x-apideck-request-id header, so you can correlate requests with Dashboard logs and share the ID with support. Proxy keeps its existing behavior. API Gateway-generated failures may omit the header. No requestid field is added to response bodies.
- Details: https://developers.apideck.com/changelog?api=unified-apis&search=10.69.5

## 2026-10-15 — Accounting — other

- Release: 10.69.4
- ID: 10.69.4-0
- API: accounting
- Change type: other
- Connectors: netsuite
- Resources: bill-payments
- Description: Behaviour change for NetSuite Bill Payments updates. An update that includes allocations now replaces the payment's bill allocations with the list sent: a bill left out is removed from the payment and its open balance is restored, so a payment can now be moved from one bill to another, and the payment total becomes the sum of the allocations applied. Previously the sent allocations were merged into the existing ones: a bill left out stayed applied, so moving a payment to another bill made it pay both. An update that omits allocations, or sends an empty list, still leaves the existing allocations unchanged. If you add a bill to a payment by sending only the new allocation, send the payment's full list of allocations instead, each with its amount. Vendor credits are unchanged: they can still only be applied when a payment is created, and an update does not unapply a credit applied then.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.69.4

## 2026-10-14 — Accounting — other

- Release: 10.69.3
- ID: 10.69.3-0
- API: accounting
- Change type: other
- Connectors: sage-intacct
- Resources: journal-entries, invoices, credit-notes
- Description: Sage Intacct now honours the Idempotency-Key header on Journal Entries, Invoices and Credit Notes creates. A 32-character value derived from the key is sent as the create's control id with Sage Intacct's duplicate check switched on, so a retry with the same key and body never creates a second record. It returns the original record's id when the values you sent identify it: a journal entry by its sourceid, an invoice or credit note by its number (or an invoice's code) and customer. Otherwise (no such value, or document sequencing replaced the number you sent) the retry returns Sage Intacct's "already recorded" error instead; nothing is written onto the record to find it. Creates without the header are unchanged.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.69.3

## 2026-10-14 — Accounting — other

- Release: 10.69.3
- ID: 10.69.3-1
- API: accounting
- Change type: other
- Connectors: sage-intacct-rest
- Resources: journal-entries, invoices, credit-notes
- Description: Sage Intacct REST now honours the Idempotency-Key header on Journal Entries, Invoices and Credit Notes creates. A 32-character value derived from the key is sent as Sage's own Idempotency-Key header, and Sage answers a retry with the same key and body with the original record, id included. Keys are remembered for 1 hour. Creates without the header are unchanged.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.69.3

## 2026-10-14 — Accounting — other

- Release: 10.69.3
- ID: 10.69.3-2
- API: accounting
- Change type: other
- Connectors: sage-intacct
- Resources: credit-notes
- Description: Sage Intacct Credit Notes lists now support filter[number] (exact match).
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.69.3

## 2026-10-14 — Accounting — other

- Release: 10.69.3
- ID: 10.69.3-3
- API: accounting
- Change type: other
- Connectors: Not specified
- Resources: invoices, credit-notes
- Description: Documented the Sage Intacct Accounts Receivable setting If duplicate numbers, which rejects an Invoices or Credit Notes create whose number already exists for the same customer.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.69.3

## 2026-10-14 — Accounting — fix

- Release: 10.69.1
- ID: 10.69.1-0
- API: accounting
- Change type: fix
- Connectors: netsuite
- Resources: invoices, bills, purchase-orders, quotes, goods-receipts, employees, projects, expense-reports
- Description: Fixed NetSuite returning date-only fields one calendar day early when the NetSuite integration user's time zone is east of UTC. NetSuite sends a date-only field as local midnight in the user's zone, expressed at the Pacific offset, so a record dated 2025-06-26 by a user on Amsterdam time arrives as 2025-06-25T15:00:00.000-07:00, which was read as 2025-06-25. This affected invoicedate and duedate on Invoices, billdate and duedate on Bills, duedate, issueddate and deliverydate on Purchase Orders, quotedate and expirydate on Quotes, receiveddate on Goods Receipts, hiredate, terminationdate and birthdate on Employees, startdate and enddate on Projects, and duedate and the line transactiondate on Expense Reports (get only). The fix applies to gets and to lists without filter, sort or passthrough; filtered and sorted lists are unchanged. No action is required for almost all accounts — these dates now read correctly without configuration for any NetSuite integration user between UTC-10 and UTC+13, and users from UTC-10 to UTC see unchanged values. The optional timezone connection setting from v10.37.0 now applies to reads as well: when set, reads are exact for every zone and tolerate a setting up to about 12 hours off in either direction. One regression: UTC-11 users (Pago Pago, Niue, Midway) read these dates correctly before and now read them one day late until timezone is set, the same setting they already need for writes. Kiritimati (UTC+14) read a day early before and still does without the setting.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.69.1

## 2026-10-14 — Proxy — other

- Release: 10.69.1
- ID: 10.69.1-1
- API: proxy
- Change type: other
- Connectors: sap-s4hana-cloud
- Resources: Not specified
- Description: SAP S/4HANA Cloud: OData write requests (any method other than GET, HEAD or OPTIONS) sent through the Proxy API now pass SAP's CSRF protection. Previously they failed with 403 "CSRF token validation failed", because SAP requires the session cookie issued with its CSRF token and the proxy does not forward a caller's Cookie header. Immediately before each write, the proxy fetches a token and session cookies from the OData service root of the requested URL and sends them with the write, retrying once if SAP still answers 403 with x-csrf-token: required. A retried write that still fails returns SAP's real response with x-apideck-downstream-error: true; a repeat CSRF rejection returns the original 403. Callers no longer need to fetch a token; an x-csrf-token they send is replaced by the proxy's when the handshake succeeds. If the proxy's token fetch fails, the request is forwarded unchanged and SAP's own 403 is returned. Each write makes one extra GET to the service root. The handshake, the write and the retry share the request's 28-second budget: the token fetch is shortened when little time remains, the write is given only the remaining time, a request that reaches the proxy with no time left is answered with 504 without contacting SAP, and the retry is skipped rather than started when it could not finish in time. Requests that supply their own credentials through x-apideck-downstream-authorization are not covered, and SOAP endpoints (/sap/bc/srt/…) are unaffected.
- Details: https://developers.apideck.com/changelog?api=proxy&search=10.69.1

## 2026-10-13 — Accounting — coverage-expansion

- Release: 10.69.0
- ID: 10.69.0-0
- API: accounting
- Change type: coverage-expansion
- Connectors: fiken
- Resources: customers, suppliers, invoice-items, projects, tracking-categories, invoices, credit-notes, quotes, sales-orders, journal-entries, bank-accounts, bills, payments, bill-payments, sales-receipts, attachments, ledger-accounts, tax-rates, payment-methods, general-ledger-transactions, companies, company-info, trial-balance
- Description: Added Fiken as an Accounting API connector (beta), for Norwegian small businesses on Fiken. It supports Customers, Suppliers, Products and Projects / Tracking Categories (read and write), Invoices (create, read, and update of the due date), Credit Notes, Quotes, Sales Orders, Journal Entries and Bank Accounts (create and read), Bills, Payments, Bill Payments and Sales Receipts (create, read and delete), Attachments on invoices, bills and journal entries, and Ledger Accounts with current balances, Tax Rates, Payment Methods, General Ledger Transactions, Companies, Company Info and Trial Balance (read). Fiken has no webhook API, so created and updated events for customers, suppliers, invoices, credit notes, products and bills are delivered by polling. A connection is authorized with OAuth, and the customer picks the Fiken company to connect.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.69.0

## 2026-10-13 — Accounting — other

- Release: 10.68.1
- ID: 10.68.1-0
- API: accounting
- Change type: other
- Connectors: netsuite
- Resources: credit-notes
- Description: NetSuite Credit Notes now return status from how much of the credit has been applied: authorised when none of it has, partiallypaid when part of it has, paid when all of it has, and voided for voided credit memos. Open credit memos were returned as draft before, and partiallypaid was never returned. A status NetSuite reports without amounts that Apideck does not recognise is now left out instead of being returned as draft.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.68.1

## 2026-10-13 — Accounting — other

- Release: 10.68.1
- ID: 10.68.1-1
- API: accounting
- Change type: other
- Connectors: netsuite
- Resources: invoices
- Description: NetSuite Invoices now return authorised for open invoices instead of draft, partiallypaid for open invoices with part of the amount paid (on filtered lists, where NetSuite reports the paid amount), submitted while pending approval, draft when rejected and void when voided. An unrecognised status is left out instead of being returned as draft.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.68.1

## 2026-10-13 — Accounting — coverage-expansion

- Release: 10.68.0
- ID: 10.68.0-0
- API: accounting
- Change type: coverage-expansion
- Connectors: e-conomic
- Resources: customers, suppliers, invoice-items, quotes, sales-orders, invoices, credit-notes, journal-entries, bills, bill-payments, ledger-accounts, tax-rates, journals, payment-methods, departments, fiscal-periods, trial-balance, company-info
- Description: Added e-conomic as an Accounting API connector (beta), for Danish businesses on e-conomic. It supports Customers, Suppliers, Products, Quotes and Sales Orders (read and write), Invoices and Credit Notes (booked records to read; drafts to create, update and delete), Journal Entries, Bills and Bill Payments (create and read), and Ledger Accounts, Tax Rates, Journals, Payment Methods, Departments, Fiscal Periods, Trial Balance and Company Info (read). Webhooks are delivered natively for customers, suppliers, products, invoices, quotes, ledger accounts and tax rates; credit notes arrive as invoice events. A connection takes the Agreement Grant Token the customer receives when they approve your e-conomic app.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.68.0

## 2026-10-13 — Accounting — other

- Release: 10.67.2
- ID: 10.67.2-0
- API: accounting
- Change type: other
- Connectors: netsuite
- Resources: journal-entries
- Description: NetSuite now honours the Idempotency-Key header on Journal Entries creates. The key is sent as the journal entry's externalId, so a retry with the same key and body returns the original journal entry's id instead of writing again or failing with DUPRCRD, including after a create that timed out but was saved. Creates without the header are unchanged.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.67.2

## 2026-10-13 — Ecommerce — other

- Release: 10.67.1
- ID: 10.67.1-0
- API: ecommerce
- Change type: other
- Connectors: shopify-public-app
- Resources: Not specified
- Description: Shopify (Public App) now requests Shopify's expiring offline access tokens on authorization (expiring=1) and refreshes them automatically using the issued refresh token, as Shopify requires for all public apps from 2027-01-01 (and already for apps created since 2026-04-01). Connections authorized before this release hold a non-expiring token without a refresh token and need to be re-authorized once through Vault.
- Details: https://developers.apideck.com/changelog?api=ecommerce&search=10.67.1

## 2026-10-10 — Accounting — coverage-expansion

- Release: 10.67.0
- ID: 10.67.0-0
- API: accounting
- Change type: coverage-expansion
- Connectors: Not specified
- Resources: fiscal-periods
- Description: Added Fiscal Periods (list and get, beta): the posting periods of a company's fiscal calendar, with startdate, enddate, fiscalyear (the four-digit year the fiscal year ends in), periodnumber, type (period, quarter or year), isadjustment, a status of open, locked (blocked for some users or transaction types), closed (blocked for all users) or future, and lockedthrough, the last date in the period a lock date rejects postings for, so an integration can check that a date is open before posting into it. status is null where the connector does not expose it, or reports a state with no unified equivalent.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.67.0

## 2026-10-10 — Accounting — other

- Release: 10.67.0
- ID: 10.67.0-1
- API: accounting
- Change type: other
- Connectors: netsuite, oracle-fusion, microsoft-dynamics-365-business-central, exact-online, twinfield, procountor-fi, pennylane, fortnox, spiris, visma-eaccounting, visma-netvisor, datev-unternehmen-online, minox, freeagent, xero, quickbooks, odoo, snelstart
- Resources: Not specified
- Description: Fiscal periods are supported on NetSuite, Oracle Fusion, Microsoft Dynamics 365 Business Central, Exact Online (NL and UK), Twinfield and Procountor. Pennylane, Fortnox, Spiris, Visma eAccounting, Visma Netvisor, DATEV Unternehmen Online, Minox and FreeAgent expose fiscal years only, returned as records with type: year. Xero, QuickBooks, Odoo and SnelStart have no fiscal-year list: their years are generated from the company's fiscal year-end setting, with status taken from the lock or closing dates where the connector has them. Which fields each connector derives, and how it maps its own period states, is listed per connector on the operation. On Fortnox, status and lockedthrough come from the company's locked period, which needs the optional settings scope. Connections do not request it by default, so they return status null until the application owner adds the scope and the customer re-authorizes.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.67.0

## 2026-10-10 — Accounting — coverage-expansion

- Release: 10.67.0
- ID: 10.67.0-2
- API: accounting
- Change type: coverage-expansion
- Connectors: Not specified
- Resources: trial-balance
- Description: Added Trial Balance (get, beta): every ledger account's balance as of filter[enddate] (today in UTC by default), as debit, credit and a signed balance, with totaldebit and totalcredit. Each line has a linetype and an accountid that GET /accounting/ledger-accounts/{id} accepts; lines with a zero balance are left out, and a report whose debits and credits do not balance returns a 502. Balance sheet accounts are cumulative to the date; income and expense accounts are year-to-date within the fiscal year that contains it. filter[accountingmethod] selects cash or accrual where the connector supports it, and returns a 400 where it does not.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.67.0

## 2026-10-10 — Accounting — other

- Release: 10.67.0
- ID: 10.67.0-3
- API: accounting
- Change type: other
- Connectors: netsuite, xero, quickbooks, intuit-enterprise-suite, sage-intacct, microsoft-dynamics-365-business-central, odoo, freeagent, dualentry, campfire, zoho-books, sage-business-cloud-accounting, minox, moneybird, datev-unternehmen-online, freshbooks, twinfield, visma-netvisor, spiris, visma-eaccounting, rillet, pennylane, exact-online, snelstart
- Resources: Not specified
- Description: Trial balance is supported on NetSuite, Xero, QuickBooks, Intuit Enterprise Suite, Sage Intacct, Microsoft Dynamics 365 Business Central, Odoo, FreeAgent, DualEntry, Campfire, Zoho Books, Sage Business Cloud Accounting, Minox, Moneybird, DATEV Unternehmen Online, FreshBooks, Twinfield, Visma Netvisor, Spiris, Visma eAccounting, Rillet, Pennylane, Exact Online (NL and UK) and SnelStart. NetSuite, Exact Online, Minox, Moneybird, DATEV and Twinfield report as of the end of the period or month that contains the date. Pennylane returns a 422 while an earlier fiscal year is still open, since its balance sheet balances would miss that year. Where a connector does not close earlier years' results into equity (NetSuite, Exact Online, Business Central, Odoo, Sage Business Cloud Accounting, Moneybird, Twinfield, Visma Netvisor, Minox), they are returned as one extra line, "Result of previous fiscal years (not yet appropriated)", with linetype unappropriatedresult and null accountid and code, so debits equal credits. SnelStart needs the rapportage scope on the connection key. The date semantics of each connector are listed on the operation.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.67.0

## 2026-10-09 — Accounting — coverage-expansion

- Release: 10.66.4
- ID: 10.66.4-0
- API: accounting
- Change type: coverage-expansion
- Connectors: Not specified
- Resources: invoices
- Description: Added the optional Idempotency-Key header to Invoices updates. A key on an update is scoped to the invoice it updates; connectors that cannot honour it reject it with 400.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.66.4

## 2026-10-09 — Accounting — other

- Release: 10.66.4
- ID: 10.66.4-1
- API: accounting
- Change type: other
- Connectors: quickbooks, intuit-enterprise-suite
- Resources: journal-entries, invoices
- Description: QuickBooks and Intuit Enterprise Suite now honour the Idempotency-Key header on Journal Entries and Invoices creates and on Invoices updates, voids included. A retry with the same key and body returns the original result instead of writing again, for 24 hours from the first attempt.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.66.4

## 2026-10-09 — Accounting — other

- Release: 10.66.3
- ID: 10.66.3-0
- API: accounting
- Change type: other
- Connectors: Not specified
- Resources: journal-entries, invoices, bills
- Description: Changed the example value of the Idempotency-Key header on Journal Entries, Invoices and Bills creates from a UUID to a readable placeholder. Behaviour is unchanged.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.66.3

## 2026-10-08 — Accounting — other

- Release: 10.66.2
- ID: 10.66.2-0
- API: accounting
- Change type: other
- Connectors: netsuite
- Resources: credit-notes, bill-credit-notes, bills, invoices, quotes, journal-entries
- Description: NetSuite now supports number filters on every transaction list that offers one: filter[number] on Credit Notes and Bill Credit Notes, and filter[billnumber] and filter[reference] on Bills, joining Invoices, Quotes and Journal Entries. Each is an exact match on the value the list and get return, and combines with the other filters. A bill number is the supplier's own, so filter[billnumber] can return bills from several suppliers.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.66.2

## 2026-10-08 — Accounting — fix

- Release: 10.66.2
- ID: 10.66.2-1
- API: accounting
- Change type: fix
- Connectors: netsuite
- Resources: bill-credit-notes
- Description: Fixed NetSuite Bill Credit Notes returning number: null on filtered lists (any filter[...]); they now return the same number (for example VENDCRED4) as the unfiltered list and get.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.66.2

## 2026-10-08 — Accounting — fix

- Release: 10.66.2
- ID: 10.66.2-2
- API: accounting
- Change type: fix
- Connectors: netsuite
- Resources: invoice-items
- Description: Fixed NetSuite Products creates and updates for Service items with a price returning Please enter missing quantity level(s) when NetSuite had actually rejected them for another reason, such as a missing tax schedule; the error now carries NetSuite's actual reason.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.66.2

## 2026-10-08 — Accounting — coverage-expansion

- Release: 10.66.1
- ID: 10.66.1-0
- API: accounting
- Change type: coverage-expansion
- Connectors: quickbooks, intuit-enterprise-suite
- Resources: sales-receipts, refunds
- Description: Added accounting.salesreceipt.created, accounting.salesreceipt.updated, accounting.salesreceipt.deleted, accounting.refund.created, accounting.refund.updated and accounting.refund.deleted webhook events for Sales Receipts and Refunds. Delivered by QuickBooks and Intuit Enterprise Suite, which map their native SalesReceipt and RefundReceipt change notifications to these events; emailed and voided notifications are delivered as the corresponding .updated event.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.66.1

## 2026-10-08 — Accounting — coverage-expansion

- Release: 10.66.0
- ID: 10.66.0-0
- API: accounting
- Change type: coverage-expansion
- Connectors: minox
- Resources: invoices, bills, credit-notes, bill-credit-notes, journal-entries, ledger-accounts, invoice-items, journals, tracking-categories, customers, suppliers, tax-rates, categories, balance-sheet, profit-and-loss, aged-debtors, aged-creditors, attachments
- Description: Added the Minox connector. Supported: Invoices, Bills, Credit Notes and Bill Credit Notes (list, get, create, delete), Journal Entries (list, get, create, delete), Ledger Accounts and Invoice Items (list, get, create, update, delete), Journals and Tracking Categories (list, get, create, update), Customers and Suppliers (list, get, create, update), Tax Rates and Categories (read), Balance Sheet, Profit and Loss, Aged Debtors, Aged Creditors, and Attachments on journal entries, invoices, bills and both credit-note types.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.66.0

## 2026-10-08 — Accounting — other

- Release: 10.66.0
- ID: 10.66.0-1
- API: accounting
- Change type: other
- Connectors: minox
- Resources: Not specified
- Description: Minox books invoices, bills and credit notes on the administration's sales or purchase journal, so they are posted on create (no drafts), cannot be updated (delete and create again), and take no discounts. Their status and balance follow Minox's open items. When an administration has more than one sales or purchase journal, choose the one to book on in the connection settings.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.66.0

## 2026-10-08 — Accounting — other

- Release: 10.66.0
- ID: 10.66.0-2
- API: accounting
- Change type: other
- Connectors: minox
- Resources: Not specified
- Description: Minox supports virtual webhooks (created and updated events) for invoices, bills, credit notes, customers, suppliers, invoice items, ledger accounts, tax rates and tracking categories. Deletions are not reported, and sorting is not supported on any list: Minox records have no timestamps.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.66.0

## 2026-10-08 — Accounting — other

- Release: 10.66.0
- ID: 10.66.0-3
- API: accounting
- Change type: other
- Connectors: minox
- Resources: Not specified
- Description: Minox connections are approved by the main user of the Minox subscription, and a record holds at most one attachment. Quotes are not available yet: Minox has to enable its ordering API for the subscription.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.66.0

## 2026-10-08 — Accounting — coverage-expansion

- Release: 10.65.0
- ID: 10.65.0-0
- API: accounting
- Change type: coverage-expansion
- Connectors: acumatica, myob-acumatica, sage-intacct, sage-intacct-rest, fortnox
- Resources: sales-orders
- Description: Added a new Sales Orders resource (beta): the customer's committed order with product line items, as distinct from the AR invoice it later becomes. It carries number, ordertype (the downstream order/transaction type), customer, ponumber (the customer's purchase order number) and reference, orderdate, deliverydate (the requested delivery date), status (draft, open, onhold, backordered, invoiced, closed, cancelled, other), amounts (subtotal, totaltax, total and the read-only unbilledamount), shippingmethod, paymentmethod, customermemo and internal notes, invoiceid and quoteid where the system records the link, billing and shipping addresses, custommappings, and lineitems using the shared invoice line-item model so each line can reference an inventory item. List, get, create, update and delete are available, with filter[number], filter[customerid], filter[updatedsince], filter[createdsince] and filter[subsidiaryid]. Supported on Acumatica and MYOB Acumatica (SalesOrder entity; every line needs an InventoryID via item.id or code; ordertype defaults to SO; status: onhold places the order on hold on create), Sage Intacct (Order Entry documents of the Order class; lists are header-only, lines come back on get; create resolves the Order transaction definition from ordertype, the new salesorderdocumenttype connection setting, or the company's single active definition; lines need item.id and unitofmeasure, and locationid on multi-entity companies), Sage Intacct REST (same definition resolution via document::{definition}; SYS- fulfilment definitions are excluded) and Fortnox (customer orders on /3/orders; status derived from the cancelled/invoiced/sent flags, invoiceid and quoteid from the invoice and offer references; DELETE cancels the order, as Fortnox has no delete). Sage Intacct does not record the invoice created from an order, so invoiceid is not returned there; the document an order was converted from is exposed as the sourcedocumentkey custom field, because it is not necessarily a quote. Not yet mapped on other accounting connectors.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.65.0

## 2026-10-07 — Accounting — coverage-expansion

- Release: 10.64.0
- ID: 10.64.0-0
- API: accounting
- Change type: coverage-expansion
- Connectors: xero
- Resources: journal-entries, invoices, bills
- Description: Added an optional Idempotency-Key header to Journal Entries, Invoices and Bills creates, so a create that times out or ends with an uncertain outcome can be retried safely. Generate one key per record you create (a UUID is recommended; 1-255 printable ASCII characters, sent bare or as a quoted string) and resend it with the same body on every retry: the record is created at most once. A key is remembered for 24 hours from its first use, or for the connector's own deduplication window where that is shorter (Xero: 6 minutes); after that, the same key is treated as a new request, so retry within the window. A retry while the first attempt is still running returns 409, reusing a key with a different body returns 422, and a key sent to a connector or operation that cannot honour it returns 400 instead of creating the record unprotected. Requests without the header are unchanged. Support is enabled per connector, starting with Xero Bills creates.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.64.0

## 2026-10-07 — Accounting — other

- Release: 10.63.0
- ID: 10.63.0-0
- API: accounting
- Change type: other
- Connectors: freeagent
- Resources: bill-payments, payments, projects, general-ledger-transactions, expenses, quotes, bank-feed-statements, attachments, bank-accounts
- Description: FreeAgent now supports Bill Payments, Payments, Projects, General Ledger Transactions (read-only), Expenses, Quotes, Bank Feed Statements and Attachments on bills, bill credit notes and expenses, plus deleting Bank Accounts. FreeAgent records a payment as an explanation on a bank account, so each bill payment or payment settles exactly one document and lists are read across every bank account. A bill, credit note or expense holds one attachment, and uploading again replaces it. Bank feed statements cannot be updated. See the FreeAgent notes on each resource for the details.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.63.0