Password-required files
Use the documented password flow when the PDF needs a password before processing can continue.
For developers
Build around the human decision.
Use the Fulla REST API to bring PDF intake and approved statement output into your application, while keeping the reviewer’s decision visible in the data flow.
System ownership
Decide what your system owns.
Keep a person's review between the extracted draft and the data your application receives.
- 01
Your intake
Collect authorized PDFs and associate them with the right workspace.
- 02
Fulla draft
Process the statement and prepare rows with source references.
- 03
Your reviewer
Inspect the draft, save corrections and approve the checked revision.
- 04
Approved output
Retrieve approved JSON or create a CSV or XLSX export.
- 05
Your application
Validate mapping, import the data and retain authorized records.
Illustrative system boundary, not a running integration.
One state does not imply the next
Model extraction and approval as separate states.
An upload does not immediately produce final data. The API exposes processing status and a result endpoint that returns the latest saved review revision without requiring approval. Inspect and correct those rows before using approved conversion for the final output.
Make review a visible step in your application or direct the reviewer to the Fulla workspace. Review writes use a base revision, and approval names the exact revision checked. Handle a revision conflict by inspecting the current state instead of silently repeating an obsolete approval.
Processing
Wait for the draft to become available.
Ready for review
A person checks the draft against its source.
Approved
Retrieve output for the exact revision that was approved.
Expired
Content access has ended. A new upload starts a new content lifetime.
Plan for the edges
Design the queue around real limits.
The documented upload accepts one to ten PDFs, with a 50 MiB per-file limit and a 100 MiB total request limit. Each PDF is limited to 250 pages. Workspace keys are rate-limited to 60 requests per minute; respect Retry-After when a request receives 429.
Statements and their derived content are deleted 24 hours after the upload starts. Use the reported expiry when scheduling review and retrieval. An expired source cannot be kept alive by repeated status calls or export requests.
Retries and rate limits
Respect Retry-After on a 429 response. Do not turn a failed or stale request into an assumed success.
The download deadline
Schedule review and retrieval against the reported expiry. Repeated requests do not extend content access.
Shared responsibility
Validate the downstream mapping.
Approved JSON returns inline from conversion. CSV and XLSX conversion produce an export with status and download URLs. Decide which output your consumer needs, and validate account, period, amount direction and row counts before the data enters a downstream process.
The API is a statement-processing interface, not a native accounting connector. Any external posting or synchronization belongs to the application you build, with its own authorization and validation.
Fulla handles
- PDF extraction and draft preparation
- Source-linked review
- Output from approved revisions
You decide
- Who reviews and approves
- Downstream mapping and validation
- Your authorized records and retention