Welcome to the GitHub of the CAMARA technical project. General information about the project can be found on the Website, within the Wiki and in the Governance repository. Please read the Project Charter if you want to know what CAMARA and its APIs are about.

CAMARA brings together multiple APIs, repositories, and working groups. The right starting point depends on what you are looking for.

If you want to understand which APIs exist, which sub-project or working group owns them, and their current maturity, CAMARA provides multiple entry points depending on the level of detail you are looking for:

👉 CAMARA API Overview (website)

👉 CAMARA API Portfolio (interactive, cross-release)

Both entry points provide access to CAMARA APIs and link to their corresponding API descriptions.

The API Overview is well suited for a high-level introduction and browsing by topic. The API Portfolio provides a detailed, up-to-date view across releases, ownership, and maturity.

Together, these are the recommended entry points for visitors, architects, and decision makers.

If you already know which API you are interested in:

Start with the API Portfolio and select the API (for implementation, use the latest meta-release, currently Fall25), then follow the link to the API repository release on GitHub, read the repository README and API documentation, and review the published OpenAPI and test specifications. If you are looking for live implementations offered by operators, see the GSMA Open Gateway operator map.

If you are implementing an API, you may also need:

• Security and Interoperability Profile and Access and User Consent Management (Identity & Consent Management)
• CAMARA API Design Guide and further documents such as the API Testing Guidelines in the Commonalities repository

These documents are maintained by the respective working groups and apply across APIs. When implementing an API from a specific meta-release, use the corresponding release of these documents.

If you want to join discussions, attend meetings, or contribute, you will need access to CAMARA's collaboration and communication tools.

Start here:

• Getting Started with CAMARA (community tools & access)

This page explains how to set up a Linux Foundation ID (LFID) and SSO, how to join mailing lists and Zulip channels, and how CAMARA collaboration is organized.

Participation in CAMARA is free for individuals.

Organizations may choose to join CAMARA as a Participating Organization or as a member/sponsor, which provides additional involvement, representation, and influence in the project:

👉 Join CAMARA – organizational participation and membership

If you plan to contribute changes (specifications, tests, documentation), start with the following entry points:

• Contributing Guidelines (project-wide contribution process), Project Charter and Project Structure and Roles
• Commonalities (API design guidelines and common artifacts)
• Identity and Consent Management (if you want to contribute to security, identity, or consent topics)
• Propose a new API (API onboarding and lifecycle)

Each repository contains its own README; contribution guidance is typically found across the README, issues, meeting information, minutes, and existing practice.

If you are a maintainer, codeowner, or release manager, start with the following entry points:

• API Release Guidelines (release process and rules)
• API Readiness Checklist (release requirements)
• CAMARA wiki pages for meta-release milestones and coordination

Release coordination and cross-repository status tracking are currently handled through the wiki (as used for the Fall25 meta-release). As the new release process is rolled out, maintainers and codeowners will increasingly declare release intent via release-plan.yaml, with automation taking over much of the manual tracking, while the authoritative rules continue to live in GitHub repositories.

This page is intentionally kept concise. If you are unsure where to go next, browse the CAMARA wiki for meeting minutes, working groups, and release tracking, or explore the Governance, Release Management, Commonalities, Identity and Consent Management, and API Backlog repositories for project-wide rules and guidelines.