Developer Platform

Integrate first-mile processing directly: submit documents, retrieve structured data with per-field confidence, and subscribe to events.

The Object Model

A document belongs to a queue, is processed against a model, and carries fields, each with a value, confidence, and provenance. Documents emit events you subscribe to via webhooks. Once you know that shape, the API is predictable before you read the reference.

What a Developer Can Do

• Submit documents and retrieve structured data with per-field confidence and provenance.

• Manage models and queues, subscribe to webhooks, and export audit logs as CSV or JSON.

• Call the redaction endpoint: POST /v2/redaction/document, with a GET to track the redacted output.

Regional and Access Model

Regional endpoints span Singapore, EU, US, and China, with residency enforced at the egress boundary as infrastructure, not a config flag. Access is governed by SSO and RBAC covering document access, search, and model sharing. See Audit Readiness for the trail behind every field.

Where to Go Next

Integrate directly with APIs & SDKs, let an agent call Staple with Agentic Integrations, or read the Developer Documentation.

Proven In Production

A global investment bank integrated via API and SSO across 5+ countries, processing documents in 3 to 6 seconds at 99.6% accuracy after eliminating 800+ document templates.

Read the Docs

Start with the developer documentation, or book a demo.

Related Topics

See Staple process your documents

Book a 30-minute demo with a document processing specialist.

Book a Demo

Not ready yet?

Take your time to decide.

Read the foodpanda case study