Skip to main content

File and API integrations

Collect exported files with Seal Edge, or set up connections with Seal’s API and Scripts.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

What these systems hold.

These are the general routes for a system without its own connection: files exported to a folder, Seal’s REST API, and Scripts that run in Seal.

EU GMP Annex 11 asks that computerised systems exchanging data electronically include built-in checks for the correct and secure entry and processing of data (Annex 11, 5). Each route needs a defined format, a check that rejects what does not match, and a record of what arrived.

What Seal reads and writes back.

Seal Edge collects exported files from a site computer or network share, and an upload Script decides which records each file creates; the software that exported the file stays the source of truth. Through the REST API, another system reads and writes records in Seal. Scripts are versioned Python, edited in a change set, tested and published like other Seal records, and can call an external service after an event or on a schedule.

Seal
  1. A site computer or network shareSource of truth

    Reads Exported results, mapped by a Script

  2. Another system or applicationSource of truth agreed when scoped

    Reads Records another system writes through the API

    Writes back Records another system reads through the API

  3. An external serviceSource of truth agreed when scoped

    Reads Responses from the services a Script calls

    Writes back Calls to an external service, after an event or on a schedule

3 connections

Blueprints that use these records.

Start with one source.

Tell us what Neil needs to do and where the records live. We’ll scope the connection with your team.

Book a demo