Does Nuelink have an API?

Yes! Nuelink has a public API. Let's walk through it. 👇

The Nuelink API lets you publish content to every social channel Nuelink supports (Facebook, Instagram, Threads, LinkedIn, Google Business, YouTube, TikTok, Pinterest, X, Mastodon, Bluesky, and Telegram) directly from your own apps, scripts, or workflows. With it, you can:

Push posts to Nuelink from your CMS, e-commerce store, or internal tools.
Build custom automations that fit how you work.
Connect Nuelink to AI assistants and no-code tools.

Note: The Nuelink API is currently in Alpha. This first release focuses on one core workflow: creating posts and uploading media. Listing, updating, and deleting posts will arrive in a later release. Endpoints and response shapes may change before general availability. We'll email registered developers ahead of any breaking changes.

Heads up: Nuelink MCP is coming very soon. It will let AI assistants like Claude or ChatGPT work with your Nuelink account through plain language, no code needed.

Before You Start

To use the Nuelink API, you'll need:

✅ A paid Nuelink account.

✅ At least one brand with a connected channel and a collection.

✅ Your Nuelink API key (we'll generate this in a moment).

If you haven't connected a channel or created a collection yet, do that first from your dashboard. The API publishes posts into a collection, so it needs one to point at.

How to Generate Your API Key

Click your profile icon in the top right corner and open Settings.

In the Settings menu, click the API tab.

Click Generate API Key.

Give your token a Name. and set an Expiration Period. Then click Generate Token.

Copy the key and store it somewhere safe. Treat it like a password and never share it publicly. That's it! Your key is ready to use.

If you ever lose it or think it was leaked, come back to this page and click Revoke to disable it, then generate a new one.

Where and How You Can Use It

The Nuelink API works with anything that can send a web request. You don't need to be a developer to benefit from it. Here are the most common ways people use it:

1. No-code automation tools: Connect Nuelink to platforms like Zapier, Make, n8n, Pabbly Connect, or IFTTT. For example, you can automatically publish a post to Nuelink whenever a new product is added to your Shopify store, a new blog goes live on WordPress, or a new row appears in a Google Sheet.

2. Custom apps and websites. If you (or your developer) are building an internal tool, dashboard, or client portal, the API lets you push posts to Nuelink directly from that app. Great for agencies that want to give clients a simple "publish" button inside their own software.

3. AI assistants and chatbots Pair the API with an AI workflow,w so your assistant can draft and publish posts on your behalf. For example, "Write a caption for our new product launch and schedule it on Instagram for Friday at 9 AM."

4. Scripts and bulk workflows Run a script to upload and schedule dozens of posts at once, sync content from a spreadsheet, or build a custom recurring posting routine.

5. Internal tools for teams: Build a simple form for your team where they can submit content, and it lands directly in your Nuelink Queue, ready for review.

To use the API, you'll send a request that includes your API key in the header like this:

Authorization: Bearer YOUR_API_KEY

That single line authenticates every request, regardless of the tool or language you're using.

How Nuelink is organized

Before your first call, it helps to know the three-level hierarchy the API uses:

Account
└── Brand   (a workspace, e.g., "Fernwood Botanicals")
  ├── Channels   (the connected social accounts: IG, X, TikTok, …)
  └── Collections (content folders grouped by theme or campaign)
    └── Posts  (the social media posts themselves)

Brand — A fully isolated workspace. Each brand has its own channels, collections, and automations.
Collection — A content folder inside a brand. Each collection has a set of default channels and weekly time slots (the Queue).
Channel — A single connected social account, like @yourbrand on Instagram.

So creating a post is always: pick a brand → pick a collection inside it → POST to that collection. You don't pass channel IDs when creating a post — the collection's configuration determines which channels receive it.

Quick example

Here's the full flow, end to end, using curl. Adapt as needed for your language of choice.

Base URL: https://nuelink.com/api/public/v1

1. Verify your token works

curl https://nuelink.com/api/public/v1/me \
-H "Authorization: Bearer YOUR_API_KEY"

2. List your brands and grab a brand ID

curl https://nuelink.com/api/public/v1/brands \
-H "Authorization: Bearer YOUR_API_KEY"

3. List collections in that brand and grab a collection ID

curl https://nuelink.com/api/public/v1/brands/BRAND_ID/collections \
-H "Authorization: Bearer YOUR_API_KEY"

4. (Optional) Upload a media file

Skip this step if your post is text-only.

curl -X POST https://nuelink.com/api/public/v1/brands/BRAND_ID/media \
-H "Authorization: Bearer YOUR_API_KEY" \
-F "media=@./photo.jpg"

5. Create the post

curl -X POST https://nuelink.com/api/public/v1/brands/BRAND_ID/collections/COLLECTION_ID/posts \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"caption": "Hello from the Nuelink API 👋",
"publishMode": "IMMEDIATE",
"media": [{ "id": "MEDIA_ID_FROM_STEP_4" }]
}'

You'll get back a post ID, and the post will be pushed to every channel in the collection.

Rate limits

The current limit is 30 requests per minute per API key, across all endpoints. Every response includes three headers that show where you stand:

x-ratelimit-limit — max requests allowed in the current window
x-ratelimit-remaining — requests you have left
x-ratelimit-reset — seconds until the window resets

If you hit the limit, you'll get a 429 Too Many Requests. Back off until x-ratelimit-reset elapses, then retry.

Keep Your API Key Secure

Your API key works like a password. A few habits to keep things safe:

Treat it like any other credential. Never commit it to a public repo or paste it into a shared chat.
Only share it with tools and services you trust.
If you suspect it's been exposed, revoke it from the API settings page and generate a new one. The old key will stop working immediately.

Where to Go Next

This article is an express tour. For the full reference (every endpoint, every parameter, platform-specific options like first comments, threaded posts, Reels vs. carousels, error codes, and pagination), head over to our developer docs:

👉 docs.nuelink.com

If you run into anything unexpected or have feedback on the alpha, we'd love to hear from you at [email protected].