I built Meteus, an API that helps developers post to platforms like Instagram, TikTok, Pinterest, LinkedIn, X, and Tumblr from backend code — without needing to fight each platform’s unique OAuth, content formatting, or media upload flows.
It was born out of frustration with how inconsistent and restricted these APIs are. Meta’s Graph API requires reviews and scopes, TikTok’s API is still mostly private, and Pinterest requires platform approval. Managing all of these across one app got painful — so I abstracted the process.
Meteus is:
API-only (no dashboard, no frontend)
Built for devs who want to automate publishing from code
Supports scheduling, multi-platform posts, image + video content
A typical request looks like:
{
"platforms": ["instagram", "tiktok", "pinterest"],
"text": "This post was sent via one API.",
"imageUrl": "https://cdn.meteus.dev/example.jpg",
"schedule_at": "2025-06-20T10:00:00Z"
}
Right now there’s a waitlist while I onboard the first developers manually. The API docs and code example are on the homepage: https://meteus.dev
I’d really appreciate:
Feedback on the API design or naming
Input on use cases I might be missing
Any lessons you’ve learned from dealing with social APIs
Thanks!
meyusufdemirci•7mo ago
I built Meteus, an API that helps developers post to platforms like Instagram, TikTok, Pinterest, LinkedIn, X, and Tumblr from backend code — without needing to fight each platform’s unique OAuth, content formatting, or media upload flows.
It was born out of frustration with how inconsistent and restricted these APIs are. Meta’s Graph API requires reviews and scopes, TikTok’s API is still mostly private, and Pinterest requires platform approval. Managing all of these across one app got painful — so I abstracted the process.
Meteus is:
API-only (no dashboard, no frontend) Built for devs who want to automate publishing from code Supports scheduling, multi-platform posts, image + video content A typical request looks like:
{ "platforms": ["instagram", "tiktok", "pinterest"], "text": "This post was sent via one API.", "imageUrl": "https://cdn.meteus.dev/example.jpg", "schedule_at": "2025-06-20T10:00:00Z" }
Right now there’s a waitlist while I onboard the first developers manually. The API docs and code example are on the homepage: https://meteus.dev
I’d really appreciate:
Feedback on the API design or naming Input on use cases I might be missing Any lessons you’ve learned from dealing with social APIs Thanks!
– Yusuf