V1 API Overview
The Metrika API V1 provides programmatic access to social media datapoints.
Base URL
All endpoints are served from:
https://metrika.run
Authentication
Every request must include an API token in the Authorization header:
Authorization: Bearer YOUR_TOKEN
See Authentication for details on obtaining and using tokens.
Content Type
Send and receive JSON. Set the Content-Type header:
Content-Type: application/json
Supported Resources
| Platform | Types |
|---|---|
facebook | account |
instagram | account |
linkedin | account |
threads | account |
tiktok | account |
x | account |
youtube | account |
Supported Datapoints
| Datapoint |
|---|
follower_count |
Service Status
Metrika is currently in beta. While we work to keep metrics accurate and up to date, you should expect:
- Occasional delays in metric collection and updates
- Temporary unavailability of certain platforms during scraper maintenance
- Data gaps when third-party platforms change their systems
We recommend building your integration to handle stale or missing data gracefully.
Rate Limiting
Requests are rate-limited per account (all tokens for the same account share a pool). The limit depends on your subscription status:
| Tier | Limit | Window | Scope |
|---|---|---|---|
| Paid | 3000 requests | 1 minute | Per account |
| Free | 25 requests | 30 days | Per account |
When exceeded, the API returns 429 Too Many Requests with a descriptive error message.
Versioning
The current stable version is V1. All V1 endpoints are prefixed under the base URL. Future versions will be released as V2, V3, etc., with backward-compatibility guarantees documented per release.
Errors
The API uses conventional HTTP response codes:
| Status | Meaning |
|---|---|
| 200 | Success |
| 401 | Unauthorized — missing or invalid API token |
| 422 | Unprocessable entity — request validation failed |
| 429 | Too many requests — rate limit hit |