Detailed description of the Blockchain Telecom API is under section Client's API
Lite integration for Request Issuer
Usage of build-in Bot Messenger or Bubbletone mobile app simplifies all integration process dramatically. The Request Issuer should make following steps:
1. Web-account: customize Offers (localize description and setup retail prices in local currency) for its subscribers 2. Web-account: customize Bot Messenger under section "Settings / Localization" 3. Web-account: input settings of own SMPP server to provide downloading of encrypted SMS with mobile profiles 4. Web-account: upload MSISDN's of subscribers and OTA keys of SIM-cards for built-in OTA platform 5. Support an easy http-GET Credit Control request, with response 200 (OK) / 402 (Payment is required). Details are described at "A subscriber has selected one of third-party Offers" 6. Distribute Multi-Account SIM-cards among subscribers.
If you like to provide own User Interfaces for your subscribers, please learn the integration process at "Flexible integration" section.
Lite integration for Offer Assignee
That's the most optimal case for any Offer Assignee:
1. New Offers are published via Web-account 2. When a "Start a new Request" transaction is created and validated onto Blockchain, the Offer Assignee receives the "One of own Offers is selected" API call 3. If the Offer Assignee is ready to start servicing this Request, it makes "Accept a received Request" API call, with "service_data" section encrypted with the public PGP-key of the Request Issuer 4. When the service is started using by end-user, the Offer Assignee publishes "Report" transaction by making the "Report service consumption on a Request" API call, with details of the service consumption 5. All limits and validity period are controlled by the Billing system of the Offer Assignee.