Name: Uptydupty API | API-Only Uptime Monitoring
Brand: manowar-online
SKU: api-manowar-online-uptydupty
Availability: InStock
Author: API Market

Gustavo Silva

# Uptydupty API

[![Uptydupty API](https://manowar.online/uptyduptyapi.svg)](https://manowar.online/uptydupty/)

**60-second uptime checks. Your status page. Your brand.**  
API-only URL monitoring. No dashboard to white-label.

Uptydupty is a minimalistic alternative to [UptimeRobot](https://uptimerobot.com/), [Uptime.com](https://uptime.com/), [Uptime Kuma](https://uptimekuma.co/), [StatusCake](https://www.statuscake.com/), [Pingdom](https://www.pingdom.com/), and [Tianji](https://tianji.dev/). Built by developers for developers: cheap, four endpoints, 60-second checks on every plan, and **no third-party branding** on the page your users see. We sell the probe. You draw the UI.

This is a [manowar online](https://manowar.online/) product.

## What it does

Built for products that need a status page, a mobile widget, or an internal dashboard — and do not want a competitor’s logo on it, but also don't want to deal with the whole complexity of self-hosting a dedicated VPS or compute server in your cloud just for it. You register URLs. We check them every 60 seconds. You GET JSON reports.



| | |
| --- | --- |
| **Register** | `POST /websites` with a URL. You get a ULID. Same URL you already own is 200, not a duplicate. HTTP redirects are **not** followed: a 3xx is up at the registered URL only. Register the final URL if you need the destination tracked. |
| **List** | `GET /websites` list your sites: status, last check, `last_failure_reason`. Still available if you downgrade past the site cap, so you can recover ULIDs and DELETE until you are under the allowed quantity of tracked websites for your plan. |
| **Reports** | `GET /websites/{ulid}/reports` is 30-day daily by default. `period=24h` is hourly. `include=incidents` adds outages and one-check blips. |
| **Delete** | `DELETE /websites/{ulid}` drops your association. Last owner gone means the website and its history are gone in one commit. Other users monitoring the same URL are untouched. |


## Four calls, four jobs

Identify through {API}Market (`x-api-market-key`). We never ask your end users for an account on our site.

| Call | Job |
| --- | --- |
| `POST /websites` | Start monitoring a URL |
| `GET /websites` | What websites are being tracked? |
| `GET /websites/{ulid}/reports` | 30-day or 24-hour JSON for your UI |
| `DELETE /websites/{ulid}` | Stop. Last owner wipes the data |


## Base URL and authentication

All requests go through the API.market gateway:

```
https://prod.api.market/api/v1/manowar-online/uptydupty
```

Pass your API.market key in the `x-api-market-key` header on every request. No other credential is needed — find your key under **Account → API Keys** on api.market.

```bash
curl -X POST "https://prod.api.market/api/v1/manowar-online/uptydupty/websites" \
  -H "x-api-market-key: YOUR_API_MARKET_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://api.example.com/health"}'
```

The paths below are relative to that base URL — `/websites` becomes https://prod.api.market/api/v1/manowar-online/uptydupty/websites.

## Start

1. **Register a URL.** `POST /websites` with `{"url":"https://api.example.com/health"}`. You get an `id` (ULID) and `check_interval_seconds: 60`.
2. **See what you track.** `GET /websites`.
3. **Render a status page.** `GET /websites/{ulid}/reports`. Add `?period=24h` for hourly buckets. Add `?include=incidents` for `incidents` and `short_incidents`.
4. **Leave.** `DELETE /websites/{ulid}` when you are done.

Site count is the plan gate: BASIC 1, PRO 5, ULTRA 50, MEGA 200. Every plan is checked every 60 seconds. Monthly API unit caps come from your API.market plan. `POST /websites` is also rate-limited to 10 per minute per user (429).

Private and reserved addresses are rejected (literal IPs, `localhost`, and DNS that resolves to a blocked range). Failures are classified: `dns_error`, `tcp_timeout`, `tls_error`, `conn_refused`, `http_4xx`, `http_5xx`, `blocked`, `unknown`.

Uptime is of checks that actually ran (`ok_checks / checks`). No samples is **100%**, not 0% downtime. `coverage_percent_*` is checks / expected minutes so gaps stay visible. Unsampled graph slots are 100% so charts do not plot a fake outage.

## Examples

We provide the JSON. You build the UI however you like.

### Register

```http
POST /websites
Content-Type: application/json

{"url":"https://api.example.com/health"}
```

```json
{
  "id": "01J4Z6XQW9K3M7N2P8RTVBY5HD",
  "url": "https://api.example.com/health",
  "check_interval_seconds": 60,
  "monitored_since": "2026-07-29T00:14:22Z"
}
```

Re-POSTing a URL you already own returns **200** with the same `id`. A new registration is **201**.

### List

```http
GET /websites
```

```json
{
  "websites": [
    {
      "id": "01J4Z6XQW9K3M7N2P8RTVBY5HD",
      "url": "https://api.example.com/health",
      "current_status": "up",
      "last_check_at": "2026-08-29T12:33:01Z",
      "last_check_response_ms": 176,
      "monitored_since": "2026-07-29T00:14:22Z"
    }
  ]
}
```

`last_failure_reason` is omitted when empty. A down site includes it (`http_5xx`, `tls_error`, …).

### 30-day report (default)

```http
GET /websites/01J4Z6XQW9K3M7N2P8RTVBY5HD/reports
```

```json
{
  "website": {
    "id": "01J4Z6XQW9K3M7N2P8RTVBY5HD",
    "url": "https://api.example.com/health",
    "check_interval_seconds": 60,
    "monitored_since": "2026-07-29T00:14:22Z"
  },
  "summary": {
    "uptime_percent_30d": 99.87,
    "uptime_percent_24h": 100.0,
    "coverage_percent_30d": 98.5,
    "coverage_percent_24h": 100.0,
    "avg_response_ms_30d": 184,
    "current_status": "up",
    "last_check_at": "2026-08-29T12:33:01Z",
    "last_check_response_ms": 176,
    "last_incident_at": "2026-08-15T14:03:00Z"
  },
  "daily": [
    { "date": "2026-07-30", "uptime_percent": 100.0, "avg_response_ms": 181, "incidents": 0 },
    { "date": "2026-08-15", "uptime_percent": 99.44, "avg_response_ms": 190, "incidents": 1 },
    { "date": "2026-08-29", "uptime_percent": 100.0, "avg_response_ms": 188, "incidents": 0 }
  ]
}
```

`daily` includes every calendar day in the window. Unsampled days are `"uptime_percent": 100`. `avg_response_ms_*` averages successful checks only.

### Last 24 hours

```http
GET /websites/01J4Z6XQW9K3M7N2P8RTVBY5HD/reports?period=24h
```

```json
{
  "website": {
    "id": "01J4Z6XQW9K3M7N2P8RTVBY5HD",
    "url": "https://api.example.com/health",
    "check_interval_seconds": 60
  },
  "period": "24h",
  "summary": {
    "uptime_percent_24h": 99.65,
    "coverage_percent_24h": 100.0,
    "avg_response_ms_24h": 177,
    "current_status": "up"
  },
  "hourly": [
    { "hour": "2026-08-28T13:00:00Z", "uptime_percent": 100.0, "avg_response_ms": 182 },
    { "hour": "2026-08-28T15:00:00Z", "uptime_percent": 91.67, "avg_response_ms": 171 },
    { "hour": "2026-08-29T12:00:00Z", "uptime_percent": 100.0, "avg_response_ms": 176 }
  ]
}
```

### Incidents

```http
GET /websites/01J4Z6XQW9K3M7N2P8RTVBY5HD/reports?include=incidents
```

A single failed check that recovers on the next check is a **short-incident**. A second consecutive failure promotes the same row to a regular **incident**. `ended_at: null` means it is still open. With `period=24h&include=incidents`, both lists are limited to incidents that overlap the last 24 hours.

```json
{
  "incidents": [
    {
      "started_at": "2026-08-15T14:03:00Z",
      "ended_at": "2026-08-15T14:11:00Z",
      "duration_seconds": 480,
      "reason": "http_5xx",
      "last_status_code": 502
    }
  ],
  "short_incidents": [
    {
      "started_at": "2026-08-29T12:33:00Z",
      "ended_at": "2026-08-29T12:34:00Z",
      "duration_seconds": 60,
      "reason": "http_5xx",
      "last_status_code": 502
    }
  ]
}
```

Without `include=incidents`, both arrays are omitted.

### Errors

A website you do not own is indistinguishable from missing: **404**. Bad JSON, a forbidden URL (private IP, `localhost`), or a bad `period` / `include` is **400**. Create is **429** when you exceed 10 POSTs per minute.

Over the plan site cap: **403** on create and reports. List and DELETE stay open so you can drop sites until you fit.

```json
{
  "status": "plan limit reached",
  "description": "Delete websites until your count fits the current subscription"
}
```

Calls without a valid API.market key are rejected by the gateway before they reach us, with **400** and a message naming the missing header.

## Plans

| Plan | Sites | Price | Monthly API units |
| --- | --- | --- | --- |
| BASIC | 1 | $0 | 1,000 |
| PRO | 5 | $4.99 | 10,000 |
| ULTRA | 50 | $14.99 | 100,000 |
| MEGA | 200 | $29.99 | 200,000 |

Our JSON, your UI. Same 60-second interval on every row.

## Privacy

Uptydupty identifies you through API Marketplace identifiers. We do not save your personal data or create accounts for you, nor do we sell your data to others.

While you monitor a URL, we keep minute buckets (48 hours), daily rollups (31 days), and incidents (31 days after they end). When the **last** associated user DELETEs that URL, the website and all of that history are deleted in one transaction. Deleting only your association leaves the row intact if someone else still monitors the same URL.

OpenAPI: [https://uptyduptyapi.manowar.online/v1/swagger](https://uptyduptyapi.manowar.online/v1/swagger).

## Contact Us

If you have any questions or need support, you can reach out to us through the chat available on this page, or email us at hello@magicapi.com.


60-second uptime checks with no dashboard and no third-party branding. Register URLs, read JSON reports, and build your own status page.

Uptydupty API | API-Only Uptime Monitoring

BASIC

Manowar Online

ULTRA

MEGA

Uptydupty is an API-only monitor for URLs. No dashboard to white-label, no competitor logo on the page your users see. Register a site, read JSON reports...