An API. A Python SDK. A command line. Scripts. Seal for developers. Your own tools, on the record.
The v3 API, in beta, with a Python SDK and the seal command. Scripts that run in Seal, apps on an entity's page, and Neil set up from code.

- 1import seal
- 2from datetime import date, timedelta
- 3
- 4soon = date.today() + timedelta(days=14)
- 5lot = seal.entities.list(
- 6 where={"kind": "template", "title": "Lot"}
- 7).one()
- 8lots = seal.entities.list(
- 9 system="materials",
- 10 where={
- 11 "template": lot.id,
- 12 "fields": {
- 13 "Expiry": {"lt": soon.isoformat()},
- 14 "Quarantined": False,
- 15 },
- 16 },
- 17)
- 18print(f"{lots.total} lots expire by {soon}")
- 19
- 20with seal.changesets.create(name="Expiry sweep"):
- 21 for row in lots:
- 22 quarantined = {"Quarantined": {"value": True}}
- 23 seal.entities.update(row.id, fields=quarantined)
- 24 print("Staged", row.title)
Run 14
As T. Nakamura- Run 14, by T. NakamuraRun
- 3 lots expire by 2026-11-30print
- Staged RM-2041print
- Staged RM-2047print
- Staged RM-2052print
- Expiry sweep, 3 entities, awaiting publicationChangeset
- Finished, 1.9 sRun
Staged, then published by a person
Today an integration holds an admin login and writes straight into the database. Here it holds a key, and stages work a person publishes.
| Compared on | Today | Seal |
|---|---|---|
| A key | A shared admin login | Its systems, the lowest access, no signature |
| A write | Straight into the database | Staged in a changeset a person publishes |
| A script | On someone's laptop | In Seal, as the person who runs it |
| A dashboard | An export to a spreadsheet | An app on the entity's page |
| A coding agent | Guessing from a wiki | Given the guide Neil works from |
A key signs nothing
A key is granted its systems and the lowest access that does the job. It can't publish, sign, create a key or make an admin.
- SystemsSpecific systems
- MaterialsMember
- QualityMember
- Changeset publishingOff
- Sign-off stepsOff
- Creates keys or adminsNever
Today
Mon 16 Nov- Read 212 lots in MaterialsRead
- Staged 12 results on RM-2052Staged
- LIMS results, 16 Nov, awaiting publicationChangeset
- Published by L. HaddadPerson
Your own app, on the entity's page
An app is an entity: HTML and TypeScript, versioned, published like any change, and run on the page with the person's own access.
| Lot | Material | Expiry | Days |
|---|---|---|---|
| RM-2041 | Polysorbate 80 | Thu 19 Nov | 3 |
| RM-2047 | Sucrose | Mon 23 Nov | 7 |
| RM-2052 | Histidine | Sat 28 Nov | 12 |
| RM-2058 | WFI, drum | Wed 9 Dec | 23 |
The app
3 files- index.html1.2 kB
- app.ts3.8 kB
- styles.css0.9 kB
- Modebun
- Readswindow.SEAL_CONTEXT
- Published by L. Haddad, Thu 12 NovActive
- Board by material, T. NakamuraChangeset
Neil, set up from code
A persona, a connection and a routine, from the SDK. A person authorises the connection, and the routine is set up as a person.

- 1import seal
- 2
- 3seal.personas.create(
- 4 "QA",
- 5 "Review deviations and CAPAs. Say what "
- 6 "evidence is missing and who needs to act.",
- 7)
- 8gmail = seal.connections.connect("gmail")
- 9print(gmail["authorizationUrl"]) # open within 15 min
- 10
- 11seal.routines.create(
- 12 name="overdue-deviations",
- 13 description="Weekday check of overdue deviations.",
- 14 trigger={
- 15 "kind": "schedule",
- 16 "schedule": {
- 17 "kind": "cron",
- 18 "expression": "0 8 * * 1-5",
- 19 "time_zone": "Europe/London",
- 20 },
- 21 },
- 22 action={
- 23 "kind": "neil_prompt",
- 24 "prompt": "List deviations past their due date "
- 25 "and draft a short reminder to each owner.",
- 26 "persona": "QA",
- 27 "connections": [gmail["id"]],
- 28 },
- 29)
The routine
Active- RunsWeekdays at 08:00, Europe/London
- PersonaQA
- ConnectionGmail, authorised by L. Haddad
- Set up byL. Haddad, Fri 13 Nov
- 4 deviations overdue, 4 reminders draftedRun
- Drafts wait for L. Haddad to sendGmail
Your coding agent, signed in as you
seal login gives the command line a token of your own, and seal skill install gives your agent the guide Neil works from.
- $ seal login https://platform.seal.run/o/blubber
- Opening Settings, API keys, in your browser. Select Allow.
- Signed in as T. Nakamura. Saved in ~/.seal/credentials
- $ seal whoami
- T. Nakamura, blubber
- $ seal skill install
- ~/.seal/skills/seal-guide/
- › Which lots in Materials expire this month and
- are not quarantined? Stage them for QA.
Questions about Seal for developers.
Is the API ready to build on?
The v3 API is in beta: a route or an SDK call may still change before general availability. Customers build on it today. Tell support@seal.run before a business-critical integration depends on it, so a change reaches you first.
Can a script or a key sign anything?
No. An API key can't give a human electronic signature, and nothing it does is one. Where Seal has turned sign-off steps on for a key, each step it gives is recorded as confirmed by the key, by name, never as a signature. A Script runs as the person who runs it, and signs nothing on their behalf.
What does a write do?
It is staged. A key or a script opens a changeset, names it, and puts its writes in it; the changeset goes through the same review, Checks and publication as one a person makes. With Changeset publishing off, which is the default, a person publishes it in Seal.
How do we get the SDK?
From Seal, matched to your deployment: the Python SDK and the seal command are one package, for Python 3.10 or later, and it is not on PyPI yet. The interactive reference is at /api/docs/v3 on your own Seal, with its OpenAPI description beside it, once you are signed in.
Is there a TypeScript SDK?
Inside a custom app, yes: an app built in bun mode imports Seal's TypeScript SDK and queries the record from the entity's page. Elsewhere, TypeScript and every other language call the HTTP API, where every route is under /api/v3, errors have one shape and pages have a cursor.
Where does a Script run?
In Seal's own sandboxed runtime, as the person who runs it, with their access and the SDK already signed in. It can run on its own, from an entity's page, or on a trigger such as a step being rejected, and its log is streamed and kept with the run.
Which region does it call?
Your own. The API root is https://platform.seal.run/api in the EU, https://us.platform.seal.run/api in the US and https://au.platform.seal.run/api in Australia, and the CLI saves the right one when you sign in.
Can we test against a copy first?
Yes. Where your organisation has isolated environments, a key can be bound to one, and then works only inside it, never against production. It expires after 90 days and is revoked when the environment is archived.
Seal Edge or the API?
Seal Edge is for equipment, instruments and your historian: a computer on your network reads them, and nothing is written by you. The API is for code you write, against the record, from wherever it runs. A plant with both has its readings and its tools on the same record.
Can our coding agent use it?
Yes. seal login gives the command line on your computer a token of your own, and seal skill install puts Seal's API reference and guides where an agent on that computer reads them. It then reads and stages work as you, and a person publishes what it stages.


See your process in Seal.
Working 48 hours after we agree its scope: tested, with evidence your QA approves.