Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
api:api_applicants_id_invoices_id [2024/07/30 11:50] – external edit 127.0.0.1api:api_applicants_id_invoices_id [2025/01/24 10:26] (current) – [GDPR information] Lauri
Line 6: Line 6:
  
 However, in order to not destroy accounting records, invoices are the only data that is preserved after an applicant record is destroyed. To achieve this, invoices are detached from the applicant records, losing this association. This is why in the admin UI they are distinctive with a gray "anonymous" icon and also why in the API response the ''applicant'' and ''application'' field is set to ''NULL''.  However, in order to not destroy accounting records, invoices are the only data that is preserved after an applicant record is destroyed. To achieve this, invoices are detached from the applicant records, losing this association. This is why in the admin UI they are distinctive with a gray "anonymous" icon and also why in the API response the ''applicant'' and ''application'' field is set to ''NULL''. 
 +
 +:!: The response field ''collected'' designates that the invoice has been collected **in full**. Partial collections will not set this field, also collections in excess will reset this field back to ''null''. In addition, it is possible to edit the invoice after the payment - if the invoice amount is changed as a result, this field will also be cleared. In short, this field indicates whether the invoice is currently paid in full. The only exception is 0 invoices, in which case the field value is undefined.
  
 ===== HEAD, GET ===== ===== HEAD, GET =====
api/api_applicants_id_invoices_id.1722340208.txt.gz · Last modified: 2024/07/30 11:50 by 127.0.0.1
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International


  • Show page
  • Old revisions