Rename content slug
Rename a project-scoped content slug
Authentication: personal access token. The spec defines an api_key security
scheme — send an Authorization: ApiKey <your-personal-access-token> header
(value format: ApiKey <your key>). A session_cookie scheme (connect.sid)
exists for browser sessions. Operations in this spec declare security: [], an
artifact of the upstream spec generator — authentication is still enforced by the
server.
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
projectUuid | string | Yes |
Request body
{
"to": "string",
"from": "string",
"resourceType": "chart"
}Responses
200 — Success
{
"results": "string",
"status": "ok"
}default — Error
{
"error": {
"data": "string",
"message": "string",
"name": "string",
"statusCode": 0
},
"status": "error"
}Reference overview
Auto-generated reference for every public Qyra API endpoint, generated from the OpenAPI spec.
List content-as-code write-backs
List this instance's content-as-code write-back PRs for the project. Pass refresh=true to also re-check open PRs against the git provider (a merged PR then reads as merged instead of a stale pending badge).