Pipixia Public Data API | SandBase
Choose the Pipixia board-list or board-detail API, understand response checks, daily metrics, exact IDs, pricing and the boundaries of a single snapshot.

Pipixia board research starts with a choice: inspect the list of board previews, or read one board type you have already selected. These answer different questions. A preview helps you choose a relevant board; a detail request gives a snapshot of that board. Neither one, by itself, proves that a post is rising over time.
This 2026-11-08 repair checks those two contracts through free inspect and public reference payloads, without a new business call. The original 2026-09-27 UTC board-list capture remains below. The wider catalog still helps locate search, user and post tasks, but those routes were not revalidated in this revision.
Key takeaway
- Board list takes an empty object and returns previews under data.boards; detail takes an integer block_type and uses data.board.
- The documented SandBase payload is outputs[0].data. Require completed status, integer provider status_code zero and the selected collection shape.
- Daily comment likes and plays are different measures; keep their item_info labels, exact string IDs and null values.
- App links are not pagination parameters. This guide does not expand into every board, media downloads, statistics or view-increment calls.
The retained cover is conceptual artwork. Its creator names, cards and counts are illustrative, not verified identities or measured results from this revision; LIVE and real-time labels are not a measured freshness guarantee.
Pick a public read
| Your question | Endpoint | Input | What to inspect |
|---|---|---|---|
| Which board previews are available? | Board list | {} | data.boards and each board’s board_items |
| What is on the board I selected? | Board detail | {"block_type":12} | data.board and board_items |
The selected calls authenticate with a SandBase key, not a Pipixia account session. SandBase supplies an access layer and does not own or operate Pipixia. This is not an official Pipixia partnership or an account-authorized workflow. A public read cannot grant access to private information or permit actions as a platform member.
List declares no request parameters. Detail declares the required integer block_type, with 12 as its example, and no cursor, page or limit. An old description names /fetch_hot_search_board_list; use the actual /v1/api/pipixia/app/hot-search-board-list route instead of treating that function name as a callable URL. The Python snapshot tutorial checks the two shapes separately.
Historical Pipixia catalog screenshot retained for navigation. Old catalog paths, GET labels and endpoint counts are not the current execution contract or a fresh availability check.
One request from an existing setup
Keep SANDBASE_API_KEY in your runtime or secret manager. A connected agent can reuse it and send one selected request. For a new project, share SKILL.md, quickstart.md and the human quickstart. State whether you want previews or a particular board, and ask for observed fields before approving a larger workflow. Do not paste the key into the conversation.
curl --fail-with-body --connect-timeout 10 --max-time 90 \
-X POST https://api.sandbase.ai/v1/api/pipixia/app/hot-search-board-list \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'This command prints one response; it does not validate the business result for you. The tutorial adds timeouts, redirect rejection, JSON and HTTP error handling, strict provider checks and collection validation. For an independent detail read, choose the detail URL and body {"block_type":12} instead. Do not add a model field, search term or invented paging parameter.
A completed transport run is not enough: validate the object in outputs[0].data, integer status_code zero and its inner data object. List must contain a boards array; detail must contain a board object with board_items and the selected type. Present empty arrays are different from missing or malformed collections. Do not turn a provider error into an empty successful list.
Preserve the original observation
The original board-list run 08d73dd2-2498-47aa-8cdc-87056e1426d1, recorded 2026-09-27 UTC, is retained verbatim below. Its count is historical and does not describe today’s board. The repair date is not a new run date.
{
"id": "08d73dd2-2498-47aa-8cdc-87056e1426d1",
"status": "completed",
"model": "pipixia/app/hot-search-board-list",
"outputs": [
{
"data": {
"status_code": 0,
"message": "success",
"data": {
"boards": [
{ "board_items": [ { "item_info": "今日神评点赞", "today_digg_num": "4375" } ] }
]
}
}
}
]
}Current public README examples also show status_code zero and message success, with list using data.boards and detail using data.board. They contain a selected entry labeled 今日神评点赞 (today’s highlighted-comment likes), today_digg_num 1915 and today_show_num null. These are saved reference values, not new measurements. Preserve a field’s original type; the older excerpt’s string count and the newer reference’s numeric count should not be silently presented as one freshly measured series.
Historical board-list parameter and envelope reference. Its generated model field is historical; the current list body is an empty object. Its empty business example does not mean that missing collections are valid; current prose distinguishes the selected reference shape from the old screenshot.
Interpret a board before comparing it
Carry item_info and the metric name with each value. Daily highlighted-comment likes are not the post’s lifetime likes or a video’s plays. A null today_show_num is not zero, and a missing comment object is not proof that the post has no comments. Do not choose a truthy counter and rename every result “engagement.” That loses both the unit and the evidence for what was observed.
Keep the board’s block_type, available title and retrieval time beside each item. The array’s order is a position within that snapshot, not a global ranking across board types. An item can appear in multiple boards; item-only maps may overwrite one context with another. If a later snapshot does not include it, record “unobserved,” not “deleted” or an invented last-place rank.
Prefer exact item_id_str values. Saved browser-rendered examples also display numeric item_id values with lost precision. Turning a rounded number into text does not recover the true identifier. If the string is absent, keep identity unknown rather than guessing from a numeric display. This is a boundary in the saved representation, not a claim that a new API execution corrupted an ID.
A highlighted comment’s city_name is its displayed region label, not the author’s address or an audience geography measure. Signed cover/avatar links may expire; reading the URL neither downloads the file nor establishes permission to republish it. This task leaves those fields in the response and makes no extra media requests.
Navigation is separate from execution
The wider Pipixia catalog includes search, users and posts. The following are historical navigation entries, not parameters or payloads re-tested in this revision:
| Capability | Representative route | Before a separate task |
|---|---|---|
| Search | pipixia/app/search | Check current input and result structure |
| User record | pipixia/app/user-info | Verify identifier source and returned fields |
| Post detail | pipixia/app/post-detail | Verify post ID and business response |
| User posts | pipixia/app/user-post-list | Verify its own pagination contract |
Shared authentication does not make their business payloads interchangeable. A successful board read does not verify search, profile, statistics or write-style operations. Do not reuse a board parser for every catalog route or start an implicit chain from a preview entry to its author and all their posts.
Historical Pipixia search parameter reference, not an endpoint-list screenshot. Search inputs and continuation behavior were not revalidated in this board-focused repair.
The selected board payload’s has_more_text and has_more_schema are app-navigation hints, not verified API cursors. Detail’s chosen schema has no pagination fields. The one-request procedure stops at the returned collection instead of following bds links or manufacturing an offset. No guarantee of exhaustive board retrieval is made.
Price and workload
Free inspect on 2026-11-08 lists both selected endpoints at $0.001, eligible for an organization’s shared 100-call daily allowance across eligible APIs, resetting at 00:00 UTC. Eligibility does not reveal how many calls remain. Balance and real charges were not checked, and no free-success guarantee is made. The quota reset does not determine the provider’s daily metric boundary.
One selected request lists at $0.001; choosing both independently lists at $0.002 before quota effects. Polling, automatic retries and opening every board multiply the count. The current tutorial intentionally performs one request and stops, allowing you to decide whether repeated snapshots answer the actual research question.
FAQ
Does this guide implement a monitor? It prepares a validated snapshot. A recurring monitor still needs sampling rules, storage, a matching key that includes board context and a budget. This revision performed no new multi-run trend test or scheduling action.
Can I use the full-board link as a cursor? No verified API continuation follows from that app link. Choose one integer block_type for detail; its selected schema declares no page, cursor or limit.
Does reading a board increase its posts’ view counts? No view-increment operation is part of this procedure. The catalog can contain other operations, but the selected workflow calls only board list or board detail and does not invoke statistics, downloads or follow-up actions.
Where is the old Python? It is preserved with hashes in the historical archive. Its permissive missing-status checks and empty-list fallback are superseded by the strict tutorial helper. Historical evidence remains readable without presenting that code as current guidance.
Found this useful? Share it