DeviceSwap API - Integrate it into SIMSwap API

[QaunainM]

Hi all, I had a suggestion, based on how things are panning out on the ground.

Context

• The current CAMARA approach is to make lots of separate small APIs, i.e. SIM Swap, Device Swap, Device Status (Roaming), Device Status (Reachability), etc
• But some of these APIs are very similar and complementary to each other, i.e. SIM Swap + Device Swap, or Device Reachability + Device Roaming

Problem

• If these similar and complementary APIs are separate APIs and not just endpoints of one API, then it means that Telcos have separate roadmaps and release to market plans for each one
• For these APIs to get real-world they need 'full country coverage', at least by MNOs in the first instance'

Idea / Proposal

• Make less APIs and make the similar / complementary features endpoints
• For example, the SIM Swap API currently has endpoints for; /check (True:False) and /retrieve-date (Timestamp), so if it had another endpoint for /device-swap then it means it would get country coverage much quicker which will lead to quicker and more adoption and usage

[bigludo7]

Hello @QaunainM
Ah the topic of API granularity ! a recurrent topic :)

We had a long discussion in Commonalities (and I saw you raise the question there) and the approach was to prefer granular API and one of the main reason is to have implementation providing the API full scope (a kind of all or nothing). From a developer/API customer we do not want to provide partial implementation.

[QaunainM]

@bigludo7 , makes sense and its a sensible approach, the only thing to consider is that getting each API to market (full coverage per a country) will take longer as each API will have its own supply chain.