What authentication does the Phare API use?

The Phare API uses Bearer token authentication. API keys are generated from the Phare control panel and can be project-scoped (acting on a specific project) or organization-scoped (requiring project selection headers). Through Jentic, your API key is stored encrypted and agents never handle the raw token.

Can I pause monitors during maintenance?

Yes. POST /uptime/monitors/{id}/pause temporarily stops a monitor from checking. POST /uptime/monitors/{id}/resume restarts it. This prevents false incident alerts during planned maintenance windows without deleting and recreating the monitor.

How do I retrieve incident data through Jentic?

Search Jentic for 'list uptime incidents' to discover GET /uptime/incidents. Load the schema and execute to retrieve incident records including timestamps, affected monitors, and downtime duration. Use this data for SLA reporting or escalation logic.

What is the difference between project-scoped and organization-scoped API keys?

Project-scoped keys automatically target their assigned project for all operations. Organization-scoped keys require you to specify the target project via request headers, but allow access to multiple projects with a single key. GET /projects lists available projects for organization-scoped keys.

Can I limit what my agent is allowed to do with the Phare API?

Yes. Because you run Jentic One yourself, your own rules decide which Phare operations and credentials your agent can use. Phare puts the monitor id in the URL path (/uptime/monitors/{id}), so a rule can pin your agent to a single monitor and let it read, pause, or resume only that one. You pick the operations it may call, so a destructive action like DELETE /uptime/monitors/{id} stays out of reach unless you explicitly add it.