curl --location --request GET 'https://api.stateset.com/v1/deployments' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data-raw '{
"id": 1
}'
{
"id": 1,
"name": "string",
"url": "string",
"status": "string",
"created_at": "string",
"updated_at": "string",
"project_id": 1,
"user_id": 1
}
Get Deployments
This endpoint gets deployments.
GET
/
v1
/
deployments
curl --location --request GET 'https://api.stateset.com/v1/deployments' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data-raw '{
"id": 1
}'
{
"id": 1,
"name": "string",
"url": "string",
"status": "string",
"created_at": "string",
"updated_at": "string",
"project_id": 1,
"user_id": 1
}
Body
integer
This is the id of the deployment.
This read takes a request body. The Fetch standard forbids a body on
GET,
so fetch() rejects this call rather than sending one — reach for a server-side
client (curl, undici.request, Python requests) instead. Proxies and CDNs are
also free to drop a body on a read, so prefer a direct connection.Response
number
This is the id of the deployment
string
This is the name of the deployment
string
This is the url of the deployment
string
This is the status of the deployment
string
This is the created_at of the deployment
string
This is the updated_at of the deployment
number
This is the project_id of the deployment
number
This is the user_id of the deployment
Errors
Succeeds with200. Failures return 400, 401, 403 or 429 with an error body, per the platform status-code contract.
curl --location --request GET 'https://api.stateset.com/v1/deployments' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data-raw '{
"id": 1
}'
{
"id": 1,
"name": "string",
"url": "string",
"status": "string",
"created_at": "string",
"updated_at": "string",
"project_id": 1,
"user_id": 1
}
Last modified on August 29, 2026