OrderAgreement APIs
Operations related to OrderAgreements
The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
With JSON, use the limit
parameter to change the number of returned messages and combine it with offset
to traverse through your available messages.
To get new messages only, use the "Read"
endpoint instead!
Account registration number issued by Qvalia
""
How many messages to return in Array (XML is always one!)
3
Example: 5
Where to start index for using limit/offset listing
0
Example: 0
If you are using the "read" enpoints, make it include previously read messages
false
Example: false
Qvalia unique identifier for the transaction/message
""
The document identifier of teh message, e.g. Invoice number
""
YYYY-MM-DD, e.g. 2024-01-01
""
YYYY-MM-DD, e.g. 2024-01-01
""
YYYY-MM-DD, e.g. 2024-01-01
""
YYYY-MM-DD, e.g. 2024-01-01
""
API key
""
Either "application/json" (default) or "application/xml"
application/json
GET /transaction/{accountRegNo}/orderagreements/incoming HTTP/1.1
Host: api-qa.qvalia.com
Authorization:
Accept: */*
{
"status": "success",
"data": [
{
"{transaction-type}": {},
"integrationId": "text"
}
]
}
The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
Account registration number issued by Qvalia
""
For POST requests, chose to overwrite existing message upon 409 Conflict response
false
Example: false
API key
""
Either "application/json" (default) or "application/xml"
application/json
POST /transaction/{accountRegNo}/orderagreements/incoming HTTP/1.1
Host: api-qa.qvalia.com
Authorization:
Content-Type: application/json
Accept: */*
Content-Length: 20
{
"OrderResponse": {}
}
{
"status": "success",
"data": {
"message": "{transaction-type} 100-1000 sent",
"{transaction-type}_id": "100-1000",
"integrationId": "4725a033-e501-4e2f-afa5-3a5c24eb5e28"
}
}
Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as read
The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
With JSON, use the limit
parameter to change the number of returned messages and combine it with offset
to traverse through your available messages.
Account registration number issued by Qvalia
""
How many messages to return in Array (XML is always one!)
3
Example: 5
Where to start index for using limit/offset listing
0
Example: 0
If you are using the "read" enpoints, make it include previously read messages
false
Example: false
API key
""
Either "application/json" (default) or "application/xml"
application/json
GET /transaction/{accountRegNo}/orderagreements/incoming/readorderagreement HTTP/1.1
Host: api-qa.qvalia.com
Authorization:
Accept: */*
{
"status": "success",
"data": [
{
"{transaction-type}": {},
"integrationId": "text"
}
]
}
The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
With JSON, use the limit
parameter to change the number of returned messages and combine it with offset
to traverse through your available messages.
To get new messages only, use the "Read"
endpoint instead!
Account registration number issued by Qvalia
""
How many messages to return in Array (XML is always one!)
3
Example: 5
Where to start index for using limit/offset listing
0
Example: 0
If you are using the "read" enpoints, make it include previously read messages
false
Example: false
Qvalia unique identifier for the transaction/message
""
The document identifier of teh message, e.g. Invoice number
""
YYYY-MM-DD, e.g. 2024-01-01
""
YYYY-MM-DD, e.g. 2024-01-01
""
YYYY-MM-DD, e.g. 2024-01-01
""
YYYY-MM-DD, e.g. 2024-01-01
""
API key
""
Either "application/json" (default) or "application/xml"
application/json
GET /transaction/{accountRegNo}/orderagreements/outgoing HTTP/1.1
Host: api-qa.qvalia.com
Authorization:
Accept: */*
{
"status": "success",
"data": [
{
"{transaction-type}": {},
"integrationId": "text"
}
]
}
The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
With JSON, use the limit
parameter to change the number of returned messages and combine it with offset
to traverse through your available messages.
To get new messages only, use the "Read"
endpoint instead!
Account registration number issued by Qvalia
""
For POST requests, chose to overwrite existing message upon 409 Conflict response
false
Example: false
API key
""
Either "application/json" (default) or "application/xml"
application/json
POST /transaction/{accountRegNo}/orderagreements/outgoing HTTP/1.1
Host: api-qa.qvalia.com
Authorization:
Content-Type: application/json
Accept: */*
Content-Length: 20
{
"OrderResponse": {}
}
{
"status": "success",
"data": {
"message": "{transaction-type} 100-1000 sent",
"{transaction-type}_id": "100-1000",
"integrationId": "4725a033-e501-4e2f-afa5-3a5c24eb5e28"
}
}
Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as read
The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
With JSON, use the limit
parameter to change the number of returned messages and combine it with offset
to traverse through your available messages.
Account registration number issued by Qvalia
""
How many messages to return in Array (XML is always one!)
3
Example: 5
Where to start index for using limit/offset listing
0
Example: 0
If you are using the "read" enpoints, make it include previously read messages
false
Example: false
API key
""
Either "application/json" (default) or "application/xml"
application/json
GET /transaction/{accountRegNo}/orderagreements/outgoing/readorderagreement HTTP/1.1
Host: api-qa.qvalia.com
Authorization:
Accept: */*
{
"status": "success",
"data": [
{
"{transaction-type}": {},
"integrationId": "text"
}
]
}
Was this helpful?