Skip to content

feat(API): add Checks API endpoints - #1242

Open
Manuel Boy (docstun) wants to merge 5 commits into
mainfrom
feat/checks-api
Open

feat(API): add Checks API endpoints#1242
Manuel Boy (docstun) wants to merge 5 commits into
mainfrom
feat/checks-api

Conversation

@docstun

Copy link
Copy Markdown
Member

What

Adds REST API endpoints for the new Checks API:

  • GET /projects/{project_id}/checks/issues — list check issues for a project, filterable by:
    • stateactive (default), solved, dismissed, or all
    • locale_ids[]
    • check_names[]
    • standard page / per_page pagination
  • PATCH /projects/{project_id}/checks/issues/{id}/dismiss — mark a check issue as dismissed so it drops off the default active list.

Details

  • New check_issue schema mirrors the API serializer: id, check_name, state, description, dismissed_at, solved_at, created_at, updated_at, and the embedded translation.
  • New Checks tag added under the Quality tag group.
  • Listing requires the read scope; dismissing requires the write scope.

Validated with make lint (swagger-cli valid, no openapi-generator validation errors).

🤖 Generated with Claude Code

Add REST API endpoints for listing and dismissing check issues in a
project:

- GET /projects/{project_id}/checks/issues - list check issues,
  filterable by state (active/solved/dismissed/all), locale_ids, and
  check_names, with standard pagination.
- PATCH /projects/{project_id}/checks/issues/{id}/dismiss - mark a check
  issue as dismissed so it drops off the default active list.

Adds the check_issue schema and a Checks tag under the Quality group.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

API changelog (oasdiff)

Doc-only edits (descriptions, examples) do not appear here.

2 changes: 0 error, 0 warning, 2 info
info	[endpoint-added] at doc/compiled.json
	in API GET /projects/{project_id}/checks/issues
		endpoint added

info	[endpoint-added] at doc/compiled.json
	in API PATCH /projects/{project_id}/checks/issues/{id}/dismiss
		endpoint added

Manuel Boy (docstun) and others added 4 commits August 26, 2026 16:36
Document the valid check names (translation_content_length,
translation_placeholder_usage, translation_glossary_usage) as an enum
on the check_names filter and the check_issue.check_name property.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Clarify that the description field may change at any time and should not
be parsed or relied upon programmatically.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a note to the Checks tag description clarifying that the API is
still in development and might change in subsequent releases.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The tag description is not rendered in Mintlify, so add the "still in
development" note to each Checks endpoint description as well.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@docstun
Manuel Boy (docstun) marked this pull request as ready for review August 26, 2026 15:03
Comment thread paths/checks/dismiss.yaml
"$ref": "../../responses.yaml#/401"
'403':
"$ref": "../../responses.yaml#/403"
description: Forbidden. Returned when the access token lacks the `write` scope or when the requesting user is not allowed to dismiss check issues in this project.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

overriding references doesn't work. either it should be only a reference, or a fully defined node. :(

Comment thread schemas/check_issue.yaml
solved_at: null
created_at: '2015-01-28T09:52:53Z'
updated_at: '2015-01-28T09:52:53Z'
translation:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perhaps this could be a reference?

@jablan jablan left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cosmetic issues pointed out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants