Entries
Create an entry (non-idempotent)
Create a new silo entry non-idempotently without an explicit UUID. Only recommended for testing purposes, production environments should use the PUT method.
POST
This is a non-idempotent endpoint. It must be used for developing and testing only. In production, please use the idempotent version. More info here.
The data
field may contain either GOBL Envelope or Object, and
will be validated before being persisted.
New entries may also be created based on a previous entry using the
previous_id
field. Using a previous entry allows you to provide patch
data instead of a new full document by setting the patch type in the
content_type
field to either:
application/json-patch+json
- for JSON Patch (RFC 6902)application/merge-patch+json
- for JSON Merge Patch (RFC 7396)
The previous_id
field can also be used to make corrective documents
by adding the corrective option data in the correct
field. For more
details on this, see the GOBL documentation
for correction options.
Body
application/json
Response
200 - application/json
OK
The response is of type object
.