cURL
Files
Upload file
POST
cURL
Field support per integration
DATEV Unternehmen Online
DATEV Unternehmen Online
If you’re not using the Interactive Authentication Flow, make sure the query parameter
companyId is accurately populated with the appropriate company ID. You can obtain this value by using the GET Companies endpoint available under the Authentication section.File
required
The name of the uploaded file must include the file extension, for example
invoice.pdf.The file name must not exceed 255 characters in length.
string
The
documentId field can be used to uniquely identify a document. If provided, it must be a valid GUID.string
required
The
documentType field must match one of the document types returned by the GET Document Types endpoint.string
DATEV Rechnungswesen
DATEV Rechnungswesen
If you’re not using the Interactive Authentication Flow, make sure the query parameter
companyId is accurately populated with the appropriate company ID. You can obtain this value by using the GET Companies endpoint available under the Authentication section.File
required
The name of the uploaded file must include the file extension, for example
invoice.pdf.The file name must not exceed 255 characters in length.
string
required
string
The
documentId field can be used to uniquely identify a document. If provided, it must be a valid GUID.string
required
The
documentType field must match one of the document types returned by the GET Document Types endpoint.string
required
The
integrationSource field should be set to the name of your application integrating with DATEV.string
Exact Online
Exact Online
If you’re not using the Interactive Authentication Flow, make sure the query parameter
companyId is correctly populated.
You can obtain this value by using the GET Companies endpoint available under the Authentication section.File
required
The file name must not exceed 255 characters in length.
string
The
contactId field is required for the INVOICE document type.string
required
Available options:
BILL, INVOICEQuery Parameters
Body
multipart/form-data
Example:
"Rechnungseingang"
Example:
"287a382-s35e624e5-fb9e-483"
Example:
"2021-01-01T00:00:00Z"
Example:
"b5e624e5-fb9e-4836-a443-87a3820f5b48"
Example:
"Third party app"
Example:
"Invoice 02-03-2023"
Example:
"771cb8f9-c0e9-4010-bf85-6675af290e37"
Last modified on July 9, 2026