Status
How to verify API reachability and credentials for a custom store.
Check the status
curl https://api.pengine.io/store-api/2026-08/stores/$STORE_ID/status \
-H "X-API-Key: $PENGINE_API_KEY"{
"status": "ok",
"message": "Pengine Store API is up and running!",
"version": "2026-08",
"store": { "id": "ovy3u54frpsl4sd963aja0h1" },
"checkedAt": "2026-08-19T12:37:20.829Z"
}Prop
Type
See Status errors for possible failures.
What a 200 tells you
A 200 response confirms that the API is reachable and the key matches the store in the path.
This endpoint checks API reachability and credentials. It does not check the health of every platform dependency.
Using it in monitoring
Once a minute is sufficient. The call consumes one token from your rate limit and appears in the API request log.
It also works as a deployment check. Call it after a deploy or a key rotation, and a 200 confirms the
new configuration reaches the right store.
Errors
Status errors
| Status | Code | When it happens |
|---|---|---|
401 | api_key_missing | The X-API-Key header is missing. |
401 | api_key_invalid | The key is invalid, belongs to another store, or names a store that does not exist. |
401 | store_inactive | The key matches, but the store is inactive. |
401 | api_disabled | The key matches, but the API is disabled for the store. |
There is no unauthenticated version of this endpoint, so monitoring it means monitoring with a key. Rate-limit and server errors use the shared error format. See Errors and Authentication.