Create a new entitlement registration line
Changed onCreates a new entitlement registration line with an optional file attachment.
Attachment Rules:
- Whether an attachment is required or not allowed is determined by the entitlement configuration.
- entitlements API can be used to fetch the entitlement configuration, which includes whether an attachment is required or not allowed for a specific entitlement.
- If an attachment is required but not provided, the request will be rejected with a 400 error.
- If an attachment is provided when not configured in entitlement, the document will still be stored
- Supported file types for attachments are PDF, PNG and JPEG. If the provided file is not one of these types, the request will be rejected with a 400 error.
Request
- Base URLhttps://api.maqqie.app (the document declares no server; this is the origin it was published from)
- AuthOAuth 2Client credentialsToken URLhttps://maqqie.app/auth/realms/maqqie/protocol/openid-connect/token
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Request body multipart/form-data
Example request
{
"request": {
"date": "2024-10-30"
}
}Response
Entitlement registration line created successfully
Changes
- breaking
added the new required request property
///// - breaking
added the new required request property
///// - breaking
added the new required request property
///// - breaking
the
////request property type changed from no type toobject - breaking
the response's body type changed from no type to
objectfor status - breaking
the response's body type changed from no type to
objectfor status - info
added the new optional request property
///// - info
added the new optional request property
///// - info
added the new optional request property
///// - info
added the optional property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status
- breaking
- breaking
the response's body type changed from
objectto no type for status - breaking
the response's body type changed from
objectto no type for status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - warning
removed the request property
///// - warning
removed the request property
///// - warning
removed the request property
///// - warning
removed the request property
///// - warning
removed the request property
///// - warning
removed the request property
///// - warning
removed the optional property
from the response with the status - info
the
////request property type was generalized fromobjectto no type
- breaking