Skip to content

Conversation

@ALIIQBAL786
Copy link
Contributor

What type of PR is this?

Add one of the following kinds:

  • enhancement/feature

What this PR does / why we need it:

This PR adds xFlow Research - Ali Iqbal as owner of the IMEI fraud API proposal and also adds OAS yaml file for the API.

Which issue(s) this PR fixes:

fixes #63

Special notes for reviewers:

The enum for device check are allowed | prohibited | tracked and the additional information can be provided when it is prohibited
" - lost
- stolen
- blacklisted
- blocked
- fraud
- non-payment
- regulatory"

Changelog input



Additional documentation

This section can be blank.

docs

Updating IMEI Fraud API proposal
Uploading IMEI FRAUD API OAS
Removing the Device Registers lists in the response
Not validated with real customer
Copy link
Contributor

@albertoramosmonagas albertoramosmonagas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Expanded the IMEI Fraud API proposal with detailed sections on API family name, owner, summary, business cases, technical and commercial viability, and validation status.
@ALIIQBAL786
Copy link
Contributor Author

@albertoramosmonagas Thank you for informing me about the new template, I have adjusted my proposal according to new template.

@albertoramosmonagas
Copy link
Contributor

Minutes from meeting with GSMA: Ali (Xflowresearch), Rebecca (MTN), Mark (GSMA), Jason (GSMA) and Hugo

  • (GSMA)Conclusion: All parties see value in pursuing IMEI Fraud API within the Device Identified groupMeeting notesAlignment on IMEI Fraud Detection API: Ali from Xflow Research, Rebecca from MTN, Hugo from GSMA, Jason, Mark, and Reg discussed the IMEI Fraud Detection API, clarifying its purpose, input parameters, status definitions, and the need for alignment between CAMARA, MTN, and GSMA to ensure the API meets operator and stakeholder requirements.
  • Clarification of Related Fraud Detection APIs: Rebecca clarified the distinction between the IMEI Fraud Detection API under discussion and MTN's broader Mobile Fraud Detection API, which includes SIM swap, device swap, and device distance features, ensuring all participants understood the scope of the current meeting.

Co-authored-by: Alberto Ramos Monagas <alberto.ramosmonagas@telefonica.com>
Copy link
Collaborator

@jgarciahospital jgarciahospital left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jgarciahospital jgarciahospital merged commit 79c13ae into camaraproject:main Nov 15, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New API Proposal from Chenosis : IMEI Fraud Check API

3 participants