Create a new silo entry with the given UUID.
data
property containing the GOBL JSON of either a pre-built Envelope or a partial document like an Invoice or Party.
The key
property can be used to ensure idempotency, preventing the creation of duplicate entries with the same key within the workspace.
A 409 Conflict
response will be provided if either the entry ID or key have been used in an existing document.
folder
field in the request.
If there are any validation issues with the uploaded data, the service will respond with an error message including a key
and message
. Additionally, the fields
property may include a nested structure to help identify the specific property with a validation fault.
previous_id
field. This allows you to provide patch data instead of a full new document by setting the patch type in the content_type
field to one of the following:
application/json-patch+json
- for JSON Patch (RFC 6902)application/merge-patch+json
- for JSON Merge Patch (RFC 7396)previous_id
field can be used to create corrective documents by including corrective option data in the correct
field. For more details, refer to the GOBL documentation on correction options.Use the Bearer
scheme with a valid JWT token to authenticate requests. Example: Authorization: Bearer <token>
UUID of the silo entry to create.
"347c5b04-cde2-11ed-afa1-0242ac120002"
OK
The response is of type object
.