Sending Reports

Reports are feedback items — bug reports, support messages, "this typo bugs me" notes — that land in a project's report queue, where your team can promote the useful ones to issues and dismiss the rest. External systems submit reports through the Reports API using a project token.

Typical sources: a CI pipeline filing a report when a build fails, an in-app feedback widget, or a support inbox forwarding messages in.

Requires the Reports feature

Report submission is only available when the Reports feature is enabled for your workspace. If it is disabled, requests return 403 with "feature_restricted": true.

1. Mint a project token

Report submission authenticates with a project token carrying the report:create ability:

Open the project and go to Settings (/projects/{projectId}/settings).
Scroll to the API Tokens section.
Click Create Token, name it (e.g. CI/CD Pipeline), and set the Ability to Reports.
Click Create and copy the token — it is shown only once. Store it in your CI secrets or environment.

The token is bound to that one project and may call only POST .../reports.

2. Submit a report

POST /api/projects/{projectId}/reports

bash

curl -X POST https://{tenant}.kendo.dev/api/projects/1/reports \
  -H "Authorization: Bearer your-project-token" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Deployment failed",
    "description": "Build #1234 failed with exit code 1. See logs at https://ci.example.com/1234",
    "author_name": "CI Pipeline"
  }'

Field	Required	Description
`title`	Yes	Report title, max 255 characters
`description`	Yes	Report body, max 65,535 characters
`author_name`	No	Name of the external reporter (service or person)
`files`	No	Up to 5 image attachments (jpg, jpeg, png, gif, webp, bmp, tiff; max 3 MB each)

A report submitted with a project token is automatically tagged source: 1 (Api) and created_by: null, distinguishing it from reports filed by a person in the UI. The response is the created report (201), including an attachments_count.

With screenshots

To attach images — a screenshot of the bug, a failing log — switch from JSON to multipart/form-data:

bash

curl -X POST https://{tenant}.kendo.dev/api/projects/1/reports \
  -H "Authorization: Bearer your-project-token" \
  -F "title=Login button misaligned on mobile" \
  -F "description=See attached screenshot." \
  -F "author_name=Feedback widget" \
  -F "files[0][email protected]"

3. Triage on the board

Submitted reports appear in the project's report queue. From there your team can:

Promote one or more reports into a single issue — the reports are linked to the new issue and marked as promoted.
Dismiss a report — it stays on record but drops out of the active queue.

See the Reports API for the promote, dismiss, reorder, and delete endpoints if you want to drive triage programmatically too.

Limits and errors

Report endpoints use the default API rate limit of 120 requests per minute. Common failures:

Status	Cause
`401`	Token is missing, invalid, revoked, or expired
`403`	Token lacks the required ability, or the Reports feature is disabled (`"feature_restricted": true`)
`422`	Validation failed, or the token is not linked to (or inactive for) the target project
`429`	Rate limit exceeded (120 requests per minute)

Sending Reports ​

1. Mint a project token ​

2. Submit a report ​

With screenshots ​

3. Triage on the board ​

Limits and errors ​

See Also ​