What authentication does the Ping.ie API use?

Ping.ie 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 run ping tests from multiple geographic locations?

Yes. The POST /ping endpoint accepts a locations array parameter that lets you specify probe points such as Dublin, London, New York, Singapore, and others. The response includes per-location latency metrics in a single call.

How do I check DNS propagation after updating records?

Use POST /dns/lookup with the domain and record type (A, AAAA, MX, etc.). The API queries from multiple DNS resolvers and returns the results showing whether your changes have propagated globally.

What SSL certificate details does the API return?

GET /ssl/validate returns the certificate chain, issuer, subject, validity dates, signature algorithm, key size, supported cipher suites, and any chain validation errors. This covers everything needed for security audits and expiration monitoring.

Can I update a monitor's check interval without losing history?

Yes. PUT /monitors/{monitorId} updates the monitor configuration in place - its identifier and accumulated check history are preserved while you change the interval, target URL, or probe locations.

Can I limit what my agent is allowed to do with the Ping.ie API?

Yes. Because you run Jentic One yourself, your own rules decide which Ping.ie operations and credentials the agent may use. You can allow one-off diagnostics such as POST /ping or POST /traceroute on their own, and since the monitor id sits in the URL path (/monitors/{monitorId}), a rule can pin the agent to reading a single monitor and its history. Changing or deleting a monitor via PUT or DELETE stays out of reach unless you explicitly add it.