From 438b4f0d3189613e450a563d84be8b114a3128aa Mon Sep 17 00:00:00 2001 From: Anushka Kulkarni <223412914+Anushkakulkarni1@users.noreply.github.com> Date: Tue, 11 Aug 2026 21:31:12 +0530 Subject: [PATCH 1/2] Fix Population Density Data API description --- code/API_definitions/population-density-data.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/API_definitions/population-density-data.yaml b/code/API_definitions/population-density-data.yaml index 2b9bd58..e5a1e18 100644 --- a/code/API_definitions/population-density-data.yaml +++ b/code/API_definitions/population-density-data.yaml @@ -142,7 +142,7 @@ info: In cases where personal data is processed by the API and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of three-legged access tokens is mandatory. This ensures that the API remains in compliance with privacy regulations, upholding the principles of transparency and user-centric privacy-by-design. - Population Density Data API ensures the usage of anonymized information and do not treat personal data neither as input nor output. + Population Density Data API ensures the usage of anonymized information and does not treat personal data as either input or output. Therefore, the access to Population Density Data API is defined as Client Credentials - 2-legged. Please refer to Identify and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the latest detailed specification of this authentication/authorization flow. From 8245e97ba9e0fec7e633285e3a42199558e91190 Mon Sep 17 00:00:00 2001 From: Anushka Kulkarni <223412914+Anushkakulkarni1@users.noreply.github.com> Date: Tue, 11 Aug 2026 23:04:21 +0530 Subject: [PATCH 2/2] Fix remaining API documentation typos --- code/API_definitions/population-density-data.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/code/API_definitions/population-density-data.yaml b/code/API_definitions/population-density-data.yaml index e5a1e18..57312d1 100644 --- a/code/API_definitions/population-density-data.yaml +++ b/code/API_definitions/population-density-data.yaml @@ -102,7 +102,7 @@ info: The standard behaviour of the API is synchronous, although for large area requests the API may behave asynchronously. An API invoker can enforce asynchronous behaviour by providing a callback URL (`sink`) - is in the request, in this case the API sends a callback + in the request. In this case, the API sends a callback to the callback URL provided with the result of the request. If `sink` is included, it is RECOMMENDED for the client to provide as well the `sinkCredential` property to protect the notification endpoint. In the current version,`sinkCredential.credentialType` @@ -143,7 +143,7 @@ info: Population Density Data API ensures the usage of anonymized information and does not treat personal data as either input or output. - Therefore, the access to Population Density Data API is defined as Client Credentials - 2-legged. Please refer to Identify and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the latest detailed specification of this authentication/authorization flow. + Therefore, the access to Population Density Data API is defined as Client Credentials - 2-legged. Please refer to Identity and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the latest detailed specification of this authentication/authorization flow. # Additional CAMARA error responses