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 |
|---|---|
bluesky | account, post |
discord | community |
facebook | account |
github | account, post |
instagram | account |
kick | account |
linkedin | account, organization |
pinterest | account |
reddit | account, community, post |
snapchat | account |
soundcloud | account, post |
spotify | account |
telegram | account, community |
threads | account, post |
tiktok | account |
twitch | account |
x | account, post |
youtube | account, post |
On LinkedIn, account targets personal profiles and organization targets company pages. On Bluesky, X, YouTube, Threads, Reddit, SoundCloud, and GitHub, post targets a single post, video, track, or repository instead of a whole profile. On Telegram, Reddit, and Discord, community targets a group, subreddit, or server. See Resource types for how to choose between them.
Supported Datapoints
| Datapoint | Type | Category |
|---|---|---|
followers | integer | metrics |
following | integer | metrics |
posts | integer | metrics |
verified | boolean | attributes |
employees | integer | metrics |
views | integer | metrics |
likes | integer | metrics |
reposts | integer | metrics |
Datapoints are returned under the metrics and attributes keys of each resource, using the names above.
Each datapoint also carries a semantic field with the platform’s own term for what the value counts, such as subscribers for YouTube followers, videos for TikTok posts, or karma for Reddit likes. The datapoint names above are stable across platforms; use semantic to display values in each platform’s language. See Success Response for details.
Availability by platform
| Platform | Type | followers | following | verified | employees | posts | views | likes | reposts |
|---|---|---|---|---|---|---|---|---|---|
| Bluesky | account | ✓ | ✓ | ✓ | — | ✓ | — | — | — |
account | ✓ | ✓ | ✓ | — | ✓ | — | — | — | |
| SoundCloud | account | ✓ | ✓ | ✓ | — | ✓ | — | — | — |
| TikTok | account | ✓ | ✓ | ✓ | — | ✓ | — | — | — |
| X / Twitter | account | ✓ | ✓ | ✓ | — | ✓ | — | — | — |
| GitHub | account | ✓ | ✓ | — | — | ✓ | — | — | — |
| SoundCloud | post | — | — | — | — | — | ✓ | ✓ | ✓ |
| Threads | account | ✓ | — | ✓ | — | ✓ | — | — | — |
| Twitch | account | ✓ | — | ✓ | — | ✓ | — | — | — |
| X / Twitter | post | — | — | — | — | — | ✓ | ✓ | ✓ |
| YouTube | account | ✓ | — | ✓ | — | ✓ | — | — | — |
| Bluesky | post | — | — | — | — | — | — | ✓ | ✓ |
account | ✓ | — | ✓ | — | — | — | — | — | |
| GitHub | post | — | — | — | — | — | — | ✓ | ✓ |
| Kick | account | ✓ | — | ✓ | — | — | — | — | — |
organization | ✓ | — | — | ✓ | — | — | — | — | |
account | ✓ | — | — | — | ✓ | — | — | — | |
account | — | — | — | — | ✓ | — | ✓ | — | |
| Snapchat | account | ✓ | — | ✓ | — | — | — | — | — |
| Spotify | account | ✓ | — | — | — | — | ✓ | — | — |
| Telegram | account | ✓ | — | ✓ | — | — | — | — | — |
| Telegram | community | ✓ | — | ✓ | — | — | — | — | — |
| Threads | post | — | — | — | — | — | — | ✓ | ✓ |
| YouTube | post | — | — | — | — | — | ✓ | ✓ | — |
| Discord | community | ✓ | — | — | — | — | — | — | — |
account | ✓ | — | — | — | — | — | — | — | |
community | — | — | — | — | — | ✓ | — | — | |
post | — | — | — | — | — | — | ✓ | — |
Service Status
Metrika is currently in beta. While we work to keep datapoints accurate and up to date, you should expect:
- Occasional delays in datapoint 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. Check the status page (linked in the footer of the main site) for real-time service status and incident history.
Rate Limiting
To keep the service responsive, requests are rate-limited per account. All tokens for the same account share a single pool, so the limit applies to your account as a whole rather than to individual tokens.
| Limit | Window | Scope |
|---|---|---|
| 100 requests | 60 seconds | Per account |
When you exceed the limit, the API returns 429 Too Many Requests with a descriptive error message. Back off and retry once the window resets.
Rate limiting protects the API from short bursts of traffic. It is separate from your plan’s monthly usage allowance (see below).
Usage Quota
Beyond the per-window rate limit, each plan includes a monthly usage allowance. Metrika is currently free for everyone, so the free-tier quota applies to every account:
| Tier | Monthly quota | Scope |
|---|---|---|
| Free | 500 requests | Per account |
| Paid (planned) | To be announced | Per account |
When you exhaust your monthly quota, the API returns 403 Forbidden with a message telling you when your allowance resets. The quota resets at the start of each calendar month. You can track your current usage and the reset date from your dashboard.
A higher-limit paid tier (€4.99/month) is planned. Paid plans are not available yet, so every account gets the free tier, no credit card required.
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 |
| 403 | Forbidden: monthly usage quota exhausted |
| 422 | Unprocessable entity: request validation failed |
| 429 | Too many requests: rate limit hit |
| 500 | Internal server error |