Record Attachments API

What's New

Files that belong on a SafetyChain record can now get there without anyone downloading and re-uploading them. The new Record Attachments API lets external systems (ERP, LIMS, WMS, PLM, supplier portals, label verification apps, vision systems, and other custom integrations) deposit files directly onto a specific field on a specific record in SafetyChain.

The Record Attachments API is part of the Inbound APIs family, which enables external systems to drive activity within SafetyChain. Where the existing Inbound APIs focus on creating records and tasks, this API extends the family to record modification, so external systems can enrich existing records with their supporting files. The caller supplies a record ID and a field ID (where the field is configured to accept attachments) and submits the file in the request. SafetyChain stores it against that field, where it is available wherever record content is reviewed.

Built for Label Verification, and More

The Record Attachments API was originally developed at the request of an enterprise customer running a label verification program, and is now generally available. In that pattern, a customer-built or third-party label verification application captures the label images, performs the comparison in its own environment, and uses this API to deposit the captured images onto the corresponding SafetyChain record. The result is a complete record (operator action, timestamps, and image evidence) that appears in SafetyChain history alongside any other quality activity. The same request pattern works for any external system that needs to land a file on an existing SafetyChain record, including LIMS results, supplier and vendor documents, vision and imaging output, and ERP-generated shipping or production documents.

Field-Level Placement

Attachments are placed on a specific field within a record, not just at the record level. That means multiple files can land on the appropriate fields within the same record. For example, multiple label images can be deposited on their respective fields of a verification record, or a lab result and a supplier document can be placed on the appropriate fields of an inspection record. This preserves the structured context that reviewers and auditors already operate against.

Same Integration Pattern as Other Inbound APIs

The Record Attachments API is exposed through the SafetyChain APIM gateway and uses the same authentication and access patterns as the rest of the Inbound APIs. Customers already integrated for record or task creation can extend that integration to handle attachments without learning a new pattern.

Benefits

• External systems can deposit supporting files directly onto the relevant SafetyChain record, eliminating the manual download-from-source and re-upload-to-SafetyChain step that quality, operations, and admin users handle today.

• Records arrive in SafetyChain with their supporting documentation already attached, so reviewers see the full picture at the point of review, disposition, or audit.

• Field-level placement preserves the structured context within a record, rather than dropping every file at the record level for someone else to sort out.

• Customer-built and third-party label verification applications can land captured images on a SafetyChain record, putting verification activity into the same record history as other quality checks.

• Customers already using Inbound APIs for record or task creation can reuse the same gateway, authentication, and integration patterns to attach supporting files, reducing the integration learning curve.

• Programmatic attachment preserves the source system and timing of each file, supporting traceability for enterprise audit and compliance.

Availability

Available with the 26A.1 release. Included with the Advanced package and available as an add-on for customers on the Essential package. Documentation is published in the SafetyChain Developer Hub alongside the rest of the Inbound APIs.