Skip to content

Commit

Permalink
Updating link to use tag in comment
Browse files Browse the repository at this point in the history
Co-authored-by: Herbert Damker <[email protected]>
  • Loading branch information
RandyLevensalor and hdamker authored Oct 15, 2024
1 parent 2aae560 commit b5bc186
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 @@ -305,7 +305,7 @@ paths:
- 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.
[CAMARA API Design Guidelines](https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#post-or-get-for-transferring-sensitive-or-complex-data)
[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
parameters:
Expand Down

0 comments on commit b5bc186

Please sign in to comment.