One API for every social platform
Publish, schedule and read across 22 networks through a single REST endpoint. Our OAuth apps, our platform reviews, our rate limits — you ship the feature, not 22 integrations.
POST/v1/posts
{ "accounts": ["acc_instagram_8f2", "acc_x_31a"], "content": { "text": "Nylon v1 is live — one API, every network.", "media": ["https://cdn.example.com/launch.mp4"] }, "publish_at": "2026-09-04T09:00:00Z"}Posts published
Reel · 1080×1920
X
Post · 280 chars
Company page
22 social networks, live on one contract
FacebookInstagramX (Twitter)LinkedIn
Pinterest
Threads
TikTok
YouTube
Google Business
Discord
Slack
Telegram
Bluesky
Mastodon
Dribbble
Kick
Twitch
Whop
DEV.to
WordPress
Tumblr
CustomShipping the first integration takes a week. Keeping 22 of them alive is a job.
Nylon puts 22 networks, a media pipeline and every OAuth flow behind a single endpoint — running on apps we register, submit for review and keep in good standing.
When a network changes its API, and one of them always is, the fix ships behind the same contract. Nothing in your code moves.
You have a product to build. Not 22 changelogs to read.
It starts with one endpoint
POST once and Nylon fans the payload out to all 22 live networks — on our OAuth apps, our platform reviews and our rate limits. No developer accounts to register, no approval queues to sit in.
one request
Connections, handled
Send a user to one connect URL and get back an account id. Every OAuth flow, token refresh and re-auth prompt runs on our apps.
Per-network normalisation
Character limits, media specs, threading rules and error taxonomies are handled before your request ever reaches a platform.
Media pipeline included
Upload once. Nylon transcodes video, fixes aspect ratios, generates thumbnails and handles resumable and chunked uploads.
Ocoya schedules posts for thousands of brands, and every network we supported used to be its own integration to build and then babysit. Running it all through Nylon turned that into one endpoint — my team ships features now instead of chasing platform API changes.
Aivaras TumasCEO, OcoyaEvery conversation in one thread
Messages arrive on a single conversation resource with one shape, and replies go back out through the same call. Live on Telegram today — the resource is built so the remaining networks slot in behind it without changing your code.
@lena.buildsDM
does this work with scheduled posts too?
Tom ReesGroup
Is there a sandbox we can test on?
@sofia.mDM
Can we get a demo this week?
201 · reply delivered to telegram
One message shape
A Telegram DM and a group message arrive as the same object, with the same author, thread and timestamp fields — and so will every network we add.
Reply as the brand
Post a reply back into any thread through the same resource. Threading and per-network reply rules are handled for you.
Nothing gets missed
Poll the thread list for unread conversations. Read state is tracked per thread so two agents never answer the same message twice.
Measure what matters
Every network reports differently — different metric names, different windows, different pagination. Nylon normalises them into one response shape, so a chart you build once works everywhere.
Impressions
2.41M
+18.2%
Engagement rate
4.8%
+0.6pt
Follower growth
+12.9K
+7.1%
Link clicks
38.4K
+22.5%
One schema everywhere
Impressions, reach, engagement, follower growth and link clicks under the same field names on every network.
Per post and per account
Query a single post’s performance or an account’s trend over any window, without learning a second pagination model.
No extra line item
Analytics is part of the per-account price when it ships. There is no add-on to switch on and no separate meter.
Connect once, publish everywhere
Send a user to one connect URL and get an account id back. Nylon owns the OAuth app, the refresh cycle and the re-auth prompt for every network on this wall — and the wall keeps growing.
Outgrown our keys? Bring your own.
Every account runs on Nylon-managed OAuth apps by default, and most teams never change that. When you need your own — your brand on the consent screen, your quota on your throughput — swap the credentials for any provider and keep every endpoint identical.
- Your app on the consent screen
- Your rate limits, not a shared pool
- Switch one provider at a time
- Connections keep working through the swap
Existing connections keep working through the swap.
Built to scale
The publishing engine behind Nylon has run in production since 2022. It is boring on purpose: fast, dull, and it scales with you rather than with your plan.
0
0ms
0.00%
0 min
Or you could build it yourself
Nothing here is impossible to write. It is just 22 OAuth flows, a dozen media specs and a standing on-call rota for other companies' API changes.
| With Nylon | Building it in-house | |
|---|---|---|
| Time to first published post | Minutes — one API key, one POST | Weeks per network, before platform review |
| Developer accounts to register | None. Every network runs on our OAuth apps | One per platform, each with its own review |
| OAuth flows to maintain | One connect URL | 22 flows, plus refresh and re-auth for each |
| Media handling | Transcoding, aspect ratios and resumable uploads included | A different spec and upload protocol per network |
| When a platform changes its API | We ship the fix behind the same contract | Your on-call problem, usually without notice |
| Ongoing cost | Per connected account, from $0 | Engineer time, indefinitely |
| Control over credentials | Ours by default, yours whenever you want them | Yours, along with everything else |
Pay per connected account. Nothing else.
One plan, no tiers to compare. Drag the slider to see exactly what you would pay — the first two accounts are always free.
- Every live platform
- Managed OAuth apps — nothing to register
- Unlimited posts and scheduling
- Inbox on Telegram
- Media pipeline and transcoding
- Analytics, included when it ships
- Bring your own keys when you need to
- No seats, no post caps, no add-ons
- Prorated daily — connect and disconnect freely
Included networks
All 22 networks are billed at the same per-account rate.
Your monthly cost
$4.80 per account, blended.
Prorated daily. Cancel or resize any time.
| The whole product | What it costs |
|---|---|
| Connected accounts10 accounts = $48/mo | |
| First 2 accountsFree forever. No card, no trial clock. | Free |
| Accounts 3 – 10Slider is hereOnly the accounts inside the band are billed at this rate. | $6per account / month |
| Accounts 11 – 100Crossing a boundary never re-prices the accounts below it. | $3per account / month |
| Accounts 101+No cap and no sales call — self-serve at any volume. | $1per account / month |
| PublishingIn the per-account price | |
| Posts and schedulingImmediate or scheduled publishing, threads, first comment, retries on platform failure. | Unlimited |
| Platform coverageAll 22 live networks, on OAuth apps we own and keep in review. | Every network |
| Media pipelineVideo transcoding, aspect-ratio correction, thumbnails, resumable and chunked uploads. | Included |
| Per-network normalisationCharacter limits, media specs, threading rules and error taxonomies handled for you. | Included |
| InboxIn the per-account price | |
| Direct messagesRead and reply through one message resource. Telegram today; more networks in build. | Telegram |
| Channels and groupsThe same object shape as a DM, with thread, author and timestamp fields that always agree. | Telegram |
| AnalyticsIn the per-account price | |
| Normalised metricsImpressions, reach, engagement, follower growth and link clicks under one set of field names. | Included at launch |
| Per post and per accountQuery one post’s performance or an account’s trend over a window, on the same pagination model. | Included at launch |
| API and keysIn the per-account price | |
| API requestsNo per-call metering and no request quota to buy — publish, read and poll as much as you need. | $0 / request |
| Bring your own keysYour Meta, X, LinkedIn or Google app on any provider, from the free tier up. | Every provider |
| Token managementOAuth handshakes, long-lived token exchange, refresh cycles and re-auth prompts. | Included |
| SDKs and OpenAPI specTypeScript and Python SDKs, plus a spec to generate your own client from. | Included |
| SandboxTest keys that exercise the full request contract without touching a live account. | Included |
| Team and billingIn the per-account price | |
| TeammatesInvite as many people as you like. Nylon has never had a per-seat price. | Unlimited |
| ProrationConnect and disconnect freely — accounts are billed by the day they were connected. | Daily |
| Minimum termCancel or resize without a notice period, an email thread or a sales call. | Month to month |
| Support and complianceIn the per-account price | |
| SupportEmail support from the engineers who build the API, at every volume including free. | Included |
| Data residencyProduction infrastructure runs in the United States (Virginia). The operating company is established in the EU. | US — Virginia |
| GDPR and DPAData processing agreement, subprocessor list and transfer mechanisms on the GDPR page. | Included |
Connected accounts are the only line on a Nylon invoice. There is no request metering, no seat count and no add-on to switch on later — if that ever changes, it will appear on the table above with a price next to it.
Questions developers actually ask
What exactly is BYOK?
Bring Your Own Keys. Instead of routing calls through Nylon’s platform apps, you paste your own client id and secret for a provider — your Meta app, your X project, your LinkedIn app — and Nylon uses it for OAuth and for every subsequent request. Your users see your brand on the consent screen and your app owns the rate limit.
Do I need my own developer apps to start?
No. Every provider works out of the box on Nylon-managed apps, so you can build the full integration before you have gone through a single platform review. Switch a provider to your own keys later from the dashboard — existing connections keep working.
How is this different from calling the platform APIs myself?
Eleven OAuth flows, a dozen media specs, resumable uploads, token refresh, per-network character limits, rate-limit back-off and error taxonomies — that is the work. Nylon is one REST contract instead.
What counts as a connected account?
One authorised destination: a Facebook Page, an Instagram Business profile, an X handle, a LinkedIn company page, a Discord channel. Connect and disconnect whenever you like — billing prorates by the day.
Is there an SDK?
The API is plain REST over HTTPS with JSON, so any HTTP client works. Typed SDKs for TypeScript and Python are published alongside the docs, and an OpenAPI spec is available if you generate your own.
Which networks does the inbox cover?
Telegram today — channels, groups and direct chats, read and replied to through one message resource. The other networks are in build behind the same resource, so adding them will not change the shape of your code. Publishing, by contrast, is live on every network listed on the platforms page.
When does analytics ship?
It is in build and not available yet — nothing in the API returns analytics today. The first release will cover impressions, reach, engagement and follower growth on one normalised schema, per post and per account, at no extra cost: it is part of the per-account price.
Where is data stored?
Production infrastructure runs in the United States, in Virginia. The operating company is established in the European Union. We are a processor for the content you publish through us — see the DPA on our GDPR page for the full detail, including subprocessors and the transfer mechanisms that apply.
I am migrating from another social API. How hard is it?
Endpoints map closely to what you already have: create a connection, list accounts, create a post, read the message queue. Most teams move in a day. Email us and we will read your integration with you.
Ship social publishing this week
Two connected accounts free forever. Every network, every endpoint, nothing to register — no card, no sales call.