> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/others/release-notes/5.7.0-october-28-2026.md). # 5.7.0 October 28, 2026 This release lets you configure more than one authentication method for a New System, adds a Usage Report to Analytics, and introduces automatic retries for API calls. ## New Features/Improvements * **Usage Report:** The Analytics page now has an API Usage tab where you can track API usage across your Projects, broken down by Project, Workflow, and API for any date range. Drill down from the usage graph to the related API logs to see exactly what’s driving your usage. Analytics now shows only the Projects you own, with shared Projects excluded, and is available to Project owners only. * **API Call Automatic Retries:** The API Call Step can now retry a failed call up to 5 times, so a brief outage doesn’t fail your Workflow. Turn on retries in the Step’s Advanced section, then set the interval and choose which status codes trigger a retry (timeouts and temporary failures by default). Changes apply from the next sync * **Multiple Authentication:** You can now configure more than one authentication method for a single New System in System Builder, instead of just one. When users connect to that System, they choose the method that fits their setup, so you don’t need to build a separate System for each authentication type. * **Email Notification Preferences**: You can now choose which Integrator emails you receive by category, such as Project Summary Reports, Workflow Notification Tool’s emails, Workflow job failures, and System health checks. This cuts down inbox noise while keeping the alerts you rely on. * **Access API Response Headers**: You can now read the response headers from token authentication and other API calls, not just the response body. This lets you reuse values such as session or route IDs on later calls, so you don’t have to log in again for every request * **Phone Number Formatter Step**: Format phone numbers for a selected region, such as the US or UK, in a single Step. For example, 15551234567 becomes +1 (555) 123-4567, so phone numbers reach the destination System in a consistent format without custom code. * **EDI Logs**: Finding, tracking, and correcting individual EDI transactions is now easier: * **Transaction Set tracking**: When one file contains multiple documents, such as several purchase orders in a single 850, each is tracked by its own purchase order, invoice, or shipment number, so you can follow a specific document without working through the whole file. * **Trading partner**: Each log entry shows which trading partner it belongs to. * **Edit & Send**: A larger clickable area makes it easier to add a line between two existing segments. * **Full file names**: Hover over a truncated file name to see it in full. * **3 New Public Systems Added** * CS Cart * CommerceLayer * BoxHero ## Bug Fixes * **Workflows and Pipes** * **Pipe editing in Firefox:** Editing a Pipe in Firefox now opens the page correctly instead of showing a blank screen. * **Log search:** Searching Log and Detail Log by an Entity ID that starts with a special character, such as #498, now returns the matching results. * **Support Tickets** * **Closed Tickets search**: Searching in Closed Tickets now shows results faster. * **EDI** * **Company dropdown:** In EDI, the Company dropdown now shows each company’s icon. * **Adding connectors:** Entering an invalid URL while adding a connector no longer shows a success message when the connector wasn’t created. The form also no longer keeps your previous input when you reopen it. * **Partner Builder:** The transaction types shown for an integration now match what’s configured for that partner, instead of every available type. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dckapintegrator.com/others/release-notes/5.7.0-october-28-2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.