Video Automation
DESign inStart free trial

Switching from Upload-Post

Move Upload-Post scripts, n8n workflows and Make scenarios to Video Automation: swap base URL and key, recreate profiles, reconnect accounts, checklist.

Our API speaks the same endpoints, form fields and responses as Upload-Post. In most cases you change two things – the base URL and the API key – and your scripts keep running.

What changes

- https://api.upload-post.com/api/upload
+ https://my-video-automation.com/api/upload

  Authorization: Apikey YOUR_NEW_KEY

Everything after the host stays the same: /api/upload, /api/uploadposts/users, /api/uploadposts/status and so on. Create the new key under API & webhooks (API and keys).

What is supported

  • Publishing: POST /api/upload, /api/upload_photos, /api/upload_text, /api/upload_document (LinkedIn documents) – sync, async_upload and scheduled_date with timezone
  • Status and history: GET /api/uploadposts/status, /api/uploadposts/history
  • Scheduled posts: GET, PATCH, DELETE /api/uploadposts/schedule/{job_id} and the list
  • Queue: add_to_queue, max_posts_per_slot, GET/POST /api/uploadposts/queue/settings, /queue/preview, /queue/next-slot
  • Post actions: POST /api/uploadposts/posts/retry, /posts/unpublish
  • Analytics: GET /api/analytics/{profile_username}, /api/uploadposts/total-impressions/{profile_username}, /api/uploadposts/post-analytics/… – for the platforms whose API offers the numbers
  • Profiles: create, list, show, PATCH display name, delete, disconnect a platform, generate-jwt connect links, validate-jwt, me
  • Pages and boards: Facebook pages, LinkedIn pages, Pinterest boards and sections, pinned pages
  • Webhooks: users/notifications, users/webhook-secret, the same signature headers (X-Upload-Post-Signature, X-Upload-Post-Timestamp)
  • Headers: Idempotency-Key, X-Request-Id, rate-limit headers
  • Per-platform fields such as youtube_title, privacyStatus, privacy_level, facebook_page_id, pinterest_board_id, first_comment, is_ai_generated

What is different

  • Not supported: Reddit, Discord, Telegram, Google Business, Mastodon and WordPress. If you send them, they answer like an unconnected platform (success: false, skipped: true) and the other platforms are published normally.
  • Platform availability: our own platform apps go through each platform's review. Which platforms are live right now is on the integrations overview. Bluesky, the API, webhooks and the compatibility layer work today.
  • Comments, DMs, ads and AI helpers of Upload-Post (comments, AutoDM, ChatGPT ads, FFmpeg editor) are not part of our API.
  • Data location: application, database and media are hosted in Germany; a data processing agreement is included.

Step by step

  1. Create the workspace and choose a plan that fits your number of profiles (Plans and billing).
  2. Recreate the profiles with exactly the same usernames. Your scripts send user=<name>; if the names match, nothing else changes. You can do it in Accounts → New profile or with POST /api/uploadposts/users.
  3. Reconnect the accounts. Access tokens cannot be moved from Upload-Post – every account signs in once more. For client accounts send a connect link (Connecting accounts).
  4. Create an API key and store it in your tool (n8n credential, Make connection, environment variable).
  5. Change the base URL in every script and workflow.
  6. Set up the webhook again if you used one, and update the signing secret in your receiver.
  7. Test with one post – for example a Bluesky text post or a scheduled post a few minutes ahead – and check History.
  8. Switch the rest, then cancel Upload-Post once all scheduled posts there have gone out.

Checklist

  • Profiles exist with the same usernames
  • All accounts connected (no "Reconnect needed")
  • New API key stored in all tools
  • Base URL changed everywhere (search your workflows for upload-post.com)
  • Webhook URL and secret updated
  • Test post published and visible in History
  • Scheduled posts still waiting at Upload-Post are either sent there or created again here

Need help?

Send us one of your requests (without the key) to info@my-video-automation.com – we check it against our API. More details: API reference and the Upload-Post API integration page.