Duck Service API

REST · v2 · HTTPS only

Request-based data access, without the plumbing.

Authenticate once, then fetch versioned resources over a plain HTTPS request. Predictable responses, no SDK required.

Operational 99.95% 30-day uptime v2 current
example request
# fetch a resource by id
GET https://api.duckserviceapi.top/v2/{resource}
Authorization: Bearer <your-token>
Accept: application/json

# 200 OK
{
  "version": "v2",
  "resource": "gitjpc8gk5y6ogxq",
  "status": "active"
}

Quickstart

Three steps to your first response

Every request is a single authenticated call against the /v2/ namespace. No client library, no handshake.

01

Create a token

Generate a bearer token from your dashboard. Tokens are opaque strings scoped to one project.

02

Call an endpoint

Send a request to /v2/{resource} with your token in the Authorization header.

03

Read the response

Resources return as UTF-8 payloads over HTTPS. Cache them client-side and refresh on your own schedule.

Reference

v2 endpoints

All routes live under /v2/. Resource identifiers are opaque tokens; treat them as case-sensitive.

GET /v2/{resource} Fetch a single resource by token
GET /v2/lookup Resolve a resource by query params
POST /v2/batch Request several resources at once
GET /v2/status Service health and version info

Pricing

Straightforward tiers

Usage is metered per request. Upgrade or cancel any time from the dashboard.

Starter

$0/mo
  • 1,000 requests / month
  • Single token
  • Community support

Standard

$12/mo
  • 100,000 requests / month
  • Up to 10 tokens
  • Email support

Scale

$49/mo
  • Unmetered requests
  • Unlimited tokens
  • Priority support

Status

All systems operational

Real-time health for the /v2/ API. Last checked a few moments ago.

API api.duckserviceapi.top Operational
EDGE /v2/ routing Operational