# API changelog

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

## 2026-11-05 — Issue Tracking — other

- Release: 10.78.0
- ID: 10.78.0-0
- API: issue-tracking
- Change type: other
- Connectors: github, gitlab, gitlab-server, jira, jira-api-token, linear
- Resources: webhook-events, collections, collection-tickets
- Description: Ticket Webhook Events (issue-tracking.ticket.created, issue-tracking.ticket.updated and issue-tracking.ticket.deleted) now include collectionid: the Collection (repository or project) the ticket belongs to, the same value already in entityurl. Together with entityid it identifies the ticket for Collection Tickets calls without searching every collection, which matters on GitHub, where entityid is the issue number and is only unique within a repository. It is sent for GitHub, GitLab, GitLab on-prem, Jira and Jira (API Token). Other connectors, such as Linear, do not include it, so treat collectionid as optional.
- Details: https://developers.apideck.com/changelog?api=issue-tracking&search=10.78.0

## 2026-11-03 — HRIS — new-connector

- Release: 10.77.0
- ID: 10.77.0-0
- API: hris
- Change type: new-connector
- Connectors: sdworx-webservice-oidc, sdworx-webservice
- Resources: employees, time-off-requests
- Description: Added new SD Worx (Web service) connector with support for Employees and Time Off Requests. It reads the same SD Worx HR Selfservice Absences webservice as the existing SOAP connector, now over REST with OIDC client credentials: SD Worx registers a certificate per customer and issues a Client ID for it, which the consumer enters together with the certificate's private key in the connection form. SD Worx no longer activates the username/password access the SOAP connector relies on, so that connector is now named SD Worx (Web service) Legacy and declares the new connector as its migration target; existing legacy connections keep working. time-off-requests returns one record per employee per day (or day part) from the absence report, requires the startdate, enddate, companyid and employeeid filters (one employee per request, as the legacy connector does), returns enddate (equal to startdate, one record per day) and description (the absence code label), and converts updatedat and the updatedsince filter between UTC and the Belgian local time SD Worx records; SD Worx limits each Client ID to 1,000 requested employee-months per day. employees exposes id, first name, last name and company id only.
- Details: https://developers.apideck.com/changelog?api=hris&search=10.77.0

## 2026-11-03 — Accounting — other

- Release: 10.76.1
- ID: 10.76.1-0
- API: accounting
- Change type: other
- Connectors: netsuite
- Resources: quotes
- Description: NetSuite Quotes: status can now be set on create and update; before, it was accepted and ignored. sent, accepted and rejected set the estimate's sales stage (Proposal, Purchasing and Closed Lost), and draft is accepted but sets no sales stage: a new quote starts at the account's default stage, and an update leaves the stage unchanged. On an update, a status the quote already reads as changes nothing, so a quote at another stage that reads as sent, such as In Negotiation, keeps it. Proposal, Purchasing and Closed Lost are matched by exact name, so renaming one of them in NetSuite makes the status that sets it return 422; a quote at any other renamed stage reads draft. converted, void, expired and deleted, which NetSuite sets itself, now return 422, except that an update may send back converted, void or expired when the quote already has that status, so a quote read and sent back unchanged still saves. For a quote whose customer is a prospect, NetSuite also moves the prospect's status to the same stage. Reads also changed: a rejected (Closed Lost) quote reads rejected, an expired one expired and a voided one void, where all three used to read draft; an open quote in a sales stage of the account's own reads draft instead of rejected; and filtered or sorted lists now report the same status as unfiltered ones, including on later pages, instead of always draft. These read changes do not update a quote's last-modified date, so a sync that filters on updatedsince keeps the old values until it runs a full resync.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.76.1

## 2026-11-02 — Accounting — other

- Release: 10.76.0
- ID: 10.76.0-0
- API: accounting
- Change type: other
- Connectors: yuki
- Resources: bank-feed-statements
- Description: Yuki now supports Bank Feed Statements: create, list and get. Yuki has no bank statement API, so a created statement is uploaded to the administration's archive as a CAMT.053 bank file, which Yuki books on its own, usually within a minute; the response returns the archive document id. bankfeedaccountid is the bank account's IBAN, which does not need to exist in Yuki beforehand; an IBAN with invalid check digits, or the wrong length for a SEPA country, returns a 400. startbalance is required, and an endbalance that does not equal the start balance plus the transactions returns a 400. status is pending until Yuki has booked the file and success after; Yuki never reports a rejection, so a file it could not process stays pending, and a statement for a period already imported for the same IBAN is accepted but its transactions are skipped. Get returns the balances and transactions read from the stored file; the list returns statement headers only, including files a bookkeeper uploaded directly. The currency is always EUR, statements cannot be updated or deleted, and bank feed accounts are not supported because Yuki has no API to list bank accounts.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.76.0

## 2026-11-02 — Accounting — coverage-expansion

- Release: 10.75.0
- ID: 10.75.0-0
- API: accounting
- Change type: coverage-expansion
- Connectors: Not specified
- Resources: ledger-accounts
- Description: Added fixedasset to Ledger Accounts (read-only), for an account that holds the cost of fixed assets: cost and accumulateddepreciation (totals over the assets in the account), and acquisitiondate, depreciationmethod (normalised, with the system's own value in downstreamdepreciationmethod) and usefullifemonths. An account usually holds several assets, so the date, method and useful life are set only when every asset in the account has the same value. Other accounts, including accumulated-depreciation accounts, have no fixedasset.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.75.0

## 2026-11-02 — Accounting — other

- Release: 10.75.0
- ID: 10.75.0-1
- API: accounting
- Change type: other
- Connectors: quickbooks
- Resources: Not specified
- Description: QuickBooks: fixedasset.cost and fixedasset.accumulateddepreciation on each top-level account of type Fixed Asset, from the account and its sub-accounts. QuickBooks has no acquisition date, depreciation method or useful life.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.75.0

## 2026-11-02 — Accounting — other

- Release: 10.75.0
- ID: 10.75.0-2
- API: accounting
- Change type: other
- Connectors: xero, zoho-books
- Resources: Not specified
- Description: Xero and Zoho Books: the whole fixedasset object, from the fixed-asset register. Reading the register costs extra requests, so it is computed only when fields names fixedasset or one of its sub-fields. Xero needs the assets.read scope, which is now in Apideck's default scope set: connections authorized before this release must be re-authorized, and until then fixedasset is not set. Zoho Books needs a Premium plan or higher with the Fixed Asset module enabled.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.75.0

## 2026-11-02 — Ecommerce — other

- Release: 10.74.2
- ID: 10.74.2-0
- API: ecommerce
- Change type: other
- Connectors: amazon-seller-central
- Resources: Not specified
- Description: Amazon Seller Central integrations have a new optional Selling Partner Appstore listing setting. Not listed (Draft), the default, keeps today's behaviour; choose Listed on the Selling Partner Appstore (Published) once your SP-API app is published there, so authorisation no longer requests your app's Draft version (version=beta). The setup guides were also corrected: apps that are not listed are supported (Amazon allows up to 25 seller authorisations for them), and MD1000, MD9000 and MD9100 are explained.
- Details: https://developers.apideck.com/changelog?api=ecommerce&search=10.74.2

## 2026-11-02 — Accounting — other

- Release: 10.74.1
- ID: 10.74.1-0
- API: accounting
- Change type: other
- Connectors: sap-s4hana-cloud
- Resources: invoices, credit-notes, journal-entries, payments, bill-payments
- Description: SAP S/4HANA Cloud Invoices, Credit Notes, Journal Entries, Payments and Bill Payments lists now return meta.cursors.next and page through every record; before, they stopped after the first page. limit counts SAP posting lines, so a page can hold fewer records than limit; a record with more posting lines than limit comes back complete on a page of its own unless it has more than 5,000 lines or cannot be read within the request's time budget. meta.totalcount is no longer returned for these lists and meta.cursors.previous is always null; passthrough of $top, $skip or $orderby on them returns 400.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.74.1

## 2026-10-30 — Accounting — other

- Release: 10.74.0
- ID: 10.74.0-0
- API: accounting
- Change type: other
- Connectors: quickbooks, intuit-enterprise-suite, zoho-books, sage-business-cloud-accounting, moneybird, pennylane, netsuite
- Resources: invoices
- Description: Invoices now include quotes: the quotes (estimates) linked to an invoice, each with its id and, where available, number. Supported on QuickBooks, Intuit Enterprise Suite, Zoho Books, Sage Business Cloud Accounting, Moneybird, Pennylane and NetSuite. Creates can link quotes on all of these except Pennylane and NetSuite, and updates only on QuickBooks and Intuit Enterprise Suite; QuickBooks and Intuit Enterprise Suite accept several quotes per invoice, the others one. Zoho Books returns quotes on get but not on list.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.74.0

## 2026-10-29 — HRIS — fix

- Release: 10.73.2
- ID: 10.73.2-0
- API: hris
- Change type: fix
- Connectors: workday
- Resources: employees
- Description: Fixed Workday Employees returning parts of the street line in addresses[].line2 for some countries. Spanish addresses with a separate street type (Calle, Carrer) now return it at the start of line1 (for example Calle Montesa 16), and French addresses whose house number Workday labels Street Number now return it in streetnumber and at the end of line1 (for example Rue Juliette Lamber 13). In both cases line2 no longer carries that component. Street-name components labelled Street, Name of Street or Street Name and Type are now recognised directly instead of by position, and a labelled street name now goes to line1 even when it is not Workday's first address line. jobs[].location follows the same rules.
- Details: https://developers.apideck.com/changelog?api=hris&search=10.73.2

## 2026-10-29 — HRIS — fix

- Release: 10.73.2
- ID: 10.73.2-1
- API: hris
- Change type: fix
- Connectors: workday
- Resources: companies, departments
- Description: Fixed Workday Companies and Departments lists failing with a 500 on tenants whose company or cost center hierarchy organization type has a different reference ID (for example COMPANYHIERARCHYTYPE). The list is now requested again without the hierarchy type and returns the companies and cost centers; tenants where the hierarchy type exists are unchanged.
- Details: https://developers.apideck.com/changelog?api=hris&search=10.73.2

## 2026-10-29 — HRIS — other

- Release: 10.73.2
- ID: 10.73.2-2
- API: hris
- Change type: other
- Connectors: workday
- Resources: time-off-requests
- Description: Workday Time-Off Requests now return 501 (unsupported). Workday's web services have no operation that reads time off requests, and the previous mapping failed on every call.
- Details: https://developers.apideck.com/changelog?api=hris&search=10.73.2

## 2026-10-29 — HRIS — fix

- Release: 10.73.2
- ID: 10.73.2-3
- API: hris
- Change type: fix
- Connectors: workday
- Resources: employees
- Description: Fixed Workday Employees returning compensations[].paymentunit and jobs[].paymentunit as null for workers paid hourly or weekly. They now return hour or week, alongside month and year; other pay frequencies (for example bi-weekly) return other.
- Details: https://developers.apideck.com/changelog?api=hris&search=10.73.2

## 2026-10-29 — ATS — fix

- Release: 10.73.2
- ID: 10.73.2-4
- API: ats
- Change type: fix
- Connectors: workday
- Resources: applicants
- Description: Fixed Workday Applicants returning parts of the street line in addresses[].line2 for some countries. A separate street type (Spanish Calle, Carrer) now starts line1 (for example Calle Montesa 16), and a house number that Workday labels Street Number is now returned in streetnumber and at the end of line1 (for example Rue Juliette Lamber 13). In both cases line2 no longer carries that component. Street-name components labelled Street, Name of Street or Street Name and Type are now recognised directly, and a labelled street name now goes to line1 even when it is not Workday's first address line.
- Details: https://developers.apideck.com/changelog?api=ats&search=10.73.2

## 2026-10-29 — ATS — other

- Release: 10.73.2
- ID: 10.73.2-5
- API: ats
- Change type: other
- Connectors: workday
- Resources: applicants
- Description: Workday Applicants create, update and delete now return 501 (unsupported) instead of 404. These operations were never implemented for Workday; listing and getting applicants is unchanged.
- Details: https://developers.apideck.com/changelog?api=ats&search=10.73.2

## 2026-10-29 — Accounting — fix

- Release: 10.73.2
- ID: 10.73.2-6
- API: accounting
- Change type: fix
- Connectors: workday
- Resources: customers, suppliers
- Description: Fixed Workday Customers and Suppliers returning parts of the street line in addresses[].line2 for some countries. A separate street type (Spanish Calle, Carrer) now starts line1 (for example Calle Montesa 16), and a house number that Workday labels Street Number, as on South African addresses, is now returned in streetnumber and at the end of line1 (for example Swartkoppies Road 35). In both cases line2 no longer carries that component. Street-name components labelled Street, Name of Street or Street Name and Type are now recognised directly, and a labelled street name now goes to line1 even when it is not Workday's first address line.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.73.2

## 2026-10-29 — Accounting — fix

- Release: 10.73.2
- ID: 10.73.2-7
- API: accounting
- Change type: fix
- Connectors: workday
- Resources: payments
- Description: Fixed Workday Payments returning no id for payments without a payment reference ID. The id now falls back to the Workday WID, which get and update accept; payments that have a reference ID keep it as their id.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.73.2

## 2026-10-29 — Accounting — fix

- Release: 10.73.2
- ID: 10.73.2-8
- API: accounting
- Change type: fix
- Connectors: workday
- Resources: bills, purchase-orders
- Description: Fixed Workday Bills and Purchase Orders delete always failing with a Workday validation error; they now cancel the bill or purchase order. Fixed purchase order update failing whenever shippingaddress.id or billingaddress.id was sent.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.73.2

## 2026-10-29 — Accounting — fix

- Release: 10.73.2
- ID: 10.73.2-9
- API: accounting
- Change type: fix
- Connectors: workday
- Resources: bills
- Description: Fixed Workday Bills returning attachment notes as an object instead of the comment text.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.73.2

## 2026-10-29 — Accounting — fix

- Release: 10.73.2
- ID: 10.73.2-10
- API: accounting
- Change type: fix
- Connectors: workday
- Resources: journal-entries
- Description: Fixed Workday Journal Entries create failing with a Workday validation error when sourcetype is not sent. The journal source now defaults to ManualJournal.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.73.2

## 2026-10-29 — Accounting — fix

- Release: 10.73.2
- ID: 10.73.2-11
- API: accounting
- Change type: fix
- Connectors: workday
- Resources: suppliers
- Description: Fixed Workday Suppliers returning no paymentmethod when the supplier accepts several payment types; it now returns the default payment type. A supplier update now keeps the supplier's other accepted payment types instead of replacing them with paymentmethod, which becomes the default.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.73.2

## 2026-10-29 — Accounting — other

- Release: 10.73.2
- ID: 10.73.2-12
- API: accounting
- Change type: other
- Connectors: workday
- Resources: customers, suppliers
- Description: Workday Customers and Suppliers create and update now use displayname as the business entity name when companyid is not sent. Workday requires the two names to match, so a create with only displayname no longer fails.
- Details: https://developers.apideck.com/changelog?api=accounting&search=10.73.2

## 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