---
title: "Tell Vigilia a new version went live"
method: POST
path: "/apps/{appId}/deploys"
tags: ["Apps"]
---

# Tell Vigilia a new version went live

`POST /apps/{appId}/deploys`

## Request

- Base URL: `https://app.getvigilia.com/v1`
- URL: `https://app.getvigilia.com/v1/apps/{appId}/deploys`
- Auth: HTTP bearer

Call it from CI or a deploy hook. Vigilia also notices deploys on its own from the page's build; a marker adds your label (a version or commit) and exact timing. Errors that begin within a day of a deploy say so on their incident (`afterDeploy`). The same label posted twice within ten minutes is treated as one deploy. Needs a read & write token.

## Path parameters

- `appId` string, required

## Request body

- object
  - `label` string: e.g. "v1.4.2" or a commit SHA

## Response `201`

Recorded.

- object
  - `deploy` object
    - `at` integer
    - `label` string, nullable

## Other responses

- `401`: No token, or not a valid one.
- `403`: The token is read-only.
- `404`: No such thing on your account.
- `429`: Too many requests for this token (`rate_limited`), or a Free account's daily requests are used up (`daily_limit`) — wait `Retry-After` seconds.

---

[API](https://skmtc.dev/getvigilia/apis/vigilia-api.md) · [All operations](https://skmtc.dev/getvigilia/apis/vigilia-api/llms.txt) · [OpenAPI document](https://skmtc.dev/getvigilia/apis/vigilia-api/revisions/43dd51b3e83a?raw)