ComRIS API
Published 13 Apr 2026
Prepared by CompliSense Editorial Desk
Detailed Analysis
Key details
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 transactions, tracking 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 whitelisting, two-way SSL handshake, OAuth-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 opening, holding retrieval, and pledge/repledge requests.
• The security framework requires JSON-based payloads, Bearer token authentication, x-api-key usage, and a layered encryption model involving AES-256 encryption, RSA 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 generation, opening of ComRIS accounts, bulk UCC account creation, holding statement retrieval, commodity withdrawal requests, receipt status checks, warehouse details lookup, pledge and unpledge operations, buyer invoice retrieval and download, intention for delivery submission, CM payout pool transfer, payout reports, and bulk CM approval workflows.
• The document also prescribes detailed HTTP status codes, error handling logic, and application validation codes, thereby indicating that the framework is intended for production-grade integration with strict controls over authentication, message validation, field formats, duplicate 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.
Applicability
Who this applies to
- Stock brokers
- Broker operations teams
- Risk and compliance functions
- Trading members
- Operations and compliance teams
Need deeper implementation context?
Read the regulatory brief above, then use CompliSense for deeper applicability review, workflow interpretation, ownership tracking, and evidence-ready compliance execution.
Request walkthroughRelated compliance hubs
Use these hubs to connect this update with broader workflow themes, regulator archives, and practical explainers.
Content accountability
Prepared by CompliSense Editorial Desk (Regulatory Content Team).
This attribution reflects the preparation role used for CompliSense regulatory publishing.
Related compliance explainers
Practical context for teams interpreting similar obligations, deadlines, or implementation workflows.
What Firms Get Wrong in Update Logging and Closure Tracking
Published 26 Jun 2025
One Year of Regulatory Monitoring Lessons: What Still Breaks Inside Compliance Teams
Published 04 Sept 2025
Historical Search of Circulars: Why It Matters During Audits, Reviews, and Internal Escalations
Published 29 May 2025