Files. Connections. Applications.

File transfers.
Less friction.

Build a better handoff between your apps. Practical API patterns for uploading, verifying, and delivering files without turning every transfer into a special case.

Explore the API Follow a transfer →

HTTP-native · JSON-first · Language-independent

TRANSFER WORKFLOW / EXAMPLE01
# One handoff, a predictable response.
POST /v1/transfers
Content-Type: application/json

{
  "filename": "project-assets.zip",
  "content_type": "application/zip",
  "expires_in": 3600
}
ZIP
project-assets.zipupload → verify → deliver
SHA-256 INTEGRITY CHECKVERIFIED
Standard HTTPSResumable by designScoped accessExplicit delivery events
01 / The building blocks

Small pieces. Reliable transfers.

Keep your application logic focused. Give file movement its own clear, observable lifecycle.

[01] UPLOAD

Pick up where you left off.

Use upload sessions and recorded offsets to resume an interrupted transfer. Retry a chunk instead of sending the whole file again.

[02] VERIFY

Know what arrived.

Compare content length and SHA-256 checksums before making a file available. A completed request and a verified file are different things.

[03] DELIVER

Make access intentional.

Issue short-lived download URLs with narrow permissions. Keep permanent credentials out of browsers, shared links, and application logs.

02 / API notebook

A familiar interface.
A clear contract.

Create a transfer, upload the bytes, then check its state. Use the same sequence from a command-line tool, a backend job, or an integration worker.

REFERENCE EXAMPLES · v1

The snippets describe an integration pattern. Replace the example base URL and token with those of your transfer service.

Example credentials only. Keep service tokens on your backend.


03 / From request to receipt
Every file has a journey.
01 — INITIATE
Create a session
Describe the file and request a bounded upload window.
02 — TRANSFER
Send the bytes
Stream content, track offsets, and retry safely.
03 — CONFIRM
Verify the result
Check size and checksum before exposing the file.
04 — HAND OFF
Notify your application
Publish a completion event and issue scoped access.


Good connections start with boundaries.
Limit token scope. Set an expiration. Verify webhook signatures. Use idempotency keys for retries, and never treat a public download URL as permanent storage.
Read the examples ↗


When should an upload be retried?
Retry temporary network failures and eligible server errors with exponential backoff. Use a session ID and a stable idempotency key to prevent duplicate work. A validation error needs a corrected request.
How do you keep delivery observable?
Give each transfer a unique ID. Record state changes rather than file contents or access tokens. A small event history makes troubleshooting much easier than guessing from a connection timeout.