Skip to main content
POST
Create an Abstract
Create a title abstract in your workspace from a template. Send the request as multipart/form-data. Document files are optional — include files[] to attach them now, or omit them and add documents later. This single endpoint supports a one-click push from another system: send the custom fields to create the abstract, and attach documents in the same call or whenever they’re ready.

Request

integer
The template to create the abstract under. Discover ids via GET /abstract-templates. Omit to use your workspace’s default template.
object
A map of custom field key → value. Discover available keys via GET /abstract-templates. Array values (e.g. multi-select) are accepted. Unknown keys are ignored. Send as a JSON-encoded string in the multipart form.
string
Property street address.
string
Property city.
string
Property county.
string
Property state.
string
Tax map / parcel identifier.
file[]
Optional. One or more document files to attach to the abstract. Use repeated files[] parts for multiple uploads. Omit to create the abstract with no documents and upload them later.

Example: one-click push (no documents yet)

This is the typical create-now, upload-later flow. The abstract is created with its custom fields; documents are added later.

Example: create with documents attached

If the documents are ready, attach them in the same request with files[].
string
The obfuscated abstract id. Use this as the opaque identifier for the abstract.
string
The abstract’s status name, or null. A status is set only when the chosen template has statuses enabled, in which case the template’s default status is applied.
array
The documents attached to the abstract. Empty when none were sent. Files are processed asynchronously; is_processing is true until processing finishes.
array
Per-file failures, at the top level alongside data. Empty when every file succeeded (or none were sent). See Partial failures.

Supported file types

PDF, DOCX, DOC, PPTX, PPT, TXT, XLSX, XLS, PNG, JPG, JPEG, TIFF, GIF, BMP, WEBP.

Partial failures

Files are validated individually. The abstract is always created as long as its fields are valid. If a file fails (e.g. a PDF over the page limit), the abstract is still created, the good files are attached, and the failed file’s reason appears in the top-level errors array:
Limits: up to 100 MB per file and 500 pages per PDF. Image-heavy PDFs have tighter limits (50 MB / 300 pages).