id
in POST
requests, but Aidbox API respects id
inside the request body and creates a resource with a specific id
. This decision was made because we didn't find any reasons to ignore it and to make Aidbox API be closer to the SQL INSERT
query. As a result, a new response code 409 Conflict
appeared.201
400
409
422
If-None-Exist
header, Aidbox uses query parameters as in ordinary read
operation. This is done to make all conditional operations to look the same (use search query parameters). create
interaction (Aidbox version of create)200 OK
412 Precondition Failed
error indicating the client's criteria were not selective enoughPOST
HTTP method accepting a resource type via path parameters and the resource as a body of the request. A response to this interaction may be one of the following:201
400
409
422
2xx
) also contains a created resource as a body and additional headers Location
, ETag
, Last-Modified
which contain the full path to a resource (base url, resource type and id of a newly created resource), additionally information about version (vid) and modification time of that resource.4xx
) contains OperationOutcome
resource which describes issues the server faced during the creation of this resource.201
Created201
201
422
Unprocessable entity422
id
and treats it as all other attributes in contrast to FHIR API. Read more about differences here.create
becomes conditional create
and works in the following way (depending on the number of search results): create
interaction200 OK
412 Precondition Failed
error indicating the client's criteria were not selective enough200
OK200
200