Developer Platform

The Developer Platform is Staple for teams that want to integrate first-mile document processing directly, over an API and webhooks, rather than through a screen. You submit documents, retrieve structured data with a per-field confidence score and its provenance, and subscribe to the events that tell your systems when something has happened. The goal is that once you understand the object model, the API behaves the way you would predict before you have read a single page of reference.

The Object Model

Everything in the platform hangs off a small, consistent shape. A document belongs to a queue, is processed against a model, and carries fields, and each field has a value, a confidence score, and a provenance record of where it came from. A model is a natural-language, prompt-driven blueprint for how a document type should be understood, defining what to capture rather than where it sits on the page. Documents move between queues as they are validated and routed, and they emit events at each meaningful state. Learn that shape once and the Connect and Operate API is predictable across every endpoint.

What A Developer Can Do

• Submit documents in any format or language and retrieve structured data with per-field confidence and provenance.

• Create and manage models and queues, so a new document type is an API call rather than a support ticket.

• Subscribe to webhooks for the document lifecycle, and export audit logs as CSV or JSON for offline review.

• Call the redaction endpoint, POST /v2/redaction/document, with a follow-up GET to retrieve the redacted output.

• Pull verified data with its Metastructured Data envelope attached, so the receiving system can verify integrity without contacting Staple.

Event-Driven By Design

You do not have to poll to know a document is ready. A webhook posts JSON to an HTTPS endpoint your team controls the moment a document reaches a state you care about, and a single webhook can listen for one or more events. The lifecycle you can subscribe to covers a document being uploaded, completed, rejected with its reason, deleted, or moved between queues, alongside process signals such as a tax validation failing or a buyer rejecting a submitted document, so an integration learns about a break the moment it happens rather than when someone logs in and notices.

Each webhook is scoped to the queues it should watch, points at an endpoint you own, and carries a delivery-failure alert and a last-triggered record so a missed payload does not go unnoticed. Authenticating outbound webhooks with OAuth 2.0 against your own identity provider is on the near-term roadmap and labeled as such rather than implied. Full request and response schemas live in the developer documentation. Because the payload a webhook pushes is the same structured data the API export returns, an integration can start by pulling on demand and later switch to event-driven delivery without changing how it parses the result.

Regional And Access Model

Regional endpoints span Singapore, the EU, the US, and China, with residency enforced at the egress boundary as infrastructure rather than a configuration flag, so a document tagged for one jurisdiction cannot be routed out of it. Access is governed by SSO and role-based access control covering document access, search, model sharing, and who may create or manage webhooks. Every field carries the trail behind it; see Audit Readiness for how that trail is exposed and exported.

Multi-Tenant When You Need It

If you are embedding Staple inside your own product, the platform is multi-tenant by design. Each of your customers runs as an isolated tenant with its own models, queues, rules, and data scope, kept separate by role-based access control and row-level security. You decide whether to configure models on a customer's behalf through the API or expose Staple's no-code configuration so they define new document types themselves. The embedding path is described in full under For Software Platforms.

What The Developer Platform Does Not Do

Staple gives you verified data, the events around it, and the interfaces to both. It is not a low-level OCR SDK you assemble a pipeline from, and it does not ask you to manage models or infrastructure that the platform already runs for you. You integrate a capability, not a toolkit you have to maintain.

Proven In Production

A global investment bank integrated Staple over the API with SSO across more than five countries, processing documents in 3 to 6 seconds at 99.6% accuracy after eliminating more than 800 document templates it had previously maintained. Across deployments, Staple runs for Fortune 100 companies and global financial institutions in 60 countries at a 100% deployment success rate.

Where To Go Next

• Integrate directly with APIs and SDKs.

• Let an agent call Staple through Agentic Integrations.

• Read the Developer Documentation.

Read The Docs

Start with the developer documentation, or book a demo with the platform team.