Table of contents
⚙️ Massive management via API REST
Massive management can be triggered via API, whose specifications are indicated below in the document.
Via the API /brokers/{broker-code}/organizations/{organization-fiscal-code}/debtpositions/file it is possible to trigger the massive loading, change and deletion of the debt positions present in a compressed file, as described in the Input trace specifications.
In a positive case, the method responds immediately with a code HTTP 202, once a positive response is obtained, it is possible check the status of the massive operation using the API /brokers/{broker-code}/organizations/{organization-fiscal-code}/debtpositions/file/{fileId}/status. To obtain a complete report, including the outcomes for every debt position, query the API
/brokers/{broker-code}/organizations/{organization-fiscal-code}/debtpositions/file/{fileId}/report
Via the API /brokers/{broker-code}/organizations/{organization-fiscal-code}/debtpositions/file it is possible to trigger the massive loading, change and deletion of the debt positions present in a compressed file, as described in the Input trace specifications.
In a positive case, the method responds immediately with a code HTTP 202, once a positive response is obtained, it is possible check the status of the massive operation using the API /brokers/{broker-code}/organizations/{organization-fiscal-code}/debtpositions/file/{fileId}/status. To obtain a complete report, including the outcomes for every debt position, query the API
/brokers/{broker-code}/organizations/{organization-fiscal-code}/debtpositions/file/{fileId}/report
post
delete
On this page
Tell us what you think
For clarifications on implementation specifications, such as SACI and SANP, you can open an issue on GitHub