Hi Yury
By the same token, a different customer might want to know how much she will be paying for a-la-carte VoDs in a TV subscription.
TMF Open API has not attempted to give models of specific telecommunications products, and so there will not be any APIs that relate to Mobile, or to TV, or to any other specific product.
You can, of course, extend the model (Product, ProductSpecification) to create specific strongly-typed catalog entities and instances for Product, and build APIs for those. This is one of the use cases for the @type and @baseType fields. The question you need to ask yourself is whether it is worth the effort to update your software by adding each time you want to create a new line-of-business (i.e. ProductSpecification).
If you keep with the generic catalog model, then when you GET a ProductOffering that includes a roaming ProductSpecification, you could expect to retrieve with it the various ProductOfferingPrice that encode the roaming prices. Here also you might need an extension since you may not want to define a ProductOfferingPrice for each roaming destination, and POP does not (yet) support the concept of a table-driven price.
Hope it helps.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------
Original Message:
Sent: May 02, 2019 08:59
From: Yury Bury-Burymski
Subject: API to provide information about prices in roaming
I would like to find a suitable data model and API specification for providing pricing information for mobile calls in roaming.
User story: "As a user, I want to see the cost of roaming in order to know how much I will pay abroad."
I expect to find an API that returns dozens or hundreds of prices grouped by country \ network \ price_zone.
------------------------------
Yury Bury-Burymski
A1 Group
------------------------------