import requests
url = "https://platform.ankra.app/api/v1/org/applications/launch-status"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://platform.ankra.app/api/v1/org/applications/launch-status', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://platform.ankra.app/api/v1/org/applications/launch-status \
--header 'Authorization: Bearer <token>'{
"repository_owner": "<string>",
"repository_name": "<string>",
"state": "not-connected",
"application_id": "<string>",
"decision_count": 123,
"applications": [
{
"application_id": "<string>",
"name": "<string>",
"branch": "<string>",
"state": "not-connected",
"launch_plan_status": "planned",
"decision_count": 123,
"proof_headline": "<string>",
"healthy_deployment_count": 123,
"deployment_count": 123
}
],
"is_truncated": true
}{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>"
}
]
}Get a repository's launch status
Where a GitHub repository is on its way to a working app on Ankra (ankra-bjkszh.7): not connected, analysing, N decisions left in the Launch Plan, ready for approval, proving the setup pull request, proof failed, or live. The state the Ankra Chrome extension shows on GitHub, Vercel, Lovable and Claude Design pages. Every application the caller can see that builds the repository is listed, the one building branch first. Requires applications.read.
import requests
url = "https://platform.ankra.app/api/v1/org/applications/launch-status"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://platform.ankra.app/api/v1/org/applications/launch-status', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://platform.ankra.app/api/v1/org/applications/launch-status \
--header 'Authorization: Bearer <token>'{
"repository_owner": "<string>",
"repository_name": "<string>",
"state": "not-connected",
"application_id": "<string>",
"decision_count": 123,
"applications": [
{
"application_id": "<string>",
"name": "<string>",
"branch": "<string>",
"state": "not-connected",
"launch_plan_status": "planned",
"decision_count": 123,
"proof_headline": "<string>",
"healthy_deployment_count": 123,
"deployment_count": 123
}
],
"is_truncated": true
}{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>"
}
]
}Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
The GitHub repository as owner/name; a trailing .git is ignored.
^[A-Za-z0-9](?:[A-Za-z0-9-]{0,38})/[A-Za-z0-9._-]{1,100}$Put the application that builds this branch first.
255Response
The repository's launch state, not-connected when no visible application builds it
Where a GitHub repository is on its way to a working app. state is the state of the first application: the one building the requested branch, else the oldest. not-connected means no application the caller can see builds the repository; analysing that no App Contract is stored yet; decisions that the Launch Plan leaves decision_count questions to a person; ready that it leaves none; proving that the setup pull request's proof is queued or running; proof-failed that it failed or could not prove; live that a deployment reads Healthy under the readiness gate.
not-connected, analysing, decisions, ready, proving, proof-failed, live Show child attributes
Show child attributes
More applications build the repository than one read judges (five).