Metricool’s API is one of the most underappreciated features in social media scheduling. Most tools at this price point don’t have a documented REST API. Metricool does, it works reliably, and it enables publishing workflows that manual scheduling simply can’t match at scale.
This is what the Metricool API can do, what it can’t do, and how we use it in a real content operation.
What the API Supports
Creating scheduled posts. The primary use case. You can create a post via API call — specifying the caption, media, platforms, brand, and scheduled time — and it appears in the Metricool planner as a scheduled post. This is what enables publishing from an external content pipeline without manual re-entry into the Metricool interface.
Retrieving scheduled content. You can pull a list of scheduled posts for a brand via API, which is useful for auditing what’s queued, building custom calendar views, or syncing Metricool’s schedule with an external system.
Analytics retrieval. Performance data — follower counts, engagement metrics, post performance — is accessible via API, enabling automated reporting pipelines and custom dashboards that pull Metricool data alongside other data sources.
Brand and account management. Basic account structure queries — listing connected brands and their associated social accounts — are available via API, which is useful for multi-brand operations building custom management tools on top of Metricool.
What the API Doesn’t Support
The Metricool API doesn’t support every feature available in the UI. Story scheduling, some Instagram Reel configurations, and certain platform-specific post types may have limited or no API support. Check the current API documentation for the specific endpoints and parameters before building a workflow that depends on a specific feature — the API surface area has been growing, but it’s not yet comprehensive coverage of every UI feature.
How We Use It
Our publishing pipeline creates Metricool draft posts via API as part of the content production workflow. When an article or social post is ready for scheduling, the pipeline calls the Metricool API to create a draft post with the caption, media URL, platform selections, and brand ID. The draft appears in the Metricool planner for review and final scheduling. This workflow eliminates manual re-entry of content into the scheduling interface and ensures every piece of content is logged in both our internal system and Metricool simultaneously.
We also pull analytics data via API for monthly reporting, which allows us to aggregate Metricool performance data alongside other data sources without manual export and re-import.
Getting Started with the API
API access requires an Advanced plan tier or above. Once on the right plan, generate your API token in Settings → API. The token authenticates all API requests — include it as a Bearer token in the Authorization header of every API call.
The base URL for API calls is the Metricool API endpoint documented in their developer documentation. Authentication, available endpoints, request formats, and response structures are all documented there. The documentation is adequate — not as comprehensive as some major platform APIs, but sufficient to build functional integrations.
Start with a simple GET request to list your brands and verify authentication is working before building more complex workflows. The most common issue is incorrect token handling — verify your Authorization header format against the documentation before troubleshooting anything else.
We set up and run Metricool for multi-brand social media operations — the pipeline, the scheduling system, and the analytics workflow.
Tygart Media manages social scheduling across multiple brands using Metricool daily. We know what the tool actually does and what it doesn’t.
Frequently Asked Questions
Does the Metricool API support all social platforms?
The API supports the major platforms — Instagram, Facebook, LinkedIn, Twitter/X, and Google Business Profile — for post creation and analytics retrieval. Support for newer or less common platforms (TikTok, Pinterest, Twitch) may be more limited via API than in the UI. Check the current API documentation for the specific platform support before building platform-dependent workflows.
Is the Metricool API rate limited?
Yes — Metricool’s API has rate limits that restrict how many requests you can make in a given time window. The specific limits are documented in the API documentation. For typical agency use cases — creating a few dozen posts per day, pulling analytics weekly — the rate limits are not constraining. High-volume automated publishing workflows may need to implement request throttling to stay within limits.
Can you use the Metricool API to post images and videos?
Yes, with some nuance. Media is typically passed as a URL that Metricool fetches, rather than as a file upload in the API request. Your media needs to be accessible via a public URL at the time of the API call. For operations with a media hosting infrastructure — a CDN, cloud storage, or media management system — this is straightforward. For operations without an existing media hosting layer, you’ll need to add one before the API-based media posting workflow is viable.
Leave a Reply