How to Schedule Social Media Posts with an API (No-Code and Code Examples)

There are two real ways to schedule a post through an API: writing the request yourself, or letting a no-code tool make the request for you. Both end up calling the same underlying API. The difference is how much of the wiring you do by hand.

The no-code route

If you don't want to write code, automation platforms like Zapier can connect a scheduler to other apps and trigger posts from some other event: a new row in a spreadsheet, a new item in a CMS, a webhook from another app. You configure a trigger and an action, and the platform makes the API call for you.

This works well for simple, event-based scheduling. It gets harder to manage once you need conditional logic, bulk operations, or custom error handling.

The code route

Calling the API directly gives you full control, at the cost of writing and maintaining the integration. With OneUp, a request has three parts: the base URL (https://www.oneupapp.io/api/), an endpoint for the kind of post, and your API key passed as an apiKey query parameter.

Here's a text post scheduled with curl, using the format from OneUp's reference:

curl -G -X POST "https://www.oneupapp.io/api/scheduletextpost" \
  --data-urlencode "apiKey=$ONEUP_API_KEY" \
  --data-urlencode "category_id=49839" \
  --data-urlencode 'social_network_id=["123456789","987654321"]' \
  --data-urlencode "scheduled_date_time=2026-12-25 14:00" \
  --data-urlencode "content=Your post text here"

What each piece means:

• category_id: the category that holds the accounts you want to post to
• social_network_id: a JSON array of account IDs, or "ALL" for every account in the category
• scheduled_date_time: publish time in YYYY-MM-DD HH:MM format
• content: the post text

You get the category and account IDs from OneUp's list-categories and list-category-accounts endpoints. For images and video, use /api/scheduleimagepost (with an image_url) or /api/schedulevideopost (with a video_url). Because the key travels in the URL, store it in an environment variable and keep it out of logs.

The full list of endpoints and parameters is in the reference at docs.oneupapp.io, which is worth working from directly.

Where OneUp fits both approaches

OneUp supports the code route with its REST API and API key, which you generate on the API Access page. For something in between, its MCP server lets you connect AI tools like Claude, ChatGPT, or Grok and schedule posts by prompting in natural language, with no hand-written requests.

Choosing between them

• No-code fits simple, event-driven scheduling where you'd rather not maintain code.
• The direct API fits custom logic, bulk operations, or scheduling built into a larger product.

Ready to see the endpoints? Check out OneUp's API documentation.