API Readiness Checklist

January 20, 2026 ยท View on GitHub

Checklist for api-name api-version in rx.y.

NrAPI release assetsalpharelease-candidateinitial
public
stable
public
StatusReference information
1API definitionMMMMrelative link
2Design guidelines from Commonalities appliedOMMMComm. release nr
3Guidelines from ICM appliedOMMMICM release nr
4API versioning convention appliedMMMM
5API documentationMMMMin yaml (or relative link)
6User storiesOOOMrelative link
7Basic API test cases & documentationOMMMrelative link
8Enhanced API test cases & documentationOOOMrelative link
9Test result statementOOOMissue link
10API release numbering convention appliedMMMM
11Change log updatedMMMMrelative link
12Previous public release was certifiedOOOMcomment
13API description (for marketing)OOMMwiki link

To fill the checklist:

  • in the line above the table, replace the api-name, api-version and the rx.y by their actual values for the current API version and release.
  • in the Status column, put "Y" (yes) if the release asset is available or fulfilled in the current release, a "N" (no) or a "tbd". Example use of "tbd" is in case an alpha or release-candidate API version does not yet provide all mandatory assets for the release.
  • in the Reference information column, provide the relative links (from the API repository home folder) to the release asset once available, the applicable release numbers (not versions) of Commonalities and ICM, and any other relevant links or information.
  • For the point 12: The Reference information comment shall reference a note (e.g. "see (1)") under the checklist table to be added that states the certified company(s) as can be found on the following link: GSMA Open Gateway Portal (see the MAP for API deployments).

Note: the checklists of a public API version and of its preceding release-candidate API version can be the same.

The documentation for the content of the checklist is here: see API Readiness Checklist section in the API Release Process.