API Overview

Programmatic access to manage your Pinguzo servers and monitors via REST API.

Introduction

The Pinguzo REST API allows you to manage your servers and monitors programmatically. All requests are made to a single endpoint and authenticated with your API key. The API returns JSON responses with consistent success and error formats.

Base URL

https://cp.pinguzo.com/api/v1/rest.php

All API requests are made to this URL, with the resource query parameter determining which entity you are working with (servers, monitors, or incidents).

Rate Limiting

Each API key is limited to 1000 requests per hour. If you exceed this limit, you will receive a 429 Too Many Requests response. The rate limit window resets every hour.

Rate limit headers The rate limit is tracked per API key using a sliding 1-hour window. If you need a higher limit for your use case, contact support.

Plan Limits & API Access

API access is available on all paid plans. The Free plan does not include API access. The number of servers and monitors you can create depends on your plan:

PlanServersMonitorsMin Check IntervalAPI Access
Free15300s (5 min)No
Personal12060s (1 min)Yes
Mini24060s (1 min)Yes
Professional1020060s (1 min)Yes
Business100200060s (1 min)Yes
Plan expiry If your paid plan expires, API access is paused until you renew. You will receive a 403 response with the error code PLAN_EXPIRED.

Getting Your API Key

  1. Log in to your Pinguzo dashboard
  2. Click API in the left sidebar
  3. Your API key is displayed (masked by default). Click View Key to reveal it
  4. Use the Copy button to copy it to your clipboard
Keep your key secret Anyone with your API key can access your Pinguzo account via the API. If your key is compromised, click Regenerate API Key on the API page — the old key will stop working immediately.

Available Resources

ResourceMethodsDescription
serversGET, POST, PUT, DELETEManage your monitored servers
monitorsGET, POST, PUT, DELETEManage uptime monitors (HTTP, HTTPS, Ping, Port, Keyword, DNS, SSL)
incidentsGETList and filter incidents (read-only)

Next Steps