Blog info
API · /tumblr-api
Tumblr API
Read any public Tumblr blog in real time — no login or key needed. Fetch a blog's info (title, description, total post count), its posts with paging and an optional post-type filter (text, photo, quote, link, chat, audio, video, answer), posts filtered by a tag, and a single post by id. Each post comes in the upstream Tumblr shape with its type-specific fields (photo URLs, video embeds, quote text, etc.), tags and timestamps. Pass blog = the blog name (its subdomain); every call is live (no cache). 5 endpoints. Built for blog content aggregation, social listening and feed back-ends. A Tumblr blog-reading API. No upstream key, no cache.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 607 ms
- Server probes · 24h
- Subscribers
- 4,004
- active
- Total calls
- 95
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 3,300 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 3,300 calls/month
- 2 req/sec
- All 5 read endpoints
- No credit card
Starter
€6.30 /month
- 65,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 65k calls/month
- 8 req/sec
- Posts, tags, filters
- Email support
Pro
€18.50 /month
- 325,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 325k calls/month
- 20 req/sec
- Content pipelines
- Priority support
Mega
€45.50 /month
- 1,600,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 1.6M calls/month
- 50 req/sec
- Aggregation scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Qiita Developer Community API
Articles, engagement and trending tech tags from Qiita (qiita.com), Japan's largest developer knowledge-sharing community, read keyless from its public v2 API. Qiita is where Japanese engineers post how-tos, deep-dives and notes, and where the community signals quality with LGTM ("looks good to me") likes and "stocks" (saves) — the Japanese counterpart to dev.to or Medium's engineering side, with its own metrics and its own tech-topic rankings. The articles endpoint searches and lists articles, each with its title, LGTM likes, stocks (saves), comment count, tags and author — filterable by keyword, tag and a minimum-stocks threshold so you can surface the popular pieces. The article endpoint returns one article in full by its id. The tags endpoint ranks Qiita's tech tags by how many articles and followers they have — the live map of what Japanese engineers care about (Python, AWS, React and the rest). This is the Qiita platform cut — a distinct social and developer platform, separate from dev.to, Medium and the other blogging and social feeds in the catalogue, with its own LGTM/stock engagement model. Likes are LGTM up-votes and stocks are saves/bookmarks — two distinct Qiita signals; follower and article counts are the real, live community numbers. Titles and tags are in Japanese (and English) as Qiita publishes them. Qiita rate-limits unauthenticated callers, so a longer protective cache fronts the upstream and stale data is served if the limit is hit. Keyless.
api.oanor.com/qiita-api
Medium API
Read Medium posts in real time — no login or key needed. Pull the recent stories of any Medium user (@handle), any topic/tag, or any publication, straight from Medium's own public RSS feeds. Each post comes with its title, author, canonical link, publish date, categories/tags, a clean text excerpt and the full content HTML. Pass user = the @handle, tag = a topic slug, or publication = a publication slug; every call is live (no cache). 4 endpoints. Built for content aggregation, author/topic monitoring and reading-list back-ends. A Medium reader API. No upstream key, no cache.
api.oanor.com/medium-api
Towns API
Live EVM on-chain data for Towns (chain id 550) — an OP-Stack Layer-2 that powers decentralised group chat and on-chain social spaces, with gas paid in ETH — served directly from the public Towns JSON-RPC with server-side resilience. The status endpoint returns the chain and network id, the latest block height and the node client version. The block endpoint returns a block by number (or the latest) with its hash, parent hash, timestamp, transaction count, gas used and gas limit, miner and size. The gas endpoint returns the current gas price in both wei and gwei. The balance endpoint returns the ETH balance and outgoing transaction count for any address, converted from base wei (18 decimals) into whole ETH with exact big-integer scaling. Every figure is read live from the chain over JSON-RPC — nothing bundled or modelled — behind a short server-side cache with keep-warm so the feed stays fast and fresh. Ideal for explorers, wallet and dashboard tooling, gas trackers, address monitors and analytics apps across the Towns social ecosystem. Live keyless upstream. 5 endpoints.
api.oanor.com/towns-api
Desmos API
Live on-chain data for Desmos (chain id desmos-mainnet) — the Cosmos-SDK Layer-1 purpose-built for decentralised social networking, whose native token is DSM — served directly from public LCD/REST nodes with multi-node failover. The status endpoint returns the latest block height and time, chain id, the staking bond denom and the current minting inflation rate. The validators endpoint lists the active bonded validator set ranked by stake, each with its moniker, operator address, self-plus-delegated DSM, commission rate and jailed flag. The supply endpoint returns the total DSM supply, the amount bonded in staking and the resulting bonded ratio. The governance endpoint returns the most recent on-chain proposals with their id, title, status and voting window. Token amounts are converted from base micro-DSM (6 decimals) into whole DSM, and every figure is read live from the chain — nothing bundled or modelled — behind a short server-side cache with keep-warm so the feed stays fast and fresh. Ideal for staking dashboards, validator and delegator tooling, explorers, governance trackers and portfolio or analytics apps across the Cosmos and decentralised-social ecosystem. Live keyless upstream. 5 endpoints.
api.oanor.com/desmos-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Tumblr API?
What's the rate limit for Tumblr API?
How much does Tumblr API cost?
Can I cancel my subscription anytime?
Is Tumblr API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/tumblr-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/tumblr-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/tumblr-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/tumblr-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.