Getting started

You need client_id, client_secret, and a Docmind workspace and/or Docbooks partner access. Email support@docpier.com if you do not have them. Keep the secret off the browser and out of git.

Pick a first capability: extract (Docmind, when you need typed data in your product) or book (Docbooks). Booking analyses the document itself — Combine analysis and booking.

1. Token

   POST client credentials. Cache access_token; it expires in about 300 seconds. 401 and 403 have an empty body.

   Docmind

   curl -X POST https://auth-stage.docpier.com/realms/idp/protocol/openid-connect/token \
     -H "Content-Type: application/x-www-form-urlencoded" \
     -d "grant_type=client_credentials" \
     -d "client_id=$CLIENT_ID" \
     -d "client_secret=$CLIENT_SECRET" \
     -d "scope=docmind.capture"

   Docbooks

   curl -X POST 'https://auth-stage.docpier.com/realms/idp/protocol/openid-connect/token' \
     -H 'Content-Type: application/x-www-form-urlencoded' \
     -d 'grant_type=client_credentials' \
     -d 'client_id=$CLIENT_ID' \
     -d 'client_secret=$CLIENT_SECRET' \
     -d 'scope=docbooks.bookings docmind.capture'

   Scopes and hosts: Authentication.

2. First write

   Neither call waits for processing. You get 202 and an id.

   Extract a document

   Capture: multipart POST → documentId → typed JSON.

   Docmind

   Propose a booking

   Booking: multipart POST → bookingJobId → booking report.

   Docbooks
3. Webhook, then GET

   Acknowledge with 2xx. Dedupe on webhookId. Route on product, then event. Do not poll.