Convert a source document to editable Markdown

POST/v1/knowledge/parse

Parses one supported document through the deployment's document-conversion provider. The response is staging data only; callers explicitly create a Knowledge document and should retain the original source attachment in its provenance.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
None.
Query parameters
None.

Body schema

Content type: multipart/form-data · Required

FieldTypeRequiredDescription
filestringYesPDF, Word, spreadsheet, presentation, OpenDocument, EPUB, RTF, CSV, or HTML file (maximum 50 MB).

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Editable Markdown and conversion provenanceapplication/json
FieldTypeRequiredDescription
objectknowledge.document_parseYes
markdownstringYes
providerfirecrawlYes
metadataobjectYesFree-form metadata object.
conversionobjectYes
conversion.providerfirecrawlYes
conversion.formatmarkdownYes
conversion.convertedAtstringYes
conversion.zeroDataRetentionbooleanYes
conversion.pdfModeautoYes
conversion.pageMarkersbooleanYes
conversion.creditsUsednumberYes
400Missing or invalid upload
None.
413File exceeds the 50 MB conversion limit
None.
415Unsupported document type
None.
422The document could not produce editable Markdown
None.
429Document-conversion provider rate limited
None.
503Document conversion is not configured
None.
Convert a source document to editable Markdown
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow