GET /api/build/{id}
{
"id": 1,
"label": "Test application iOS [1.5.2]",
"version": "1.5.2",
"comment": "This is a comment for this build.\nWith a line break.\nAnd another one.\n",
"is_latest": true,
"download_link": "http://my-appbuild.domain/fr/application/1/build/1/download",
"application": {
"id": 1
}
}
GET /api/application/{application_id}/build
[
{
"id": 1,
"label": "Test application iOS [1.5.2]",
"version": "1.5.2",
"comment": "This is a comment for this build.\nWith a line break.\nAnd another one.\n",
"is_latest": true,
"download_link": "http://my-appbuild.domain/fr/application/1/build/1/download",
"application": {
"id": 1
}
}
]
Note: This one has a smaller footprint in order to be used by devices to check for newer application build.
GET /api/application/{application_id}/build/latest
{
"id": 1,
"version": "1.5.2",
"comment": "This is a comment for this build.\nWith a line break.\nAnd another one.\n",
"download_link": "http://my-appbuild.domain/fr/application/1/build/1/download"
}
Note : The route return an url to upload and it can be somewhere else than the API.
PUT /api/application/{application_id}/build
{
"version": "1.5.2",
"comment": "This is a comment for this build.\nWith a line break.\nAnd another one.\n"
}
200 OK
{
"build_id": 4,
"upload_location": "http://my-appbuild.domain/api/build/4/file"
}
Note: This route is given by Create a new build
through upload_location
response field.
PUT /api/build/{build_id}/file
Binary file in body
200 OK