> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nylon.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Publishing

> Post to every connected network through one request shape.

<div className="pillar-hero" data-pillar="publishing">
  <span className="pillar-hero__mark">
    <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="1.8" strokeLinecap="round" strokeLinejoin="round">
      <path d="M4 12 20 4l-8 16-2-6-6-2Z" fill="currentColor" stroke="none" />
    </svg>
  </span>

  <div className="pillar-hero__body">
    <span className="pillar-hero__eyebrow">Pillar 1 of 3</span>
    <p>One request, fanned out to every connected account. Media requirements, character limits and threading rules are normalised before the request reaches a platform.</p>
    <span className="pillar-status pillar-status--live">Live on 12 networks</span>
  </div>
</div>

## The model

Publishing is built around two ideas:

<CardGroup cols={2}>
  <Card title="Accounts, not networks" icon="plug">
    You address a post to connected account ids. Nylon already knows which network each one belongs to and what that network accepts.
  </Card>

  <Card title="One payload, many targets" icon="send">
    The same content object is adapted per target rather than being written per target by you.
  </Card>
</CardGroup>

## What gets normalised for you

| Concern          | Handled by Nylon                                     |
| ---------------- | ---------------------------------------------------- |
| Character limits | Validated per network before the request is accepted |
| Media specs      | Transcoding, aspect-ratio correction and thumbnails  |
| Uploads          | Resumable and chunked uploads per network's protocol |
| Threading        | Per-network reply and thread semantics               |
| Errors           | Mapped to one error taxonomy — see [Errors](/errors) |

## Supported networks

Publishing is live on all twelve networks listed on the [Connections](/connections) page. Capabilities vary by network and account type — a Facebook Page accepts Reels, an X handle accepts threads — and the per-network detail is listed there.

<Note>
  Endpoint reference for publishing is not in these docs yet. The only endpoint currently documented and playground-backed is [`GET /v1/profiles`](/api-reference/list-profiles). See [API reference](/api-reference) for what is available today.
</Note>

<Card title="Connections" icon="plug" href="/connections">
  Understand connected profiles and connection statuses before you publish to them.
</Card>