💡 What's New?

Manage record attachments straight from the API. Attachments fields make batch image/document management workflows a breeze. Now, these fields have their own OpenAPI endpoints, so integrations can upload, download, and delete record file attachments programmatically — no UI required. Build integrations that push documents into TrackVia from an external system, pull attachments out for archival purposes, or clean up files as part of an automated workflow:

• Upload one or more files to an Attachments field in a single call — uploads are additive, so new files are appended alongside whatever's already there.
• Download a specific attachment by ID, streamed back with the correct file type and filename.
• Delete one or more specific attachments, or clear every attachment on a field in one call.

Every endpoint respects the same form and view permissions you've already set up — if a user or API key can't see or edit a field in the UI, the same rule applies through the API.

For more information on integrations, or to start building against these endpoints, see TrackVia's OpenAPI Docs and the TrackVia Knowledge Base

🛠️ What's Fixed?

• Record History no longer misreports old changes as "changed from empty." In accounts with a long edit history on a record, opening the History panel without a date filter could show the oldest entry on a page as if every field had just changed from empty to its current value. That's now fixed; History reflects only the fields that actually changed on that entry.
• Workato sandbox triggers no longer fire on unrelated edits. A Workato recipe using the "New record in view" trigger against a TrackVia Sandbox could fail to fire or incorrectly re-fire the first time an existing record was edited. New sandboxes now build a complete history baseline as part of creation, so recipes only fire for genuinely new records or records that newly match the view's criteria.

API v24.22