Probe Status API
Create a read-only account token and retrieve current probe health from your own systems.
What the API provides
The Probe Status API lets your server read the current health of the monitors in your Blind Spot account. Tokens are limited to the shop that created them and the read-only probes:read permission.
The API returns probe state, cadence, and the most recent check result. It never returns target URLs, request headers, embedded secrets, or Shopify customer data.
Create and verify a token
- 1
Create a token
Open API access, select Create token, add a label that identifies the consuming system and owner, and choose an expiration period.
- 2
Store the credential
Copy the token immediately. It is shown only once. Save it in a secrets manager or protected server environment variable—not in a browser bundle, URL, log, or source-control file.
- 3
Call the API
Send the token as a bearer credential to the account status, probe list, or single-probe endpoint.
- 4
Verify rotation
Create and test a replacement before revoking the old token. A revoked token must immediately return
401 Unauthorized.
export BLINDSPOT_API_TOKEN='bsp_...'
curl --request GET \
--url https://health-monitor.blindspotapps.com/api/v1/status \
--header "Authorization: Bearer $BLINDSPOT_API_TOKEN"Endpoints
| Endpoint | Result |
|---|---|
GET /api/v1/status | Account-wide state and probe counts |
GET /api/v1/probes | All probes owned by the token's shop |
GET /api/v1/probes/:probeId | One probe, if it belongs to the token's shop |
The API uses stable JSON error envelopes. Missing, malformed, expired, revoked, or incorrect credentials return 401; requests over the per-token limit return 429 with a Retry-After header.
Token safety
- Tokens expire after 30, 90, 180, or 365 days.
- Each account can keep up to five active tokens.
- Blind Spot stores a one-way hash, not the plaintext credential.
- The API is intended for server-to-server use and does not enable browser cross-origin access.
- Revocation is permanent. If a token is lost, create and verify a replacement.
Treat the token like a password
Never send a token to Blind Spot support. For troubleshooting, share the request ID from the response and the token label—not the credential itself.
Was this page helpful?

