Introduction
We are pleased to present you our new REST API. At the begining of this documentation we would like to give you some general informations about this API:
It's based on JSONAPI specification. We hope that following the rules of this specification will make our API easy to understand.
This documentation is generated from swagger file - written in OpenAPI 3.0.2 Specification
This API always accept application/json format at the API input and always return the same format as output.
API output always follows this scheme:
{
"meta": {
"numberOfErrors": NUMBER_OF_ELEMENTS_IN_ERRORS (number),
"numberOfData": NUMBER_OF_ELEMENTS_IN_DATA (number),
"status": HTTP_STATUS (number),
"uniqId": UNIQUE_REQUEST_ID (string)
"someField": SOME_VALUE (string)
},
"data": [],
"errors": [
{
"title": ERROR_TITLE (string),
"message": ERROR_MESSAGE (string),
"code": ERROR_CODE (string),
"meta":{
"parameter": SOME_VALUE (string),
"value": SOME_VALUE (string),
"source": SOME_VALUE (string),
"someField": SOME_VALUE (string)
}
}
]
}
Following rules applies to the above scheme:
meta
element is always presentmeta.numberOfErrors
indicates how many elementserrors
array includesmeta.numberOfData
indicates how many elementsdata
array includesmeta.status
indicates response HTTP statusmeta.uniqId
is used to identify request, if your will have some troubles with your request, please make sure that you sent usmeta.uniqId
valuemeta.someField
may contain additional fieldsdata
array cannot be present witherrors
array if status code is different from HTTP 207 (MULTI-STATUS)errors
array always consists object with fields:title
,message
andcode
.errors.meta
element may be present inside single error object and contain additional information (that can be parsed) about errorerrors.meta.parameter
the parameter that causes the errorerrors.meta.value
the value of this parameter passederrors.meta.source
a link to the entity that caused the error, e.g. externalIderrors.meta.somefield
additional fields that may appear