We built Plung on a simple principle: core web utilities should be fast, open, and free of unnecessary barriers. Today, we are extending that same principle to developers. The Plung public API is now fully documented and ready for production use.
Whether you are building a SaaS product that needs on-the-fly link shortening, a marketing automation pipeline that tracks click performance, or a weekend side project that just needs a quick way to generate short URLs, the Plung API is here to make your life easier.
What You Can Do
The API exposes three endpoints. That is not a limitation — it is a deliberate design choice. We did not ship a sprawling surface area of half-finished features. We shipped three endpoints that are stable, performant, and do exactly what they say.
Shorten a URL. Send a single POST request with a long URL and receive a shortened link instantly. Optionally, set a custom alias, a password, an expiration window, or a maximum click limit. Every URL is validated against Google Safe Browsing before it is accepted.
Get link statistics. Query any short code to retrieve its total click count, creation date, last access time, and any configured expiration or click limits. This is the data you need to build dashboards, track campaign performance, or simply monitor how your links are performing.
Generate QR codes. Request a QR code for any short code in PNG or SVG format and use the same canonical renderer that powers the product experience.
API Keys and the Developer Console
The current developer API uses API keys issued through the Developer Console. You create a key once, send it in the Authorization: Bearer ... header, and then work entirely against the authenticated /v2 surface.
Rate limits and monthly quotas are enforced per API key based on your plan, which makes production integrations far more predictable than shared IP-based limits.
Documentation You Can Actually Read
We did not just ship endpoints and call it a day. We wrote documentation the way we believe it should be written: precise, technically honest, and useful from the first paragraph.
Every endpoint is documented with its full URL, a plain-English description of what it does, a complete parameter table with types and validation rules, request examples in both cURL and JavaScript, the exact JSON structure of every success response, and a table of every possible error with its status code and message.
The documentation lives at plung.co/product/developers and features a sticky sidebar for navigation, syntax-highlighted code blocks with one-click copy, and a clean light-mode reading experience.
Built for Developers Who Ship
We know what it is like to integrate with an API that has vague documentation, undocumented error codes, and response shapes that change between requests. We have been on the receiving end of that experience enough times to know exactly what not to do.
Every error message in the Plung API tells you exactly what went wrong and how to fix it. Every response field is documented with its type and what values to expect. Every parameter description explains what happens if it is missing. There are no surprises.
Start Building Today
The API is live right now. Open your terminal and run:
curl -X POST https://api.plung.co/v2/shorten \
-H "Authorization: Bearer your_api_key_here" \
-H "Content-Type: application/json" \
-d '{"url": "https://example.com"}'
That is your first integration. It takes one request, one API key, and only a few seconds to get started.
Read the full documentation at plung.co/product/developers and start building.
Written by
Plung Team