API Documentation

Build powerful integrations with the PLTO.IN Edge Engine.

1. Overview

The PLTO.IN API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

Because our API is deployed on Cloudflare Workers, you can expect global response times of under 50ms regardless of where your servers are located. This makes PLTO.IN the perfect infrastructure to integrate into real-time applications like SMS gateways, email marketing software, or the Eynni AI coding environment.

2. Authentication

The PLTO.IN API uses API keys to authenticate requests. You can view and manage your API keys in the Developer Settings section of your Dashboard.

Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.

Authorization: Bearer YOUR_SECRET_API_KEY

3. Shorten a Link (POST /api/v1/links)

This endpoint creates a new shortened link. It interacts directly with our Cloudflare KV store for instant routing availability.

Request Body

  • long_url (string, required): The destination URL you want to shorten.
  • domain (string, optional): Your custom domain. Defaults to 'plto.in'.
  • custom_alias (string, optional): A specific string you want to use instead of a random hash (e.g., 'summer-sale-26').

Example Request

curl -X POST https://api.plto.in/v1/links \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "long_url": "https://litora.in/very/long/article/path",
    "custom_alias": "plto-article"
  }'

Example Response

{
  "id": "link_8a7f9c2b",
  "short_url": "https://plto.in/plto-article",
  "long_url": "https://litora.in/very/long/article/path",
  "created_at": "2026-05-28T12:00:00Z"
}

4. Retrieve Analytics (GET /api/v1/links/{id}/analytics)

Retrieve aggregated, privacy-preserving analytics for a specific link. Due to the high volume of clicks, analytics data is synced from the edge to our D1 database every 60 seconds.

5. Rate Limits

To prevent abuse, the API enforces rate limits. Free tier users are limited to 100 requests per minute. Business tier users have expanded limits up to 10,000 requests per minute. If you exceed the rate limit, the API will return a 429 Too Many Requests status code.