Get release history of a deployment
const url = 'https://api.aetherpush.com/v1/apps/example/deployments/example/history';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.aetherpush.com/v1/apps/example/deployments/example/history \ --header 'Authorization: Bearer <token>'Returns the release history of the deployment. Without query
params, returns the full history. Pass page and/or size to
opt into pagination; pass startDate/endDate (Unix ms) to
filter by upload time.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”1-indexed page number. Triggers paginated response.
Items per page. Default 20.
Unix timestamp in ms; releases uploaded before this are excluded.
Unix timestamp in ms; releases uploaded after this are excluded.
Responses
Section titled “Responses”Release history (paginated when page or size is provided).
object
object
Signed URL to download the package bundle.
True when this release is currently held by the automatic release
halt: the package is disabled and a halt event exists at its
current auto-halt generation. Present on
GET /v1/apps/{appName}/deployments/{deploymentName}/history
(and the paginated form of that route). False after an override
re-enables the release, after a manual disable with no live halt
event, or when the package is enabled. Omitted on Package
responses that do not compute the flag.
Server-minted release id (for example v3). Omitted when the
package has no label. Never null and never an empty string.
Set when releaseMethod is Promote.
Set when releaseMethod is Promote or Rollback.
SHA-256 hash of the package contents. The server computes this from the uploaded bytes; callers do not supply it.
Percentage of devices eligible for this release (1-100).
Full rollout is always 100 in responses; the server stores
completed rollouts as null and normalises them at the REST
boundary.
Package size in bytes.
Unix timestamp in milliseconds.
object
Number of items in the current page.
Example
{ "history": [ { "appVersion": "1.0.0", "label": "v3", "releaseMethod": "Upload" } ]}Unauthenticated.
Standard error envelope. code is the stable machine identifier for
client branching and i18n. The wording of error is a human-readable
fallback and is not part of the contract. Specialized responses keep
narrower code enums where clients already branch on them.
object
Human-readable error message.
Stable machine code. Prefer this over matching on error. The
values this API can answer with are listed in the ApiErrorCode
schema of the raw document at
https://api.aetherpush.com/openapi.yaml. The field stays an
open string here so that a release adding a value does not
invalidate this response.
Unique identifier for the request, also exposed as the X-Request-Id response header.
Example
{ "error": "The requested resource was not found.", "code": "not_found", "requestId": "req_abc123"}The API key’s scopes do not grant read, which answers
required_scopes. A refusal raised before the route is reached,
such as a request that did not arrive through the trusted edge,
answers a plain error instead.
Standard error envelope. code is the stable machine identifier for
client branching and i18n. The wording of error is a human-readable
fallback and is not part of the contract. Specialized responses keep
narrower code enums where clients already branch on them.
object
Human-readable error message.
Stable machine code. Prefer this over matching on error. The
values this API can answer with are listed in the ApiErrorCode
schema of the raw document at
https://api.aetherpush.com/openapi.yaml. The field stays an
open string here so that a release adding a value does not
invalidate this response.
Unique identifier for the request, also exposed as the X-Request-Id response header.
Returned when an API key’s scopes do not grant the scope a management
route requires. required_scopes lists what the route asked for, not
what the key holds. Access keys and login sessions carry wildcard
scope and pass the check without reaching this response, so only
apiKeyAuth callers receive it. A key whose only scope is keys gets
this on every management route, because that scope grants nothing,
which is also why keys never appears in required_scopes.
object
The scopes the route requires. Only these three appear: no
management route requires keys.
Examples
The API key's scopes do not grant read
{ "error": "Insufficient permissions", "code": "insufficient_scopes", "required_scopes": [ "read" ], "requestId": "req_abc123"}Refused before the route, here by the trusted edge
{ "error": "Forbidden", "code": "forbidden", "requestId": "req_abc123"}App or deployment not found.
Standard error envelope. code is the stable machine identifier for
client branching and i18n. The wording of error is a human-readable
fallback and is not part of the contract. Specialized responses keep
narrower code enums where clients already branch on them.
object
Human-readable error message.
Stable machine code. Prefer this over matching on error. The
values this API can answer with are listed in the ApiErrorCode
schema of the raw document at
https://api.aetherpush.com/openapi.yaml. The field stays an
open string here so that a release adding a value does not
invalidate this response.
Unique identifier for the request, also exposed as the X-Request-Id response header.
Example
{ "error": "The requested resource was not found.", "code": "not_found", "requestId": "req_abc123"}The tenant’s per-minute management API budget is spent.
Retry-After and X-RateLimit-* say when to retry. This is
not a plan quota: quota 429s use the Error envelope and do
not set Retry-After.
Returned with HTTP 429 when an endpoint-specific rate limit is hit,
including the per-tenant management API budget. Not the process-wide
address limiter (see GlobalAddressRateLimitErrorResponse).
retryAfterSeconds
indicates how long the client should wait before retrying, and matches
the Retry-After header when that header is set. code names the
limit that fired so clients can translate without matching on error.
object
Example
{ "error": "Rate limit exceeded", "code": "tenant_rate_limit_exceeded", "retryAfterSeconds": 60}Headers
Section titled “Headers”Seconds until the tenant window resets.