A user's rating history
API · /codeforces-api
Codeforces API
Codeforces como API — la plataforma de programación competitiva más grande, que ejecuta rondas clasificatorias regulares para cientos de miles de programadores en todo el mundo. Esta API envuelve la API oficial de Codeforces en un servicio JSON limpio y predecible. /v1/user busca el perfil de uno o varios competidores: calificación actual y máxima con el rango/título correspondiente (desde novato hasta gran maestro legendario), puntuación de contribución, país, ciudad, organización, fecha de registro y avatar. /v1/rating devuelve el historial completo de calificaciones de un competidor, concurso por concurso, con la calificación anterior y nueva, el cambio de calificación y el rango alcanzado en cada ronda — ideal para trazar una curva de calificación. /v1/contests lista los próximos concursos y los pasados, filtrables por fase (BEFORE para el calendario de próximas rondas, FINISHED para el archivo), cada uno con hora de inicio, duración y tipo. /v1/problems busca en todo el conjunto de problemas de Codeforces por etiqueta (dp, grafos, greedy, matemáticas, implementación, estructuras de datos y docenas más) y por rango de dificultad, devolviendo el id del concurso, índice, nombre, calificación de dificultad y etiquetas de cada problema con un enlace directo. Las calificaciones van desde ~800 hasta 3500+. Ideal para paneles de programación competitiva, rastreadores de calificaciones, herramientas de entrenamiento y recomendación de problemas, y bots de Discord/Telegram para comunidades de CP. Datos de la API oficial de Codeforces, de uso gratuito. El servicio es resistente al límite de concurrencia de Codeforces (reintento automático con retroceso).
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 293 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,064
- attiva
- Chiamate totali
- 10
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 1,000 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1000 calls/month
- 2 req/sec
- Profiles, ratings, contests & problems
- No credit card
Starter
€8.00 /mese
- 30,000 chiamate/mese
- 5 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 30k calls/month
- 5 req/sec
- Full rating history
- Email support
Pro
€24.00 /mese
- 130,000 chiamate/mese
- 12 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 130k calls/month
- 12 req/sec
- Problemset search & dashboards
- Priority support
Mega
€64.00 /mese
- 520,000 chiamate/mese
- 35 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 520k calls/month
- 35 req/sec
- High-volume bots & trackers
- Dedicated SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
GST API
Validate and decode Indian GSTINs (the 15-character Goods & Services Tax Identification Number) instantly and entirely offline. The validate endpoint checks the structure and recomputes the official GSTIN check digit — the base-36 weighted algorithm the GSTN itself uses — and confirms the embedded state code is real, returning a clear valid/invalid verdict with the specific reasons a number fails. The decode endpoint breaks a GSTIN into its parts: the GST state/UT code and its name, the embedded 10-character PAN, the PAN holder type (company, individual/proprietor, firm/LLP, HUF, trust, government and more, read from the PAN's 4th letter), the entity registration number, the default 'Z' slot and the check digit. A states endpoint returns the full GST state-code reference for building dropdowns and lookups. Everything is pure computation — no network call, no key, no cache — so it is fast and private, ideal for checkout and onboarding forms, invoicing and e-invoice/e-way-bill pipelines, vendor master data cleansing and bulk validation. A structural GSTIN validator and decoder — distinct from EU VAT-number validation (vat), IBAN bank-account validation (iban) and card-number checks (creditcard). Note: this verifies the number's structure and check digit, not whether it is actively registered in the GSTN portal. No upstream key, no cache.
api.oanor.com/gst-api
ads.txt API
Fetch and evaluate any publisher's ads.txt / app-ads.txt — the IAB authorized-digital-sellers standard. Pass a domain and the check endpoint fetches its ads.txt server-side, then returns every seller record parsed into its fields — advertising system, the publisher's seller/account id, the DIRECT or RESELLER relationship and the optional certification-authority id (TAG-ID) — alongside counts (direct, reseller, distinct ad systems) and the declared variables OWNERDOMAIN, MANAGERDOMAIN, CONTACT and SUBDOMAINS. The verify endpoint answers the one question programmatic-advertising integrations actually ask: is this advertising system, with this publisher id, authorized to sell this domain's inventory? — returning an authorized boolean and the matching records. A missing file is reported as found:false (not an error), and soft-404 HTML pages are detected and rejected so you never parse a "page not found" as records. The request is made server-side and private or internal targets are refused (SSRF-guarded). Built for ad-tech supply-chain verification, SSP/DSP onboarding checks, anti-fraud and inventory audits. An ads.txt seller-authorization checker — distinct from the security-contact file reader (securitytxt), the robots.txt crawlability evaluator (robots) and the sitemap parser (sitemap). No upstream key, no cache.
api.oanor.com/adstxt-api
Sitemap API
Fetch and parse an XML sitemap (the sitemaps.org protocol). Pass a sitemap URL and the parse endpoint fetches it — following redirects and transparently gunzipping .gz sitemaps — and returns its type: a urlset with every URL and its lastmod, changefreq and priority, or a sitemapindex listing the child sitemaps, with offset/limit paging for large files. The urls endpoint goes further: when the sitemap is an index it fetches the child sitemaps too and flattens every page URL into a single list, with a configurable cap on URLs and child sitemaps and a truncated flag so you stay in control. The request is made server-side and private or internal targets are refused (SSRF-guarded). Built for SEO audits, building crawl queues and content inventories, change monitoring and migration checks. A sitemap fetcher and parser — distinct from generic XML-to-JSON conversion (xml), the robots.txt evaluator (robots) and the on-page SEO audit (seo). No upstream key, no cache.
api.oanor.com/sitemap-api
Text Segmentation API
Count and split text the way people actually read it, using Unicode-correct segmentation. The count endpoint returns the number of grapheme clusters — the real, user-perceived characters, so a family emoji counts as 1 (not 7) and an accented letter as 1 — alongside words, sentences, code points, UTF-16 code units (the naive string length that over-counts) and UTF-8 byte length. This is exactly what character-limit fields, tweet/SMS counters and validation need so the count agrees with what the user sees. The segment endpoint splits text into grapheme, word or sentence segments (word segments are flagged word-like versus punctuation and spaces) and is locale-aware, so Japanese, Chinese and Thai word boundaries come out right. Everything is computed locally with no network calls. A Unicode text segmenter — distinct from the Unicode codepoint database (unicode), the case/text-utilities toolkit (text) and string similarity (similarity). No upstream key, no cache.
api.oanor.com/segmenter-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Codeforces API?
Qual è il limite di velocità di Codeforces API?
Quanto costa Codeforces API?
Posso cancellare l'abbonamento in qualsiasi momento?
Codeforces API è conforme al GDPR?
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.
curl https://api.oanor.com/codeforces-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/codeforces-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/codeforces-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/codeforces-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.