What authentication does the GETPing API use?

GETPing uses an API key sent as the X-API-Key header. Through Jentic the key is stored encrypted in the vault and injected per request, so the raw key never lands in your agent's prompt or logs.

Can I batch ping multiple URLs in one call?

Yes. POST /ping accepts an array of URLs and returns one result per target, which is useful for regional reachability checks or pre-deploy smoke tests against a list of endpoints.

What are the rate limits for the GETPing API?

The OpenAPI spec does not declare specific rate limits. Treat it as a polite-use API: avoid sub-second polling intervals on monitors and prefer the monitor history endpoint over repeatedly hitting GET /ping for the same URL.

How do I retrieve monitor history through Jentic?

Search Jentic for 'get monitor history', load the GET /monitors/{monitorId}/history schema, then execute with your monitor identifier. The response gives you the time series you can chart on a status page.

Can I update a monitor's URL without losing history?

Yes. PUT /monitors/{monitorId} updates the monitor in place - its identifier and accumulated history are preserved while the polled URL or interval changes.

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

Yes. Because you run Jentic One yourself, your own rules decide which GETPing operations and credentials the agent may use. GETPing puts the monitor id in the URL path, such as GET /monitors/{monitorId}/history, so a rule can pin the agent to a single monitor and let it read only that monitor's history and status. You choose the operations it may call, so destructive actions like DELETE /monitors/{monitorId} stay off limits unless you explicitly add them.