A first look at the Parsebay webhook API

If documents arrive somewhere automatically, like a storage bucket, an email inbox, or a scanner folder, you shouldn't have to upload them by hand. That's the idea behind the webhook API we're planning: Parsebay becomes a step in a pipeline you already run.

The shape of it

You'll point Parsebay at where your files arrive and tell it where to send results. When a new document lands, extraction will run with your saved schema, and a JSON payload with the extracted rows gets POSTed to your endpoint.

What setup will look like

1. In the app, save the header columns you want as a schema (the "Save these columns" button in the extract dialog — this part works today).
2. Create an endpoint on your side that accepts a JSON POST.
3. Tell us your source and endpoint URLs, and we enable the webhook on your account. We expect this to be part of the Business plan and up.

From then on it's hands-off: files go in, JSON comes out. The same rows will also appear in your sheet, so you can always review what was sent.

This isn't live yet. If it would fit your pipeline, write to us and tell us where your documents come from — early conversations are shaping what we build first.

Questions? Write to us — we answer every message.