CRUD on entities

CRUD operations are supported on all Uniconta entities and can be executed using HTTP requests.

The format used by the REST API for both request and response bodies (where not empty) is JSON. This means that all entities are represented as JSON objects, having a structure identical to that of the original Uniconta C# entity classes (i.e. for every class attribute/property in C# there is a corresponding key-value pair in JSON, where the JSON key is the attribute/property field's name in C# and the corresponding JSON value is the field's value).

CRUD operations are supported on all Uniconta entities and can be executed using HTTPS requests. The

type of the operation is specified by the HTTP method used for the request. The table below shows the mapping between the CRUD operations to the HTTPS methods supported.

All requests that have a body can also specify a value for the Content-Type header. The legal values for this header are application/json, text/plain or application/pdf. While application/json and text/plain can be used interchangeably or even ignored, the value application/pdf must be used when sending binary data (more information regarding this case in the Update section)