Skip to main content

Integration guideSeal API and Scripts

Google Cloud Storage

Bring files from cloud storage into Seal for processing.

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

Google Cloud Storage and SealSeal API and Scripts

Seal reads
Files from the agreed buckets
Writes back
Seal exports, archived to the agreed buckets
Source of truth
Agreed when scoped
Set up
Scoped with your team
Neil › Transfer reconciliation
draft

Check which released records reached the archive this month.

Neil

  • Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
Reads
Files from the agreed buckets
Returns
  • Records sent, destinations and failed transfers
  • Missing or unmatched information
  • Next steps for your team to review
Illustrative work with Google Cloud Storage: a request to Neil, the source it reads and the draft it returns for your review.

1What’s connected.

Bring files from Google Cloud Storage buckets into Seal, or archive Seal exports there, through a connection set up with Seal’s API or Scripts. Agree the buckets, service-account permissions and handling of changed or duplicate files.

Connection setup and permissions

Use Seal’s APIs or scripting engine for a connection tailored to your process. Agree the data mapping, access and direction of transfer before implementation.

2Read files from, or archive Seal exports to, Cloud Storage.

Route

The JSON API’s objects.insert stores an object and replaces any live object with the same name.⁠¹

Record identity

An object is identified by its name together with a generation number the service assigns, so one name read twice can be two different files.⁠² Google recommends CRC32C checksums. MD5 validation works for single uploads but not composite ones, and a mismatch rejects the write with 400.⁠³ Object metadata carries a CRC32C checksum, and an MD5 hash except on composite objects and objects encrypted with customer-managed keys.⁠⁴

Revisions

With Object Versioning, replacing or deleting a live object keeps a noncurrent version under the same name with its own generation. Google recommends soft delete over versioning to protect against deletions.⁠⁵ A bucket retention policy blocks deleting or replacing objects until they are older than the retention period, and locking that policy cannot be undone.⁠⁶

When it fails

An archive run would replace an earlier export
With ifGenerationMatch=0, a write proceeds only when no live object of that name exists, and otherwise fails with 412.⁠⁷ Archive with that precondition, and treat a 412 as an export the bucket already holds.
A retried upload
Some requests are safe to retry only when they carry particular arguments, and an object insert with ifGenerationMatch is one of them.⁠⁸ Retry archive uploads only with the precondition set.

Check one record

Archive one Seal export to a test bucket and read back its generation, CRC32C and size. Then change a file the connection reads in the bucket, and confirm the connection treats the new generation as a changed file, as agreed.

3Start with the job.

Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.

Discuss this connection →

4Before it goes live.

Access and any write-back

Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.

Verification and release

Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.

Read the assurance detail →

References

  1. 1Cloud Storage JSON API: objects.insert.
  2. 2Google Cloud: about objects.
  3. 3Google Cloud: hashes and ETags.
  4. 4Cloud Storage JSON API: object resource.
  5. 5Google Cloud: Object Versioning.
  6. 6Google Cloud: Bucket Lock.
  7. 7Google Cloud: request preconditions.
  8. 8Google Cloud: retry strategy.