Bad Request
bad-request · 400
The API refused the request on a rule its field checks can't express, and detail names the rule.
All pages
Unlike validation-error, it carries no errors[]: the explanation is in detail. A refusal for a launch that named no site adds openSites, the sites open for new services.
This type adds no members to the ones every error carries.
- Two ids that must belong together don't, such as an environment from a different project than the service's.
- The operation doesn't apply to this kind of service: only web services deploy or take a custom domain.
- An id in the path is malformed. It must be a UUID v7, or a slug where the route takes one.
- A launch that would create a service named no site, and nothing picks one for it.
- Read
detail. It is written for this case and names the rule that was broken. - On
site_required, pass--sitewith one ofopenSites. WhenopenSitesis empty,detailreadsNo site is open. - Check that every id in the request belongs to the same project.
- Don't retry unchanged: the same request is refused again.
json
{
"type": "bad-request",
"title": "Bad Request",
"status": 400,
"detail": "Environment belongs to a different project",
"requestId": "req-1785231000000-4f7b2c9ae",
"timestamp": "2026-07-28T09:30:00.000Z",
"path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/deployments",
"method": "POST",
"instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/deployments",
"docs": "https://ghaym.me/docs/errors/bad-request"
}