Skip to main content

Connect a profile, create a key, send a test post and drop the SDK into your app — in 30 seconds.

Before you begin

You need a Nylon account with at least one connected social profile.
  1. Open Connections and connect a profile.
  2. Open API keys.
  3. Select Create key, give the key a recognizable name, and copy it.
Nylon only displays a newly created API key once. Store it in your secret manager and never commit it to source control.

Use the SDK, or raw HTTP

Every step below is shown in curl, Node and Python so you can follow it in any stack. If you are on TypeScript or JavaScript, the official SDK does the same thing with retries that cannot double-post, typed errors and webhook verification already handled:

TypeScript SDK

Installation, resources, error handling and configuration.

1. List your profiles

A post is addressed to profile ids, so this is where every integration starts.
Response

2. Check the post before you send it

POST /v1/validate takes the same body as a publish and tells you what every addressed network thinks of it — including how a long caption will be split into a thread. Nothing is published.
cURL

3. Publish

Same body, real endpoint.
Publishing is synchronous. The request returns once every target has been attempted, so a carousel or a video can take a while — allow a generous client timeout. What you get back is the outcome, not a job id to poll.
Response
To schedule instead, send scheduled_at with an ISO 8601 time in the future. The response is the same shape with status: "scheduled" and targets still pending.

4. Handle a partial failure

A post can succeed on one network and fail on another. That is not an error response — the post exists, and status is partially_published. Read the reason off each target and retry only what failed:
cURL
Targets that already published are never re-sent, whatever you ask for.

Next steps

Network capabilities

Character limits, media specs and per-network options, as data you can check against.

Publishing

The model: accounts not networks, one payload many targets.

Errors

The taxonomy, per-network failure details and rate limits.

API reference

Every endpoint, with a playground.