개발자 API

Conference Partner API & MCP server

Programmatic, read-only access to the whole Conference Partner dataset: 5,787 academic conferences and 1,210 journals, with Calls for Papers and submission deadlines, conference dates and locations, CCF / ICORE / QUALIS rankings side by side, historical acceptance rates, edition history, journal impact factors, ISSNs and special issues. Two interfaces over the same data: a REST API and a native MCP server for AI agents.

Try it right now

These three commands work as-is, with no credentials and no account:

# AI-field conferences with a submission deadline in the next three months
# (no keyword needed — every search parameter is optional and combinable)
curl "https://www.myhuiban.com/api/conferences?field=ai&submission_date_start=2026-08-01&submission_date_end=2026-11-01"

# Conferences whose call for papers is currently open
curl "https://www.myhuiban.com/api/conferences/rankings/cfp?per_page=5"

# Site-wide statistics (totals, deadlines by month, country distribution)
curl "https://www.myhuiban.com/api/statistics"

Every response carries X-Quota-Limit and X-Quota-Remaining so you can see what is left for the day. CORS is open, so these also work from browser JavaScript.

REST endpoints

Endpoint What it returns Auth
GET /api/conferences Search. All parameters optional and combinable: query, ccf_rank, core_rank, qualis_rank, field (14 CS areas), submission_date_start/_end, conference_date_start/_end. none
GET /api/conferences/rankings/{ranking} Curated lists: cfp, past_cfp, ccf, core, qualis, most_viewed, most_tracked, most_attended, most_competitive, upcoming, past, trending. none
GET /api/journals Search. All parameters optional: query, ccf_rank, issn, field. none
GET /api/journals/rankings/{ranking} cfp, ccf, highest_if, most_viewed, most_tracked, all. none
GET /api/statistics Totals, upcoming deadlines by month, country / impact-factor / publisher distributions. none
GET /api/conferences/{id} Full detail: CFP text, acceptance-rate history, edition history, ratings, comments, related venues. account
GET /api/journals/{id} Full detail: CFP text, special issues, ratings, comments, related venues. account
GET /api/researchers/{id} A researcher's public profile: institution, auto-generated research-interest summary, CV, tracked / attended venues. Never includes contact details; by id only — there is no researcher search or enumeration. account
POST /api/login Exchange account credentials for a JWT. none

Paginate any list with page and per_page (max 100). Full machine-readable contract: OpenAPI 3 schema.

MCP server (for AI agents)

A native Model Context Protocol server speaks Streamable HTTP at POST https://www.myhuiban.com/mcp, and is listed in the official MCP registry as com.myhuiban.www/conference-partner. Add it to any MCP client, for example: 

claude mcp add --transport http huiban https://www.myhuiban.com/mcp

Eight tools: search_conferences, search_journals, list_conferences, list_journals, get_conference, get_journal, get_researcher, get_statistics. The search tools take the same optional filters as the REST search endpoints (research field across 14 computer-science areas, ranks, and submission / conference date ranges) — the two surfaces are backed by the same query layer and return byte-identical payloads.

These work with no credentials: search_conferences, search_journals, list_conferences, list_journals, get_statistics. The three detail tools (get_conference, get_journal, get_researcher) need a token — see below.

Every MCP tool has a REST twin (get_researcher ↔ GET /api/researchers/{id}, and so on): the two surfaces run the same query layer and return identical payloads, so you can switch transports without changing how you parse anything.

Getting a token for detail endpoints

  1. Register a free account at myhuiban.com/registration and verify your email.
  2. Exchange the credentials for a JWT: 
    curl -X POST https://www.myhuiban.com/api/login \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]","password":"..."}'
  3. Send it on every request: Authorization: Bearer <token>

Account tokens are valid for about six months and raise the quota to 200 requests per day, shared across the REST API and the MCP server. Need more, or a bulk export? Email [email protected] and tell us about your use case.

Quotas and status codes

  • 200 — success. Check X-Quota-Remaining for what is left today.
  • 401 — this endpoint needs a token (only the per-venue detail endpoints do).
  • 402 — your account's daily quota is used up.
  • 429 — the anonymous per-IP daily quota is used up; register a free account for a much higher limit.

Terms of use

The API is read-only and free to use, including in commercial products, as long as you attribute Conference Partner and link back to the venue's page on this site — every response includes a detail_page URL for exactly that purpose. Please keep one request per second or slower when crawling lists, and do not redistribute the dataset in bulk. For dataset licensing or model-training use, contact us first. See also our methodology for where the rankings and data come from.

Other machine-readable entry points

Questions, bug reports or a use case you want us to support: [email protected].