Move subscription-status API to a stable status

[ToshiWakayama-KDDI]

As discussed during previous KYC-SP meetings, it may be interesting to see if subscription-status API should be moved to a stable status regarding how it is adopted and implemented by operators in countries.

(Note: KYC SP Action Item #48.13)

[ToshiWakayama-KDDI]

Hi all,

During our meeting on 2026-04-28, @albertoramosmonagas kindly shared the following information:

(1) Mandatory task to move to stable:

• API Definition,
• Commonalities compliance,
• API documentation,
• User stories,
• Test cases (basic),
• Test Cases (enhanced),
• API Description (wiki)

(2) And also:

• Demonstrate long-term specification maturity by having participated within two CAMARA release cycles with at least one Stable API version.
• Demonstrate wide market adoption across multiple companies or projects, by demonstrating that the API has been deployed within at least one complete market or by #n operators across #m markets.
• Maintainers of the Incubating Repository apply for Graduation by opening an issue in the API Backlog working group.
• The API Backlog working group will do a pre-check on behalf of the TSC, which will confirm (or not) the inclusion of the repository as Graduated.

Information is here: https://github.com/camaraproject/Governance/blob/main/documentation/API-Onboarding-and-Lifecycle.md#3-graduated-stage
camaraproject/Commonalities#589

My understanding of the above is that:

• The items in (1) are included in the API Readiness Checklist.

• Regarding the items in (2), by clicking the link 'Information is here', I can see these four bullets in '2. Incubating Stage' and these are requirements for Transition from 'Incubating Stage' to 'Graduated Stage'.

If my understanding is correct, the items in (1) are mandatory tasks for releasing a Stable API version, and the items in (2) are not required for this.

Best regards,

[ToshiWakayama-KDDI]

Hi all,

Since there is no commercial implementations according to the GSMA Open Gateway Launch Map, I feel it is a bit premature regarding the Stable V1.0.0 version of the kyc-tenure API.

WDYT?

[ToshiWakayama-KDDI]

Hi @chinaunicomyangfan , @ClownsAlbert , @ChuanyuChen , @DanXu-ChinaTelecom ,
Is it ok for us to understand that it is too early for the Stable V1.0.0 version of the subscription status API?

Thanks,