Nuelink API FAQs
Does Nuelink have an API?
Yes! Nuelink has a public API that 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. The API is currently in Alpha, with the first release focused on creating posts and uploading media. For full details, see our main API guide and the developer docs at docs.nuelink.com.
Do I need to be a developer to use the API?
Not necessarily. If you can use no-code tools like Zapier, Make, n8n, or Pabbly Connect, you can paste your Nuelink API key into those tools and connect Nuelink to other apps without writing code.
Where can I find the full developer documentation?
The full reference, including every endpoint, parameter, error code, and platform-specific option, lives at docs.nuelink.com.
What plans include the API?
The API is available on all paid plans during the Alpha and Beta stages. We may update this later as we move toward general availability, so keep an eye on your API settings page for any plan-related changes.
I don't see the API tab in my Settings. What should I do?
Make sure you're on a paid plan. If you're on a paid plan and still don't see it, reach out to [email protected], and we'll help you get set up.
How do I get my API key?
Head to nuelink.com/settings/api, click Generate API Key, choose how long you'd like the key to stay active, and copy it somewhere safe.
How long does an API key stay active?
You choose! When you generate a key, you can set its expiration anywhere from 30 days up to 1 year. This gives you flexibility to rotate keys on a schedule that matches your security needs.
Can I revoke an API key?
Yes. Open your API settings page, find the key, and click Revoke. The key stops working right away. You can generate a new one from the same page.
How do I keep my API key safe?
Treat it like a password. Don't commit it to a public repo, don't paste it into shared chats, and only share it with tools you trust. If you ever think it's been exposed, revoke it and generate a new one.
What does the Alpha release include?
The current Alpha lets you list your brands, collections, and channels, upload media files (images, videos, PDFs), and create posts. You can publish immediately, schedule for a specific time, add to your Queue, or save as a draft.
Can I list, edit, or delete posts I've already created?
Not yet. Listing, updating, and deleting posts will arrive in a later release. We'll email registered developers as soon as those endpoints are available.
Can I pick which channels in a collection receive a post?
Not in this Alpha release. Posts go to every channel attached to the collection you choose. If you need a different mix of channels, create a new collection with just those channels. Channel-level targeting is on the roadmap.
What's the rate limit?
The current limit is 30 requests per minute per API key, across all endpoints. Every response includes x-ratelimit-limit, x-ratelimit-remaining, and x-ratelimit-reset headers so you can track your usage.
What is Nuelink MCP? Nuelink MCP is coming very soon.
MCP (Model Context Protocol) lets AI assistants like Claude or ChatGPT connect to your Nuelink account and work with it through plain language, no code or workflows needed. We'll publish a dedicated guide as soon as it's ready, and you can read more here: Nuelink MCP article (coming soon).
Will MCP replace the API?
No. MCP and the Public API serve different needs. The API is best for custom apps, scripts, and no-code automation tools. MCP is built specifically for AI assistants. Most users will use one or the other depending on the use case, and many will use both.
I found a bug or have a feature request. Where should I send it?
We'd love to hear from you. Email [email protected] with bugs, questions, or feature requests. Alpha feedback directly shapes the final release.
How will I know about breaking changes?
During Alpha and Beta, we'll email registered developers ahead of any breaking changes so you have time to update your integrations.