Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.paubox.com/llms.txt

Use this file to discover all available pages before exploring further.

The Paubox Forms API lets you build, host, and process HIPAA compliant forms (patient intake, consent, surveys, waivers) directly inside your application. Submissions are stored on Paubox’s HITRUST certified infrastructure and visible in your Paubox Forms account. The Forms API is part of Paubox Forms, Paubox’s HIPAA compliant intake form product.

What you can build with it

Healthcare teams use the Paubox Forms API to:
  • Embed patient intake forms inside a portal or app and process responses without storing PHI on their own systems
  • Collect signed consent forms tied to appointments, onboarding, or treatment plans
  • Accept form responses programmatically, including file attachments, and route them into EHRs, CRMs, or other downstream systems
  • Distribute screeners and surveys and pull aggregated results through the API

Available endpoints

MethodEndpointPurpose
GET/public/form_data/{form_id}Retrieve a form’s full definition (HTML, JSON schema, CSS) for rendering to a respondent
POST/api/forms/{form_id}/submissionsSubmit a form response, including text fields and file attachments
Base URL: https://apx.paubox.com/forms See the full reference: Get form metadata and Submit a form response.

How it handles HIPAA and security

The Paubox Forms API runs on the same HIPAA compliant infrastructure as the rest of the Paubox platform. Form definitions and submissions are stored in Paubox’s secure environment. Paubox signs a business associate agreement (BAA) with every customer. Both endpoints documented here are public. They’re called by respondents loading and submitting forms from end user devices, where authentication wouldn’t be feasible. The form’s UUID acts as access control:
  • Form IDs are UUIDs, which makes them difficult to enumerate
  • Submissions are capped at 250 MB total, including form fields and any file attachments
Paubox Forms is included with paid Paubox accounts, including Paubox Email Suite.

Authentication

EndpointAuthentication
GET /public/form_data/{form_id}Public, no API key required
POST /api/forms/{form_id}/submissionsPublic, no API key required
Form management (create, update, delete)Paubox Forms API key
The two endpoints documented here are intentionally public. Respondents fill out forms from end user devices, so authentication happens at the form definition layer rather than the request layer.

Get started

  1. Create a form in the Paubox Forms app.
  2. Copy the form’s UUID. This is the form_id you’ll pass to both endpoints.
  3. Use the endpoints below to render the form and accept submissions.

Get form metadata

Retrieve the form’s HTML, JSON schema, and CSS for rendering to a respondent.

Submit a form response

Post field values and file attachments to the submissions endpoint.

FAQs

Yes. Form definitions and submissions are stored on Paubox’s HITRUST certified, HIPAA compliant infrastructure. All data is encrypted in transit and at rest, and Paubox signs a business associate agreement (BAA) with every customer.
Both endpoints are called by respondents loading and submitting forms from end user devices, where authentication wouldn’t be feasible. The form’s UUID acts as access control: each form has a unique UUID generated by Paubox when you create the form.
Yes. Forms can be marked as signable. The signable and signature_confirmation_label fields on the form metadata indicate signature behavior, and a signature confirmation is recorded with the submission.
Yes. The attachments array on POST /api/forms/{form_id}/submissions accepts file objects with a name and base64 encoded content. The maximum total submission size is 250 MB.
Submissions are stored in your Paubox Forms account and visible in the app. You can configure email notifications to designated recipients on each submission, or pull submission data programmatically through the authenticated Forms API.
Both endpoints return a 404 Not Found response.
The form_data object on a submission accepts key-value pairs where keys match the field names defined in the form’s schema. Retrieve the schema by calling GET /public/form_data/{form_id} and reading the form_json field.
Test against any form in your Paubox Forms account. Deactivate or delete the form when you’re done testing to keep submission counts clean.