Skip to content

Commit

Permalink
Update code/API_definitions/qod-provisioning.yaml
Browse files Browse the repository at this point in the history
Adding link into flow of text

Co-authored-by: Jose Luis Urien <[email protected]>
  • Loading branch information
RandyLevensalor and jlurien authored Nov 15, 2024
1 parent b31d5de commit 7ea0672
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion code/API_definitions/qod-provisioning.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -304,7 +304,7 @@ paths:
- If a 2-legged access token is used, the device parameter must be provided and identify a device.
- The QoD provisioning must have been created by the same API client given in the access token.
- If no provisioning is found for the device, an error response 404 is returned with code "NOT_FOUND".
- This call uses the POST method instead of GET to comply with the CAMARA Commonalities guidelines for sending sensitive or complex data in API calls. Since the device field may contain personally identifiable information, it should not be sent via GET.
- This call uses the POST method instead of GET to comply with the [CAMARA Commonalities guidelines](https://github.com/camaraproject/Commonalities/blob/r0.4.0/documentation/API-design-guidelines.md#post-or-get-for-transferring-sensitive-or-complex-data) for sending sensitive or complex data in API calls. Since the device field may contain personally identifiable information, it should not be sent via GET.
[CAMARA API Design Guidelines](https://github.com/camaraproject/Commonalities/blob/r0.4.0/documentation/API-design-guidelines.md#post-or-get-for-transferring-sensitive-or-complex-data)
operationId: retrieveProvisioningByDevice
Expand Down

0 comments on commit 7ea0672

Please sign in to comment.