Short-lived by default
PINs expire after 5 minutes, 10 minutes, 15 minutes, 30 minutes, 45 minutes, or 1 hour, so they are useful for quick connection flows without becoming permanent identifiers.
FriendlyPIN beta
FriendlyPIN turns IPv4 or IPv6 addresses into temporary connection PINs for quick setup flows, support calls, and pairing screens. Create a PIN, share it, and let it expire automatically.
Every request creates a new PIN and also shows any still-active PINs for the same IP with their remaining time. Each IP can keep up to 5 active PINs at once.
Try it now
Example use
FriendlyPIN beta works well when the code only needs to last through one setup session. Pick an expiration from 5 minutes to 1 hour.
Use the form above to generate a real FriendlyPIN — this example updates once you create one.
How it works
PINs expire after 5 minutes, 10 minutes, 15 minutes, 30 minutes, 45 minutes, or 1 hour, so they are useful for quick connection flows without becoming permanent identifiers.
Use one temporary PIN flow for either address family. The resolver returns the original IP and shows how long the PIN remains active.
Each address can have up to 5 active PINs at a time. When you create a new PIN, FriendlyPIN also lists previous active PINs for that same address so users know what is still valid.
Code lengths
FriendlyPIN uses 4-character codes first, then shorter codes, and only moves to 8+ if the temporary pool is exhausted.
IPv6 lookup codes use 5 characters first, then 7+ characters. They never use PIN lengths or the IPv4 length.
IPv4 FriendlyIP codes remain exactly 6 characters and can still be calculated locally without any online service.
For developers
POST https://friendlyip.com/api/pin/create/index.php
Send { "ip": "42.13.37.67", "duration_seconds": 900 }
or an IPv6 address. Duration can be 300, 600, 900, 1800, 2700, or
3600 seconds. The API returns the new PIN plus any previous active
PINs for that same IP, up to 5 active PINs at once.
POST https://friendlyip.com/api/pin/resolve/index.php
Send { "pin": "2222" } and the API returns the
original IP and how long the PIN has left. Expired PINs are
rejected.
Dedicated SaaS
Want FriendlyPIN tuned to your product? PyroSoft can spin up a dedicated FriendlyPIN endpoint under your own URL slug, with a PIN length, expiration window, and PIN pool that match your workflow. The public API stays free for indie use — this is a paid add-on for teams that need their own pool.
Pick a slug like
friendlyip.com/yourcompany/api. Every PIN endpoint
lives under that prefix so your integration feels branded and
stays separate from the shared pool.
Default to 3, 4, 5, 6, or 8+ character PINs to balance human-friendliness against how many can be active at once. We pick the allocator that fits your chosen default.
Pick how long PINs stay valid, from 5 minutes up to 7 days. Quick support codes, all-day pairing sessions, or anything in between.
Your PINs live in a dedicated pool so your traffic never competes with the public FriendlyPIN pool, and short PINs stay available for your users.
Contact to set up
Dedicated endpoints are a paid add-on from PyroSoft Productions. Reach out with your preferred slug, default PIN length, and expiration window, and we will get your namespace live.
Example shape of a dedicated endpoint once provisioned:
POST https://friendlyip.com/yourcompany/api/pin/create/index.php