curl -s "https://inference.impulselabs.ai/deploy/status?deployment_id=clf-titanic-survived" \
-H "Authorization: Bearer $IMPULSE_API_KEY"
import os, requests
resp = requests.get(
"https://inference.impulselabs.ai/deploy/status",
params={"deployment_id": "clf-titanic-survived"},
headers={"Authorization": f"Bearer {os.environ['IMPULSE_API_KEY']}"},
)
print(resp.json()["status"]) # "ACTIVE"
const params = new URLSearchParams({ deployment_id: "clf-titanic-survived" });
const resp = await fetch(
`https://inference.impulselabs.ai/deploy/status?${params}`,
{ headers: { Authorization: `Bearer ${process.env.IMPULSE_API_KEY}` } }
);
const { status } = await resp.json();
console.log(status); // "ACTIVE"
{
"deployment_id": "clf-titanic-survived",
"status": "ACTIVE"
}
{
"deployment_id": "clf-titanic-survived",
"status": "BUILDING"
}
{
"detail": "No deployment 'clf-titanic-survived' found for user"
}
Inference
Deployment Status
Check whether a model deployment is ready to receive inference requests.
GET
/
deploy
/
status
curl -s "https://inference.impulselabs.ai/deploy/status?deployment_id=clf-titanic-survived" \
-H "Authorization: Bearer $IMPULSE_API_KEY"
import os, requests
resp = requests.get(
"https://inference.impulselabs.ai/deploy/status",
params={"deployment_id": "clf-titanic-survived"},
headers={"Authorization": f"Bearer {os.environ['IMPULSE_API_KEY']}"},
)
print(resp.json()["status"]) # "ACTIVE"
const params = new URLSearchParams({ deployment_id: "clf-titanic-survived" });
const resp = await fetch(
`https://inference.impulselabs.ai/deploy/status?${params}`,
{ headers: { Authorization: `Bearer ${process.env.IMPULSE_API_KEY}` } }
);
const { status } = await resp.json();
console.log(status); // "ACTIVE"
{
"deployment_id": "clf-titanic-survived",
"status": "ACTIVE"
}
{
"deployment_id": "clf-titanic-survived",
"status": "BUILDING"
}
{
"detail": "No deployment 'clf-titanic-survived' found for user"
}
Poll this endpoint to confirm a deployment is
ACTIVE before sending inference requests.
Query parameters
Response
Deployment statuses
| Status | Description |
|---|---|
CREATED | Deployment registered; container build not yet started |
BUILDING | Container image is being built |
ACTIVE | Model is deployed and accepting inference requests |
FAILED | Deployment failed — retrain or contact support |
Cold-start latency is typically under 30 seconds. If a deployment stays in
BUILDING for more than 5 minutes, try redeploying from the dashboard.Polling example
Python — wait for ACTIVE
import os
import time
import requests
API_KEY = os.environ["IMPULSE_API_KEY"]
DEPLOYMENT_ID = "clf-titanic-survived"
HEADERS = {"Authorization": f"Bearer {API_KEY}"}
def wait_for_active(deployment_id: str, timeout: int = 120) -> None:
deadline = time.time() + timeout
while time.time() < deadline:
resp = requests.get(
"https://inference.impulselabs.ai/deploy/status",
params={"deployment_id": deployment_id},
headers=HEADERS,
)
resp.raise_for_status()
status = resp.json()["status"]
print(f"Status: {status}")
if status == "ACTIVE":
return
if status == "FAILED":
raise RuntimeError(f"Deployment {deployment_id} failed")
time.sleep(5)
raise TimeoutError(f"Deployment did not become ACTIVE within {timeout}s")
wait_for_active(DEPLOYMENT_ID)
curl -s "https://inference.impulselabs.ai/deploy/status?deployment_id=clf-titanic-survived" \
-H "Authorization: Bearer $IMPULSE_API_KEY"
import os, requests
resp = requests.get(
"https://inference.impulselabs.ai/deploy/status",
params={"deployment_id": "clf-titanic-survived"},
headers={"Authorization": f"Bearer {os.environ['IMPULSE_API_KEY']}"},
)
print(resp.json()["status"]) # "ACTIVE"
const params = new URLSearchParams({ deployment_id: "clf-titanic-survived" });
const resp = await fetch(
`https://inference.impulselabs.ai/deploy/status?${params}`,
{ headers: { Authorization: `Bearer ${process.env.IMPULSE_API_KEY}` } }
);
const { status } = await resp.json();
console.log(status); // "ACTIVE"
{
"deployment_id": "clf-titanic-survived",
"status": "ACTIVE"
}
{
"deployment_id": "clf-titanic-survived",
"status": "BUILDING"
}
{
"detail": "No deployment 'clf-titanic-survived' found for user"
}