Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
api:api_applicants_id_invoices [2018/10/17 11:40] Lauri Elevantapi:api_applicants_id_invoices [2018/10/17 11:40] Lauri Elevant
Line 1: Line 1:
 ====== /api/applicants/ID/invoices ====== ====== /api/applicants/ID/invoices ======
  
-===== HEAD, GET ===== +===== GDPR information =====
- +
-Get a list of invoices that have been issued for the applicant in question. +
- +
-==== GDPR information ====+
  
 Due to GDPR regulations, it is possible to delete applicants from the system, for example with the "Right to be forgotten" tool, batch purge (by academic term) or with an individual applicant record deletion. Due to GDPR regulations, it is possible to delete applicants from the system, for example with the "Right to be forgotten" tool, batch purge (by academic term) or with an individual applicant record deletion.
  
 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'' 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'' field is set to ''NULL''
 +
 +===== HEAD, GET =====
 +
 +Get a list of invoices that have been issued for the applicant in question.
  
 ==== Syntax ==== ==== Syntax ====