elchin APIelchin.blog ↗
Access pages, search results, and full content from elchin.blog via 3 endpoints covering IT project management and business analysis articles.
What is the elchin API?
The elchin.blog API provides 3 endpoints to list, retrieve, and search published content from Elchinbek Jabbarbergenov's blog on IT project management and business analysis. The get_page endpoint returns full HTML content plus metadata for any page by numeric ID or URL slug, while search lets you run full-text queries across all public content types and filter by subtype.
curl -X GET 'https://api.parse.bot/scraper/bdb811a5-5c0f-46a0-9aa2-f9c28755024f/list_pages?page=1&per_page=10' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace elchin-blog-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Elchin Blog SDK — browse pages and search content."""
from parse_apis.elchin_blog_api import ElchinBlog, Subtype, PageNotFound
client = ElchinBlog()
# List all published pages on the blog
for page in client.pages.list(limit=5):
print(page.title, page.slug, page.link)
# Drill into a specific page by ID
first_page = client.pages.list(limit=1).first()
if first_page:
try:
detail = client.pages.get(id=str(first_page.id))
print(detail.title, detail.date, detail.status)
except PageNotFound as exc:
print(f"Page not found: {exc}")
# Search content filtered by subtype using the enum
for result in client.search_results.search(query="loyiha", subtype=Subtype.PAGE, limit=5):
print(result.title, result.url, result.subtype)
print("exercised: pages.list / pages.get / search_results.search with Subtype enum")
List all published pages on the blog with pagination. Returns page metadata including title, slug, excerpt, dates, and links. Results are ordered by date descending.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| per_page | integer | Number of pages to return per request (max 100). |
{
"type": "object",
"fields": {
"pages": "array of page objects with id, date, modified, slug, title, link, excerpt, author, featured_media",
"total": "integer",
"total_pages": "integer"
},
"sample": {
"data": {
"pages": [
{
"id": 359,
"date": "2025-12-05T04:07:09",
"link": "https://elchin.blog/contact/",
"slug": "contact",
"title": "Murojaat",
"author": 1,
"excerpt": "Men bilan bog'lanish...",
"modified": "2026-04-27T06:25:51",
"featured_media": 0
}
],
"total": 4,
"total_pages": 1
},
"status": "success"
}
}About the elchin API
Endpoints and Data Coverage
The API covers three operations against elchin.blog's public content. list_pages returns a paginated array of page objects — each with id, date, modified, slug, title, link, excerpt, author, and featured_media — ordered by date descending. Pagination is controlled via page and per_page (up to 100 per request), and the response includes total and total_pages for cursor management.
Retrieving a Single Page
get_page accepts either a numeric id (e.g. '67') or a URL slug (e.g. 'home', 'contact', 'privacy-policy') — exactly one must be provided. The response includes the full content field as rendered HTML, the excerpt, publication and modification timestamps, status, and the canonical link. This is the endpoint to use when you need the complete body of an article or static page.
Full-Text Search
search runs a query across all public content and returns matching items with id, title, url, type, and subtype. An optional subtype filter narrows results to page, post, or elementor_library. Passing an empty query string returns all available content, which is useful for discovery. Results are paginated with the same page and per_page controls as list_pages.
The elchin API is a managed, monitored endpoint for elchin.blog — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when elchin.blog changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official elchin.blog API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Index all IT project management articles from elchin.blog using
list_pagesfor content aggregation. - Build a topic search tool using the
searchendpoint withsubtype=postto surface business analysis content. - Retrieve the full HTML content of specific guides via
get_pageby slug for downstream text processing. - Monitor content freshness by comparing
dateandmodifiedtimestamps fromlist_pagesresponses. - Enumerate all page slugs and IDs to build a sitemap or navigation structure from
list_pages. - Filter search results to only Elementor library entries using
subtype=elementor_libraryvia thesearchendpoint.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does elchin.blog have an official developer API?+
What does `get_page` return compared to `list_pages`?+
list_pages returns metadata only — id, slug, title, excerpt, date, modified, link, author, and featured_media — without the full page body. get_page adds the full content field as HTML and the status field, making it the correct endpoint when you need the complete text of a page or post.Does the `search` endpoint return post body content?+
id, title, url, type, and subtype only — no full HTML body or excerpt. To get the full content after a search, pass the returned id or slug to get_page.Are comments or author profile details available?+
author field in page responses. You can fork this API on Parse and revise it to add an endpoint that resolves author profile details.How far back does the content coverage go, and is there a way to filter by date range?+
list_pages, but neither list_pages nor search accepts a date-range parameter for filtering. You can fork this API on Parse and revise it to add date-filtering parameters to the listing endpoint.