Integration Guide

Upload-Post + Make Integration

Seamlessly connect your Upload-Post account with Make in 3 simple steps. Follow this visual guide to configure your API integration efficiently.

Get Started with Upload-Post

Create an account or log in to your existing account

Open Upload-Post App

API Configuration

Endpoint: https://api.upload-post.com/api/upload
Method: POST
Headers:
Authorization: Apikey [YOUR_API_KEY]
Note: Find your API key in your Upload-Post Manage Api Keys

Form Data Configuration & Make.com Setup

Field Value Required
title Your video title Optional
user Your username Required
platform[] tiktok Required
video Binary file Required
Make.com Configuration: Follow these steps in Make.com:
  • Add an HTTP Module: In your Make.com scenario, add an HTTP module and choose the "Make a Request" action.
  • Configure the Request Settings:
    • Method: Set to POST.
    • URL: Enter https://api.upload-post.com/api/upload.
    • Headers: Add a header with:
      • Key: Authorization
      • Value: Apikey [YOUR_API_KEY]
    • Set the Request Body: Change the body type to multipart/form-data and add the following form fields:
      • title: Set the value to your desired title (you can use a variable if needed, e.g., [YOUR TITLE]).
      • user: Enter your username the one you setted in upload-post (e.g., [YOUR USERNAME]).
      • platform[]: Set the value to tiktok.
      • video: Attach the binary file (your video file). Make sure this field is mapped to the binary data you want to send.
  • Save and Test: Save your scenario and run a test to ensure that the video upload works correctly via the API.

Advanced Configuration Options

For Instagram Uploads

To upload to Instagram instead, simply change the platform value to instagram in your form data.

Uploading to Multiple Platforms

To upload to both TikTok and Instagram simultaneously, add both platform values by creating multiple fields with the same name platform[] in the Make.com HTTP module.

Securely Storing API Keys in Make.com

For better security, avoid hardcoding your API key directly in scenarios:

  • Create an App Key in Make.com
  • Store your Upload-Post API key as a constant
  • Reference the constant in your HTTP module headers
  • When sharing scenarios, use scenario blueprints which do not expose your keys

Example of referencing an API key constant in Make:

"headers": {
  "Authorization": "Apikey {{constants.uploadPostApiKey}}"
}

Need more guidance? Check out this detailed forum post:

Make.com Community Tutorial

Need Assistance?

Our integration experts are here to help