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 ca9a143 commit b31d5de
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion code/API_definitions/qos-profiles.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ paths:
- The access token may be either a 2-legged or 3-legged access token.
- If the access token is 3-legged, all returned QoS Profiles will be available to all end users associated with the access token.
- 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. Additionally, this call may include complex data structures.
[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)
security:
- openId:
Expand Down

0 comments on commit b31d5de

Please sign in to comment.