Keep the API key server-side
Load the PostSider credential from an environment variable in your script, worker, Django service or FastAPI application.
Python + REST API
Python does not need a special integration layer here. Use requests, httpx or your existing HTTP client to talk to PostSider from a script, worker or backend.
Start with the social media scheduler API or browse the full developer platform.
How it works
Your Python code owns the trigger and business logic. PostSider keeps the social account connections and publishing state out of your application.
Load the PostSider credential from an environment variable in your script, worker, Django service or FastAPI application.
Call the integrations endpoint and choose the account your Python job should publish to.
Send the content and target integration to the public API, adding a future UTC timestamp when the post should be scheduled.
Keep the returned post ID and read its state later, or consume webhooks when another part of your Python application depends on delivery.
Concrete example
Resolve the channel ID first. It is the value your later publishing request uses to target a specific connected account.
import os
import requests
headers = {
"Authorization": os.environ["POSTSIDER_API_KEY"],
}
response = requests.get(
"https://api.postsider.com/public/v1/integrations",
headers=headers,
timeout=20,
)
response.raise_for_status()
for channel in response.json():
print(channel["id"], channel["identifier"], channel["name"]) Related developer guides
FAQ