GB/T 45957-2025 in English

VALID

Information technology—Administrative service code—Interface requirements of code system

Issued on:2025-08-01
Implemented on:2026-02-01
File Format:PDF
Delivery:Via email within 5 business days

Price(USD)： $405.00
$393.00

Standard No:	GB/T 45957-2025
Document status:	VALID
Title in English:	Information technology—Administrative service code—Interface requirements of code system
Title in Chinese:	信息技术政务服务码码系统接口要求
Language:	English
File Format:	Electronic (PDF)
Delivery:	Via email within 5 business days
Issued on:	2025-08-01
Implemented on:	2026-02-01
ICS Classification:	35.240.99-IT applications in other fields
Chinese Classification:	L71-Code, character set and character recognition
Professional Classification:	GB-National Standard
Related Keywords:	information technology government service code system interface requirements information technology administrative service code interface requirements government service code interface standard government service code code deregistration interfaceprovides code deregistration service
Related Topics:	Service and Interface Requirements

《GB/T 45957-2025信息技术政务服务码码系统接口要求》由TC28（全国信息技术标准化技术委员会）归口，主管部门为国家标准委。

Introduction

Background and Significance of Standard Development

GB/T 45957-2025 "Information Technology Government Service Code System Interface Requirements", as an important part of the government service code standard system, is a key technical specification that came into being in the context of digital government construction. This standard was officially released in 2025. It was proposed and coordinated by the National Information Technology Standardization Technical Committee (SAC/TC28), and brought together the technical wisdom of more than 40 units including the China Electronics Technology Standardization Institute and the Beijing University of Aeronautics and Astronautics.

Standard Framework System Analysis

This standard, together with GB/T 45960 "Reference Model" and GB/T 45959 "System Technical Requirements", constitute the three pillars of the government service code standard system. Among them, the interface requirement standard focuses on the standardization of interactions between systems, ensuring seamless connection and secure data exchange between different government systems.

Standard number	Standard name	Main function	Interrelationship
GB/T 45960	Reference model	Establish basic framework	Upper-level guidance
GB/T 45959	System technical requirements	Specify system functions	Technical basis
GB/T 45957	Interface requirements	Specify interactive interfaces	Implementation guarantee

Analysis of core interface technical requirements

5.1 Interface format specification

The standard stipulates that the interface adopts HTTP/HTTPS protocol, is called in POST mode, the data format is JSON, and the encoding is uniformly UTF-8. The interface address format is "http://ip:port/${URL}". This design ensures both compatibility and scalability.

5.2 General structure of request data

The request data adopts a two-layer structure design: bizPackage (business request body) and sign (digital signature). Among them, bizPackage contains four mandatory fields: requestId, nonce, accessId and bizData to ensure the integrity and traceability of the request.

Data item

Type

Length

Function

Security

requestId

String

Request identifier

Anti-replay

nonce

Number 5.3 Return Data Specifications: The returned data also uses a signature mechanism and includes three core fields: code (status code), msg (description), and data (business data). For details on status code specifications, see Appendix A. Over 30 status codes are defined to cover various business scenarios.

In-depth interpretation of the seven core interfaces

6. Code collection interface

Used for individuals to apply for a government service code for the first time. The certKey, tokenSNO and channel type returned by the unified identity authentication are required. This interface records the user's code collection behavior and provides basic identity authentication for subsequent services.

7. Code generation interface

Generates the corresponding QR code string according to the code generation rules and supports setting real-person authentication requirements (sfsr parameter). The returned codeContent is the final government service code value, and genDate records the code generation time accurate to the second.

8. Decoding interface

The scanning device calls this interface to parse the code content and obtain information such as the routing segment, identity segment, and business segment. The request parameters contain rich contextual information, such as device ID, matter code, scanning time, etc., to ensure the auditability of the decoding process.

9. Code Verification Interface

Provides code status verification function, returns code verification status (validStatus), code verification time (validDate) and requester information (provinceName). The verification results are divided into success (1) and failure (0). Detailed error information must be provided in case of failure.

10. Code Collection Query Interface

Query the user's code collection status, return the applyFlag flag (true/false) and user setting information, including the authorization list (authList), valid times (availableTimes) and valid duration (duration).

11. Code Deregistration Interface

Provides code deregistration service to ensure that users can actively terminate the validity of the code during use, enhancing users' control over personal information.

12. Electronic Certificate Authorization Interface

Contains five sub-interfaces to implement comprehensive authorization management of electronic certificates:

12.1 Query Authorization Status Interface
12.2 Change Authorization Status Interface
12.3 Obtain Authorization Random Number Interface
12.4 Query Certificate List Interface
12.5 Download Certificate File Interface

In-depth Analysis of Security Mechanisms

Digital Signature Assurance

The standard requires the use of national secret algorithms such as SM2 to sign business data to ensure data integrity and non-repudiation. The signature covers all business data fields to prevent tampering.

Identity Authentication System

Based on the dual identity authentication mechanism of certKey and tokenSNO, combined with the accessId access identifier, a three-level identity authentication system is constructed to ensure the legitimacy of interface calls.

Data encryption transmission

Supports HTTPS protocol transmission. Sensitive data such as user identity (MID) is encrypted with the recipient's public key to ensure the confidentiality of the data during transmission.

Security level	Technical measures	Protection objectives	Compliance with standards
Transmission security	HTTPS protocol	Anti-eavesdropping	GB/T 32905
Data security	SM2 encryption	Anti-tampering	GB/T 32918
Identity security	Two-factor authentication	Anti-impersonation	GA/T 1723.2

Implementation Recommendations and Best Practices

System Design Phase

From the initial stage of system design, adhere to interface specifications and establish a unified interface gateway to implement common functions such as request routing, signature verification, and parameter validation, reducing subsequent development complexity.

Development and Implementation Phase

It is recommended to use an interface SDK to encapsulate common operations such as signature generation, parameter assembly, and exception handling. Focus on error code handling and retry mechanisms to ensure system stability.

Testing and Verification Phase

Establish a comprehensive library of interface test cases, covering all status codes and exception scenarios. Pay particular attention to concurrent performance and security testing to ensure stable system operation under high load.

Operation and Maintenance Monitoring Phase

Implement interface call monitoring and record request IDs to facilitate issue tracking. Establish an interface performance baseline to promptly identify abnormal call patterns and prevent security risks.

Technological Evolution and Future Outlook

With the deepening of digital government construction, the government service code interface standard will develop in three directions: first, integration with blockchain technology to achieve more tamper-proof authorization records; second, integration with artificial intelligence to provide intelligent interface scheduling and optimization; third, convergence with international standards to promote cross-border government service mutual recognition.

This standard provides a solid technical foundation for the digitalization of government services. Through standardized interfaces, it enables interconnection between different systems, truly realizing the government service vision of "one code for all services", and providing technical support for improving government service efficiency and optimizing the business environment.

More samples: YD/T 3934-2021 JGJ 94-2008 GB 50021-2001(2009)

Sample only — not a preview of GB/T 45957-2025

Loading PDF document...

Error loading PDF. Please make sure the file is valid and try again.

We also recommend

GB/T 45960-2025 in English

Information technology—Administrative service code—Reference model
2025-08-01
GB/T 38961-2020 in English

Personal health information code-Reference model
2020-04-29