add payment notification endpoints #2146
Lint (pull_request)
Lint completed with some errors
Annotations
Check warning on line 2859 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
summaries-should-be-in-sentence-case
All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).
Check warning on line 3254 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
summaries-should-be-in-sentence-case
All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).
Check warning on line 3295 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
request-body-properties-example
Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.
Check warning on line 4733 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
response-body-objects-arrays-example
Response body fields should not contain the "example" field. The response example corresponds to the whole schema.
Check warning on line 3182 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
summaries-should-be-in-sentence-case
All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).
Check warning on line 4624 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
response-body-objects-arrays-example
Response body fields should not contain the "example" field. The response example corresponds to the whole schema.
Check failure on line 2761 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
no-empty-descriptions
No empty descriptions allowed. Make sure that this description is a valid string that does not start with a line break (\n or \r). If this description is inside an example, please fill it with a valid value.
Check warning on line 4114 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
operation-tag-defined
Operation tags must be defined in global tags.
Check warning on line 4659 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
response-body-objects-arrays-example
Response body fields should not contain the "example" field. The response example corresponds to the whole schema.
Check warning on line 4619 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
response-body-objects-arrays-example
Response body fields should not contain the "example" field. The response example corresponds to the whole schema.
Check warning on line 3328 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
summaries-should-be-in-sentence-case
All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).
Check warning on line 2987 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
summaries-should-be-in-sentence-case
All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).
Check warning on line 3223 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
request-body-properties-example
Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.
Check warning on line 4767 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
response-body-objects-arrays-example
Response body fields should not contain the "example" field. The response example corresponds to the whole schema.
Check warning on line 4664 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
response-body-objects-arrays-example
Response body fields should not contain the "example" field. The response example corresponds to the whole schema.
Check warning on line 4784 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
response-body-objects-arrays-example
Response body fields should not contain the "example" field. The response example corresponds to the whole schema.
Check warning on line 4795 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
response-body-objects-arrays-example
Response body fields should not contain the "example" field. The response example corresponds to the whole schema.
Check warning on line 3291 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
request-body-properties-example
Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.
Check warning on line 4779 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
response-body-objects-arrays-example
Response body fields should not contain the "example" field. The response example corresponds to the whole schema.
Check warning on line 3219 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
request-body-properties-example
Each request body property should have an example. In case the schema is also used as a response and there is already an example elsewhere, feel free to ignore this alert. If you have chosen to include a complete example of the schema to better represent arrays, feel free to ignore this alert.
Check warning on line 3040 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
summaries-should-be-in-sentence-case
All endpoint summaries should use sentence case (capitalize only the first letter) and never contain periods (`.`). Exceptions include product names and some specific terms (e.g., SKU, ID).
Check warning on line 4789 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
response-body-objects-arrays-example
Response body fields should not contain the "example" field. The response example corresponds to the whole schema.
Check warning on line 4081 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
operation-tag-defined
Operation tags must be defined in global tags.
Check warning on line 4884 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
response-body-objects-arrays-example
Response body fields should not contain the "example" field. The response example corresponds to the whole schema.
Check warning on line 4827 in VTEX - Payments Gateway API.json
github-actions / Lint (pull_request)
response-body-objects-arrays-example
Response body fields should not contain the "example" field. The response example corresponds to the whole schema.