curl --request GET \
--url https://v1-api.ticket-plus.app/health
import requests
res = requests.get("https://v1-api.ticket-plus.app/health")
print(res.status_code) # 204
const res = await fetch("https://v1-api.ticket-plus.app/health");
console.log(res.status); // 204
(empty body)
Health
Health Check
Verify that the JobTicket API is reachable and operational.
GET
/
health
curl --request GET \
--url https://v1-api.ticket-plus.app/health
import requests
res = requests.get("https://v1-api.ticket-plus.app/health")
print(res.status_code) # 204
const res = await fetch("https://v1-api.ticket-plus.app/health");
console.log(res.status); // 204
(empty body)
Ping this endpoint to confirm the API is up and accepting connections. No authentication is required.
Authorizations
None required. This endpoint is publicly accessible.Response
null
A
204 No Content response with no body is the only success signal. Any 5xx, timeout, or connection error indicates a service disruption.Use this endpoint in health checks and readiness probes. If you receive anything other than
204, treat the API as unavailable.curl --request GET \
--url https://v1-api.ticket-plus.app/health
import requests
res = requests.get("https://v1-api.ticket-plus.app/health")
print(res.status_code) # 204
const res = await fetch("https://v1-api.ticket-plus.app/health");
console.log(res.status); // 204
(empty body)
Authorizations
HTTP Basic Auth using your API key credentials. Use the username and password issued from the Developer Portal. Encode them as Base64(username:password) and pass in the Authorization: Basic <token> header.
Response
204 - application/json
Service is healthy and accepting requests.
Empty body — a 204 response means the service is healthy.