Service metadata

Codefragmenten

curl "https://api.oanor.com/gettr-api/v1/meta" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/gettr-api/v1/meta", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/gettr-api/v1/meta");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/gettr-api/v1/meta",
    headers={"x-oanor-key": "oanor_test_..."}
)

Voorbeeldrespons

Een echte respons van dit endpoint, vastgelegd bij de laatste health check.

{
    "data": {
        "note": "Usernames are GETTR handles without the @ (e.g. gettr, newsmax). Follower/following are live counts; joined is the account creation date.",
        "source": "GETTR public API (api.gettr.com, live)",
        "service": "gettr-api",
        "endpoints": {
            "GET /v1/meta": "This document.",
            "GET /v1/user": "Public profile and engagement stats for a handle (username=gettr).",
            "GET /v1/trends": "Trending topics on GETTR right now (limit=10, max 30)."
        },
        "description": "Live public data from GETTR, a global microblogging social network. The user endpoint returns a public profile and its engagement stats (display name, bio, website, language, follower and following counts, imported-Twitter follower count, influencer level and join date); the trends endpoint returns what is trending on GETTR right now. Live, no key, nothing stored. A genuine social-platform feed (profiles, stats and trends), distinct from the other social APIs in the catalogue.",
        "trend_sample": 5,
        "upstream_status": "ok"
    },
    "meta": {
        "timestamp": "2026-06-11T16:47:33.429Z",
        "request_id": "bc6b3d08-c2f5-425f-915c-d590090da609"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}