Skip to main content
Offload lets your product hand off messy, multi-step human follow-up to an API. You create a case with a goal, the person to contact, and the shape of the result you want back. Offload handles the outreach, follow-ups, reply analysis, and final webhook delivery.

​
What you can automate

Offload is a good fit when your backend knows the desired outcome but does not want to manage an inbox, reminder cadence, or thread parsing.

Collect documents

W-9s, vendor agreements, signed forms, or any paperwork that takes a few follow-ups.

Confirm details

Appointment times, logistics, account information, invoice updates, or missing onboarding data.

Pause for human input

If the workflow needs a business decision, Offload pauses and asks your app for more context.

Receive structured results

When the case is done, your system gets typed JSON instead of raw email text.

​
Core flow

1

Create a case

Call POST /cases with the goal, counterparty, sender persona, and optional resultSchema.
2

Let Offload run the thread

Offload sends the initial outreach, waits for replies, follows up on a schedule, and evaluates each response.
3

Handle webhook events

Your app receives case.completed, case.failed, or case.input_needed as the workflow progresses.
4

Resume if input is needed

When Offload pauses, call POST /cases/{id}/input with the inputRequestId and the missing context.

​
Start with these pages

Quickstart

Make your first API call and wire up webhook handling.

Case lifecycle

Understand statuses, retries, and when a case becomes terminal.

Result schema

Learn how to shape the JSON payload you want back.

Webhook events

See the exact event payloads your backend should expect.

​
Product notes

  • Current public workflows are email-first. Use channel: "EMAIL" in production requests.
  • API authentication uses the x-api-key header on client-facing routes.
  • The current deployed API base URL in this workspace is https://2dr03s75sl.execute-api.us-west-2.amazonaws.com.