Monitors & detections
Check authenticated endpoints safely
Use bearer tokens, Basic authentication, headers and request bodies.
Reviewed
Set protected details
Open Request and choose Set new details. Protected request details require an HTTPS target. You can provide a bearer token, Basic authentication, custom headers and an optional body.
Use credentials scoped to the health endpoint. The examples here are fictional; never paste production credentials into a public guide, name, tag or screenshot.
- Choose your HTTP method.
- Select Set new details under Protected request details.
- Select Bearer token or Basic authentication and enter the required values.
- Add any headers your endpoint expects, then save.
Send a small JSON body
GET and HEAD cannot send a body. Other supported methods accept a body up to 16 KiB. If your endpoint expects JSON, add Content-Type with the value application/json. Up to 20 custom headers are supported.
For example, a dedicated POST health endpoint could accept the following body. Confirm the endpoint is safe to call repeatedly before enabling the monitor.
{"check":"health"}Keep, replace or remove
Saved values are encrypted and are not displayed again in the editor. Keep saved details preserves the current configuration. Replace all saved details stores only the values you enter now, so enter the complete set. Remove saved details clears it.
Protected requests do not follow redirects to another origin. Use the final HTTPS URL if necessary. Response logs are omitted for protected requests to avoid exposing echoed credentials. Exported monitors omit protected details; re-enter them before resuming an imported monitor.