codeforces.blog_entry

stable Standard

Fetch a Codeforces blog entry.

GET /v1/codeforces/blog_entry

What you get#

One Codeforces record in Onekey's unified shape, in data. If the record does not exist you get a 404 not_found and are not charged.

What it costs#

Standard · 1 credit for a fresh fetch, charged only when it succeeds.
Free when served from cache (0.2 credit for a cached response over 100 KB).
Free if the request is invalid (never charged) or the source fails or reports not found (refunded).

Parameters#

Name	Type	Required	Default	What it is	Constraints
`id`	string	yes	(required)	Blog entry id, e.g. 79	max 9 chars; must match `[0-9]{1,9}`; trimmed

Request#

curl "https://api.onekey.dev/v1/codeforces/blog_entry?id=79" \
  -H "x-api-key: YOUR_API_KEY"

Try it

Add your key to run this call right here. No key? Get one free. The key stays in this tab.

Recorded response#

A real Codeforces response, recorded and returned in Onekey's shape. Fields the platform does not provide are null.

json

{
  "success": true,
  "data": {
    "content": {
      "id": "79",
      "title": "About the programming languages",
      "text": "This post is no longer relevant; it has become significantly outdated. You should read the post at https://codeforces.com/blog/entry/121114 . Later you'll be introduced to the rules of the Codeforces contests, which differ from those of ACM-ICPC , TopCoder, GCJ, and I hope they'll bring some difference to the world of programming competitions. Most of the official competitions will be carried out according to these rules, though there will be more traditional contests. For example, Codeforces Beta Round #1 will be carried out according to the familiar ACM-ICPC rules. For some time testing will be based on Windows, but things might change in future, fortunately, the system supports testing on different platforms, even within one contest. At the present time the system is configured to support the following programming languages (the compilation and/or the launching line is shown for each language): GNU C++ 4 g++.exe -static -DONLINE_JUDGE -lm -s -x c++ -Wl,--stack=268435456 -O2 -o {filename}.exe {file} GNU C++11 4 g++.exe -static -DONLINE_JUDGE -lm -s -x c++ -Wl,--stack",
      "createdAt": "2010-02-17T09:32:18Z",
      "language": "ru"
    },
    "author": {
      "username": "MikeMirzayanov"
    },
    "engagement": {
      "likes": 0
    }
  },
  "metadata": {
    "platform": "codeforces",
    "endpoint": "blog_entry",
    "cached": false,
    "stale": false,
    "age_s": 0,
    "fetched_at": "2026-01-01T12:00:00+00:00",
    "credits_charged": 1,
    "request_id": "7f3a9c2e5b1d4c8fa2e6d0b9c4f18e37"
  },
  "error": null
}

Field mapping#

How this endpoint's source fields become Onekey's unified schema. Fields the source lacks come back as null.

Source path	Onekey field	Transform
`result.id`	`content.id`	`toString`
`result.title`	`content.title`	`stripHtml`
`result.content`	`content.text`	`stripHtml`
`result.authorHandle`	`author.username`	-
`result.rating`	`engagement.likes`	`toNumber`
`result.creationTimeSeconds`	`content.createdAt`	`toIsoDate`
`result.originalLocale`	`content.language`	-

Caching and freshness#

Fresh for about 30 minutes. Repeat calls in that window are served from cache and are free.
Between 30 minutes and 6 hours the cached copy is still served instantly and marked stale: true while Onekey refreshes it in the background.
If the source is down when a refresh is needed, the last copy can be served for up to 1 day more (marked stale).
A "not found" is remembered for 5 minutes and is free.
The cache is shared across all customers, which is what keeps repeat calls cheap.

What can go wrong#

Status	Code	What to do
401	`unauthorized`	Check the `x-api-key` header.
402	`insufficient_credits`	Add credits; your balance must cover the price.
404	`not_found`	That record does not exist. Free; do not retry.
422	`invalid_params`	Fix the parameters using the table above. Free.
429	`rate_limited`	Wait `Retry-After` seconds, then retry.
502	`upstream_error`	The source failed. Refunded; retry with backoff.

See Errors for the full list and retry guidance.

Status: stable (verified against the live source).