Narrareach Logonarrareach.

social media scheduling API

A Social Media Scheduling API For Writer-Led Publishing Workflows

Ian Kiprono

At a glance

Social media scheduling API for publishing workflows

Schedule posts across supported platforms from your own tools while Narrareach handles queue state, platform connections, retries, webhooks, and reporting.

Read the API docsSee posting API workflow
  • Bearer-token API access: so your own app or script can make authenticated REST calls to Narrareach
  • Notes endpoints: so external tools can create, schedule, reschedule, and delete publishing jobs
  • Webhook delivery: so downstream systems can react when a Note is published or updated
  • Platform-aware scheduling: so API-created Notes still use the same Substack, LinkedIn, X, Bluesky, and Threads scheduling workflow

What this page covers

What a content scheduling API lets you buildAuthentication and getting startedIntegration patterns for common tools

Built for authenticated scheduling workflows with queue visibility.

The problem

The manual version gets old fast.

A scheduling API has to do more than accept a timestamp. It needs to preserve platform-specific copy, timezone handling, media attachments, publish retries, and delivery status.

Narrareach lets external tools schedule content into a queue that writers can still review, edit, and connect to subscriber and performance outcomes.

What a content scheduling API lets you build

A content scheduling API turns your own tools into publishing triggers. Instead of switching to a social scheduler to post the content your system already produced, your code calls an endpoint and the publishing happens. Google Sheets content calendars, CMS workflows, customer success dashboards, and automation builders like Zapier, Make, or n8n can all hand off the last mile to an API.

Narrareach exposes REST endpoints for creating, scheduling, rescheduling, and deleting Notes. Your tool authenticates with a bearer token, sends the note text, platform selections, and schedule time, and Narrareach handles API delivery to Substack, LinkedIn, X, Bluesky, and Threads. You do not need to manage individual platform OAuth sessions in your own code.

Webhooks close the feedback loop. When a Note publishes or fails, Narrareach sends an event payload to your endpoint — so your Telegram channel, reporting database, or downstream automation can react in real time without polling.

  • Start with a simple workflow: one API call from a Google Sheet or Zapier to schedule a single Note, then expand
  • Use webhooks to log publish events in your own database for reporting or triggering follow-up actions
  • Keep platform connections in Narrareach so your scripts never handle social media OAuth directly

Authentication and getting started

The Narrareach API uses bearer token authentication. Generate an API token in your Narrareach account settings, then pass it in the Authorization header of every request. This approach works with any tool that can make HTTPS requests — Google Apps Script, Python scripts, Node.js backends, Zapier custom requests, n8n HTTP nodes, and Make HTTP modules.

The core workflow is three steps: create a Note with the text and optional image URL, set the API-supported platform targets (Substack, LinkedIn, X, Bluesky, and Threads), and specify a schedule time in ISO 8601 format. A single API call handles all three. For updates, use the reschedule endpoint with the Note ID and new time. For cancellations, use the delete endpoint.

Rate limits are designed for automation, not abuse. Typical batch operations — scheduling 30 to 50 Notes at once — complete well within limits. If you are building a tool that creates content on behalf of multiple users, contact the team for higher-volume access.

  • Store your API token as an environment variable or secret — never hardcode it in scripts or spreadsheets
  • Test with a single scheduled Note before building a full batch pipeline
  • Use ISO 8601 timestamps with timezone offset to avoid scheduling in the wrong timezone
  • Check the API docs at /api-docs for complete endpoint documentation and example requests

Integration patterns for common tools

Zapier and Make integrations use the Narrareach API through custom webhook or HTTP request steps. Set the trigger (new row in Google Sheets, new item in Airtable, new event in your CMS), map the content fields to the Narrareach API payload, and the Note schedules automatically when the trigger fires.

For n8n users, the HTTP Request node calls the Narrareach API directly. n8n workflows can add conditional logic — schedule to LinkedIn only on weekdays, skip Threads for articles over 300 characters, or route different content types to different platform combinations.

Google Apps Script is particularly powerful because many content calendars already live in Sheets. A simple script can read rows from a content planning spreadsheet, call the Narrareach API for each row, and update a status column when the Note is scheduled. The script runs on a timer or on edit, keeping your calendar and publishing queue in sync without any manual intervention.

  • In Zapier or Make, use the "Custom Request" or "HTTP" module with your bearer token in the header
  • Add error handling to retry failed API calls — network glitches should not break your publishing pipeline
  • Log API responses in a separate sheet or database table for debugging and audit trails
  • Use webhook payloads to update your content calendar status automatically when Notes publish

How Narrareach solves it

Keep the publishing system close to the writing.

Bearer-token API access - so your own app or script can make authenticated REST calls to Narrareach

Notes endpoints - so external tools can create, schedule, reschedule, and delete publishing jobs

Webhook delivery - so downstream systems can react when a Note is published or updated

Platform-aware scheduling - so API-created Notes still use the same Substack, LinkedIn, X, Bluesky, and Threads scheduling workflow

Start here

Schedule publishing jobs from your own tools

Built for authenticated scheduling workflows with queue visibility.

Read the API docs

Questions writers ask

Can I call Narrareach from Zapier, Make, n8n, or Google Apps Script?

Yes. If the tool can make HTTPS requests and set an authorization header, it can call the Narrareach REST API with your API token.

Do platform accounts still need to be connected in Narrareach?

Yes. The API creates and manages publishing work in Narrareach. Your API-supported Substack, LinkedIn, X, Bluesky, and Threads connections still live in your Narrareach account.

What authentication method does the Narrareach API use?

Bearer token authentication. Generate an API token from your Narrareach account settings and include it as an Authorization header on every request.

Can I use the API to schedule Notes to multiple platforms simultaneously?

Yes. The scheduling API accepts a platforms array so a single request can schedule a Note to Substack, X, LinkedIn, Bluesky, and Threads at specified times.

Is there API documentation available?

Yes. Full API and MCP connector documentation is available at narrareach.com/api-docs, including endpoint references, authentication guides, and example requests.

Can I use the API to read analytics data?

Yes. The API exposes analytics endpoints for subscriber counts, post performance, and attribution data — useful for building custom dashboards or feeding data into your own reporting tools.

Is there a rate limit on the Narrareach API?

Rate limits apply per plan. Paid plan limits are sufficient for typical automation workflows including bulk scheduling and daily analytics polling. Contact support if you need higher limits for enterprise use.

Narrareach LLM connector

Connect Claude, ChatGPT, or any MCP-compatible agent to read drafts, schedule posts, and automate Substack, Medium, LinkedIn, X, Bluesky, and Threads workflows.

Read the docs