# 31huiyi (31会议 / 31Event)

> Digital event and exhibition SaaS platform operated by Shanghai Bayantu Information Technology Co.,
> Ltd. (上海八彦图信息科技有限公司), Shanghai, China, founded 2010. Products cover conference management
> (31大会易), lightweight event management (31轻会), exhibition management (31展览云), on-site smart
> check-in and reception (31智慧现场), virtual events and an event AI assistant (31智伴).
> This file was GENERATED by API Evangelist from 31's own public documentation on 2026-09-05.
> 31 does not publish an llms.txt; https://www.31huiyi.com/llms.txt returned HTTP 404.

## API at a glance

- Name: 31 OpenAPI
- Base URL (production): https://31api.31huiyi.com
- Base URL (test): https://test2-31api.31huiyi.com
- Authorization server: https://oauth.31huiyi.com (OAuth 2.0 / OpenID Connect, IdentityServer)
- Developer center: https://api-help.31huiyi.com/zh/home
- Machine-readable contract: NONE PUBLISHED. No OpenAPI, Swagger, GraphQL SDL, AsyncAPI, Protobuf or
  WSDL document exists. 86 operations are documented as HTML tables across 93 developer-center pages.
- Style: RPC-over-HTTP. 85 of 86 documented operations are POST to a verb-named path under /op/,
  including reads. HTTP method does not signal safety.
- Response envelope: HTTP 200 with {businessCode, businessMessage, data} (or
  {sysCode, sysMessage, isSuccess, returnObj, pager} on the account family). Not RFC 9457.

## Getting started

- Credentials are NOT self-service. 31's integration staff issue an appKey (client id) and appSecret.
  https://api-help.31huiyi.com/zh/home
- Token: POST https://oauth.31huiyi.com/connect/token, application/x-www-form-urlencoded,
  grant_type=custom_user_code, client_id=openapi, method=client_secret,
  scope="offline_access OpenAppGateway", appKey, appSecret.
- Access token TTL 30 minutes; refresh token TTL 2 hours. Send as `Authorization: Bearer <token>`.
- OIDC discovery: https://oauth.31huiyi.com/.well-known/openid-configuration (served, HTTP 200)
- Postman collection: https://api-help.31huiyi.com/openapi.postman_collection.json (v2.1.0, 4 requests)
- Partner SSO handshake: https://api-help.31huiyi.com/zh/oauth

## Operation families (86 documented operations)

- Attendees (22) — register, bulk register, update, deregister, query, statistics, check-in code lookup,
  anonymous-ticket fill and cancel. https://api-help.31huiyi.com/zh/attendee
- Schedules (22) — sessions, categories, venues, dates, favourites, materials, create/update/delete.
  https://api-help.31huiyi.com/zh/queryScheduleList
- Events / bvents (6) — list, detail, sub-forum create/update, third-party relation.
  https://api-help.31huiyi.com/zh/getBventDetails
- Speakers (4) — list, detail, groups, scientist records. https://api-help.31huiyi.com/zh/speakerList
- Messaging (4) — auth-code and normal SMS and email. https://api-help.31huiyi.com/zh/communication
- Accounts / SSO (3) — createForClient, account update, usercode. https://api-help.31huiyi.com/zh/oauth
- Files (3) — upload by URL, upload by bytes, material PV/DL counters.
- Form center (3) — table-view add / update / delete record.
- Reception (3) — reception guests, hotels, plan statistics.
- CMS (3) — category list, content list, information detail.
- Statistics (3) — DingKe overview, time distribution, sign-in statistics.
- Exhibitors (2 + custom) — save exhibitor, update status, badge create/update, WAIC booth update.
- Identity (2) — VerifyIDCard, ThreeElementCertification (three-factor identity check).
- Check-in (2) — third-party sign-in, face recognition.
- Tickets (1) — item stock. Orders (1) — order info.

Operations under the `/op/notoken/` prefix are documented as callable without a user token (20 of 86),
including attendee registration and bulk registration, third-party sign-in, schedule/speaker/CMS reads.

## Outbound push (webhooks) — 8 event types

31 POSTs JSON to an endpoint YOU host; there is no subscription API and no payload signing.
check-in push, attendee push (V1 and V2), event push, exhibitor push, exhibit push, badge/certificate
status push, epidemic-info push. Acknowledge with {code,msg} (0 success) or {Status,Msg} (1 success).
https://api-help.31huiyi.com/zh/checkinpush

## What 31 does NOT publish

- No OpenAPI / Swagger / GraphQL / AsyncAPI / gRPC / WSDL contract.
- No MCP server, agent card, or agent-facing interface (including for the 31智伴 AI assistant).
- No SDKs or client libraries in any package registry; no CLI.
- No rate limits and no rate-limit response headers.
- No idempotency key or replay protection on any write.
- No deprecation or sunset policy; no status page; no SLA.
- No security.txt, no vulnerability-disclosure program, no trust center, no named certifications.
- No enumeration of non-zero business error codes.
- No reversal window on any of the nine documented undo operations.

## Company and commercial

- Website: https://www.31huiyi.com/
- English site: https://www.31huiyi.com/english
- Pricing: https://www.31huiyi.com/price — 31轻会 published at CNY 12,800 / 15,800 / 15,800 / 25,800 per
  year plus a quote-only premium tier; all other product lines are quote-only.
- Product updates: https://www.31huiyi.com/article/newslist_hy/update
- News: https://www.31huiyi.com/article/newslist_hy/news
- Help centers: https://lite-help.31huiyi.com, https://conf-help.31huiyi.com,
  https://expo-help.31huiyi.com, https://asst-help.31huiyi.com
- Terms: https://www.31huiyi.com/special/termsofservice
- Privacy: https://www.31huiyi.com/special/privacyclause
- Support: 400-690-3131 / https://www.31huiyi.com/home/about#concat
- ICP filing: 沪ICP备10004253号-2

## Data sensitivity

The attendee surface carries direct personal data (name, mobile, email, ID number, photo), national ID
verification and face recognition, under PRC PIPL. No consent, export or data-subject-request operation
is documented on the API.