API description checklist compliance review for Brand Registration marketing page

[anthorange]

Problem description
This issue is based on the Camara Marketing “Checklist for API description review”:
https://github.com/camaraproject/Marketing/blob/main/documentation/SupportingDocuments/Checklist_for_API_description_review.md

The Brand Registration API page reviewed:
https://camaraproject.org/brand-registration/

The page has checklist compliance gaps for:

• API Description (the image is only illustrative)
• Use Cases (text format / missing GSMA Use Case Library links)
• Sub Project Wiki (incorrect prefix / no link)

Expected action
Please update the Brand Registration API documentation page so it matches the checklist by applying the following corrections:

1. API Description

• The image is currently illustrative and does not clearly represent a “typical use case” workflow/value for developers (as expected by the checklist).

2. Use Cases

• Use case name should be in bold (none of them are).
• Add GSMA links that match appropriate use cases: https://www.gsma.com/solutions-and-impact/gsma-open-gateway/gsma-open-gateway-resources/?category=use-cases. I couldn't find any relevant use case for this API so I'm linking to the main use cases page.

3. Sub Project Wiki

• The correct prefix is "Sub Project Wiki:" (current prefix: "SubProject Wiki:")
• No link available in the section, just a pointer to the API Wiki section. Proposal: inline the link to the Verified Caller API wiki in this section as well.

Additional context
Checklist reference:
https://github.com/camaraproject/Marketing/blob/main/documentation/SupportingDocuments/Checklist_for_API_description_review.md

Reviewed page export:
https://camaraproject.org/brand-registration/

[alpaycetin74]

Thank you, @anthorange

We do not manage the https://camaraproject.org/brand-registration/ page.

We can update https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/232226831/Brand+Registration+API+Description if you need us to. If yes, could you provide more specific details for this page? Thank you.

[GillesInnov35]

@anthorange , I've tried to transfer this issue to Marketing Repository which is in charge of CAMARA marketing web Page. But it seems not to work.
Could create issues (Brand-Registration, Verified-Caller) in Marketing Repo ? thanks
Gilles

[MarkusKuemmerle]

Hello,

the CAMARA outreach team is currently reviewing all the API descriptions to improve it and make it attractive for customers and developers. There is some confusion how to handle and solve the findings. I would like to give the following recommendations:

• Findings in the text of API description, Use Cases, Benefits: These should be solved by the Sub Project, changes should be documented in the API description Wiki page, and then the Sub Project should open an issue in the Marketing repo to change the website. This follows the defined process description to change the website.

• Findings in the visuals: The Sub Project should give instructions to improve the visuals following the criterias defined in the checklist. The instructions also can be included in the wiki page and addressed to the outreach team by issue in the Marketing repo. We plan to ask the LF creative team to generate new visuals for us based on these instructions.

• Findings on the right column (with all the links): Reviewers should put these findings in the review xls and not in the issue. Sub Projects cannot solve it. The CAMARA outreach team is taking the findings from the xls and is changing the website.

So please work on 1. and 2. and ignore 3. in the first comment above.

Hope that helps, Markus

[alpaycetin74]

Hello,
I'd like to add a few comments.

1. re:
   API Description
   The image is currently illustrative and does not clearly represent a “typical use case” workflow/value for developers (as expected by the checklist).

An appropriate image would clearly display a company name and optionally a logo on the device screen, e.g.:

or

I prefer not to put pictures from the web on the subproject wiki page as there may be copyright issues, or it may look like favoring a company. I would recommend mockups with imaginary company names be generated for the marketing page.

2. re:
   Use Cases
   Add GSMA links that match appropriate use cases: https://www.gsma.com/solutions-and-impact/gsma-open-gateway/gsma-open-gateway-resources/?category=use-cases

I couldn't find any use case for our APIs link in GSMA portal, either.
There is only this case study document from Vodafone, which contains some useful information:
https://www.gsma.com/solutions-and-impact/gsma-open-gateway/wp-content/uploads/2026/04/Vodafone-Calling-Service-Case-Study.pdf

Thank you

[alpaycetin74]

hello,
now also added image generation instructions to the API description page:
https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/232226831/Brand+Registration+API+Description

@anthorange please let us know if you need further information.

[alpaycetin74]

Closing due to inactivity. @anthorange please let us know if you need further input. Thank you.

[MarkusKuemmerle]

@alpaycetin74 Thx for updating the wiki page. We've been waiting for an issue in the marketing repo as trigger to update the website. I've now created it, we'll do the update in the next days

[MarkusKuemmerle]

Website updated 10.08.2026