DoConure
DoConure · Integrator guide
Turn your data into a finished PDF, using a document model you control.
How it works
You send structured data; the service merges it into a template you uploaded and returns a PDF. The template is an ordinary Word, Excel or HTML file with placeholders where the variable values go.
your system (Salesforce, Odoo, a script…)
│
│ JSON: { "customer": { "name": "Acme Srl" }, … }
▼
POST /api/v1/compose/documents/generate
│
▼
PDFThe service knows nothing about Salesforce or Odoo, deliberately: any system integrates the same way.
| Template format | Use it for |
|---|---|
| Word (.docx) | Letters, contracts, forms, reports. The format anyone can edit. |
| HTML | Precise control over layout, and speed: roughly 7× faster than the others. |
| Excel (.xlsx) | Tabular reports with many rows. |
| Term | Meaning |
|---|---|
| Tenant | One customer. Owns its templates and API keys, and cannot see anyone else's. |
| Template | The document model, identified by an id such as invoice-standard-8bc99b. |
| Version | Every upload creates one. Several can be active at once — see Versions. |
| API key | The tenant's credential, sent on every request. |
What you can count on
What developers complain about in document and signature APIs, and what this one does instead.
- No approval to go live. An account is active as soon as you sign up; production needs credit, not a review.
- Free tests with the real call.
"isTest": trueinsettingsspends no credit: same address, same key. - Every call says what it cost, in
output.credits.itemsor theX-Credits-Usedheader. Out of credit, the call is refused with a code (Errors), never moved to a pricier plan; a mail warns you first. - Errors you can read. Every outcome has a stable code and number; a template's missing fields are listed by name.
- See what happened, and run it again. The console shows each document's payload with a curl command to repeat it, and each webhook's answer, next try and a Send again button; API errors lists what your keys were refused, by code, with a link to each code's row in Errors.
- The PDF looks like your Word file. A template's page says which Word fonts are missing and what replaces them (fonts).
Every page
Grouped the way the sidebar groups them — a fast path first, one recipe per task, then everything in full.
Quick Start
How To
- How do I compose and send for signature in one call?
- How do I ask for signatures in a specific order?
- How do I keep someone informed without asking them to sign?
- How do I choose how a signer proves it's them?
- How do I remind a signer, or resend a lost link?
- How do I know when something finished?
- How do I make our callbacks authenticate at my system?
- How do I put my brand on what signers see?
- How do I check a signed file later?
Detailed reference
- Generating a document
- Validate before you send
- Files, charts and download links
- Bulk composition and signing
- Versions
- Compose and sign, in one call
- Signing on its own
- Cc and bcc on an envelope
- Where the signature goes on the page
- What the signer sees
- Signature levels: SES, AES, QES
- Qualified seal and qualified timestamp
- Managing templates from a script
- Tracing a call, and watching your usage
- Tracking, consent and the ad platforms
- Outcomes and error codes
- Missing and extra fields
- Writing a template
- Lists and repeating rows
- Conditional parts
- Making a value fit the space you left for it
- Common mistakes
- Fonts in your Word template
- What each format can do
- Salesforce (Apex)
- Python
- Signing in, and getting back in
- The audit trail
- Credit, prices and VAT
- Versions of the API
- Current limits
What changed in each version is on the release notes. A problem or an idea: signed-in customers can report it from the console, and anyone can write to us from the contact page, including a complaint.