diff --git a/assessment/cloud/spec.yml b/assessment/cloud/spec.yml index 6821f269..bed0980f 100644 --- a/assessment/cloud/spec.yml +++ b/assessment/cloud/spec.yml @@ -52,7 +52,7 @@ paths: parameters: - name: customer_id in: path - description: The customer identifier is a UUIDv4. + description: The customer identifier is a UUIDv4. required: true schema: type: string @@ -77,7 +77,7 @@ paths: in: query description: | Only return emails submitted from this date. - The date should be in RFC3339 format. + The date should be in RFC3339 format. schema: type: string format: date-time @@ -86,7 +86,7 @@ paths: in: query description: | Only return emails submitted before this date. - The date should be in RFC3339 format. + The date should be in RFC3339 format. schema: type: string format: date-time @@ -156,7 +156,7 @@ paths: parameters: - name: customer_id in: path - description: The customer identifier is a UUIDv4 where the first 4 characters represent the customer type. Customers with 1111####-####-####-####-############ are to be treated as high priority while all other valid UUIDv4's are to be treated as standard priority. + description: The customer identifier is a UUIDv4 where the first 4 characters represent the customer type. Customers with 1111####-####-####-####-############ are to be treated as high priority while all other valid UUIDv4's are to be treated as standard priority. required: true schema: type: string @@ -195,7 +195,7 @@ paths: parameters: - name: customer_id in: path - description: The customer identifier is a UUIDv4. + description: The customer identifier is a UUIDv4. required: true schema: type: string @@ -239,7 +239,7 @@ paths: parameters: - name: customer_id in: path - description: The customer identifier is a UUIDv4. + description: The customer identifier is a UUIDv4. required: true schema: type: string @@ -260,7 +260,7 @@ paths: generated_at: type: string format: date-time - description: The date and time the report was generated in RFC3339 format. If the report is being made live then this should be the current date and time. + description: The date and time the report was generated in RFC3339 format. If the report is being made live then this should be the current date and time. example: 2024-02-21T13:10:05Z total: type: integer @@ -294,7 +294,7 @@ paths: parameters: - name: customer_id in: path - description: The customer identifier is a UUIDv4. + description: The customer identifier is a UUIDv4. required: true schema: type: string @@ -315,7 +315,7 @@ paths: generated_at: type: string format: date-time - description: The date and time the report was generated in RFC3339 format. If the report is being made live then this should be the current date and time. + description: The date and time the report was generated in RFC3339 format. If the report is being made live then this should be the current date and time. example: 2024-02-21T13:10:05Z total: type: integer @@ -349,7 +349,7 @@ paths: parameters: - name: customer_id in: path - description: The customer identifier is a UUIDv4. + description: The customer identifier is a UUIDv4. required: true schema: type: string @@ -372,7 +372,7 @@ paths: generated_at: type: string format: date-time - description: The date and time the report was generated in RFC3339 format. If the report is being made live then this should be the current date and time. + description: The date and time the report was generated in RFC3339 format. If the report is being made live then this should be the current date and time. example: 2024-02-21T13:10:05Z total: type: integer