From b31d5dee2c70ae75cfe52ca675e221d74fc6f2cc Mon Sep 17 00:00:00 2001 From: Randy Levensalor Date: Tue, 15 Oct 2024 09:46:50 -0600 Subject: [PATCH] Updating link to use tag in comment Co-authored-by: Herbert Damker --- code/API_definitions/qos-profiles.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/API_definitions/qos-profiles.yaml b/code/API_definitions/qos-profiles.yaml index 6fcc80f84..68ddde1a6 100644 --- a/code/API_definitions/qos-profiles.yaml +++ b/code/API_definitions/qos-profiles.yaml @@ -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: