Edit File
Edit and manipulate PDF documents by detecting and filling form fields. This is a synchronous endpoint that will wait for the edit operation to complete (up to 5 minutes) before returning results. For longer operations, use the Edit File Async endpoint.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Headers
API version to use for the request. If you do not specify a version, you will either receive a 400 Bad Request or be set to a previous legacy version. See API Versioning for more details.
Request
A file object containing either a URL or a fileId. Mutually exclusive with templateId — exactly one of file or templateId must be provided.
The ID of a saved edit template to run against. Mutually exclusive with file — exactly one of file or templateId must be provided.
The template's saved file is used as the input, and its saved config (schema, instructions, engine version, and advanced options) is used to fill in any values not set on this request's config. Values set on the request's config always take precedence over the template's.
Example: "edt_xK9mLPqRtN3vS8wF5hB2cQ"
Configuration for the edit operation. Field values should be specified using extend_edit:value on each field in the schema.
Response
The type of object. Will always be "edit_run".
A unique identifier for the edit run. Will always start with "edit_run_"
Example: "edit_run_xK9mLPqRtN3vS8wF5hB2cQ"
The extracted/detected field values from the edited document.

