MCXmediumFullMCXCCL/TECH/074/2026

ComRIS API

Issue Date: 11 Apr 2026

Detailed Analysis

Key details

View original circular

MCX Clearing Corporation Limited, vide Circular No. MCXCCL/TECH/074/2026 dated April 11, 2026, has announced an important update regarding ComRIS API framework for integration with external member environments.

Key Details of the Update –
• The circular states that, pursuant to MCXCCL circular no. MCXCCL/TECH/019/2026 dated January 29, 2026, the ComRIS API Framework has been introduced for integration with the external environment, with the objective of facilitating seamless transactionstracking of eWHR, and improving operational efficiency for Clearing Members.
• Members desirous of integration are required to submit their interest through the API subscription request form hosted on www.mcxccl.com, after which the connectivity guidelines will be shared separately with the concerned Clearing Member by email.
• The attached Annexure I contains a detailed API Specification Document setting out the architecture, security design, request-response standards, headers, encryption process, and endpoint-wise data requirements.
• As shown in the architecture flow diagram in Annexure I (pages 4 and 5), the framework is structured around IP whitelistingtwo-way SSL handshakeOAuth-based token authentication, and an API gateway model, under which member systems first obtain an authentication token and then use that token for further activities such as account openingholding retrieval, and pledge/repledge requests.
• The security framework requires JSON-based payloadsBearer token authenticationx-api-key usage, and a layered encryption model involving AES-256 encryptionRSA encryption of the dynamic secret key, and SHA256withRSA digital signatures, with all critical values required to be transmitted in Base64 encoded form.
• The API specification provides a broad operational interface covering several functions, including OAuth2 authorization token generationopening of ComRIS accountsbulk UCC account creationholding statement retrievalcommodity withdrawal requestsreceipt status checkswarehouse details lookuppledge and unpledge operationsbuyer invoice retrieval and downloadintention for delivery submissionCM payout pool transferpayout reports, and bulk CM approval workflows.
• The document also prescribes detailed HTTP status codeserror handling logic, and application validation codes, thereby indicating that the framework is intended for production-grade integration with strict controls over authenticationmessage validationfield formatsduplicate requests, and business rule failures.
• Overall, the circular is operational in nature and serves to notify Clearing Members of the availability and process for adoption of the ComRIS API, while the annexed technical document provides the implementation standards necessary for secure system integration.

Actions if Any –
• Members who wish to integrate the ComRIS API with their environment must submit their interest through the API subscription request form on www.mcxccl.com.
• Concerned members should review the API Specification in Annexure I and prepare their systems in line with the prescribed authentication, encryption, connectivity, and endpoint requirements.
• Members undertaking integration should coordinate with MCXCCL for the connectivity guidelines and implementation support to be shared separately by email.


Sources

Primary source(s)

Refer to the official regulator publication for source language and formal applicability details.

Timeline

Key dates and timeline

Issue date
11 Apr 2026
Effective date
Not specified
Deadline
Not specified
Current state
Full

Applicability

Who this applies to

  • Stock brokers
  • Broker operations teams
  • Risk and compliance functions
  • Listed companies
  • Brokers and trading members
  • Investment intermediaries

Related compliance hubs

Editorial Attribution

Prepared by CompliSense Editorial Desk (Regulatory Content Team) and reviewed by CompliSense Regulatory Review Desk (Compliance Review Team).

Last updated: 13 Apr 2026

Need deeper implementation context?