Hi all,
According to the current Store REST API of APIM 3.0, using Subscription
resource[1], we can get the subscription details for a particular API.
The subscription resource is as follows.
*{*
*applicationId : "75834e14-d445-4e98-b90a-e2b726718384",*
*lifeCycleStatus : "ACTIVE",*
*policy :
If we introduced both API info DTO and application info DTO as attributes
of subscription info DTO it would be bulky(publisher API info DTO will have
lot of unwanted fields for this use case). If we follow rest API best
practices ideally we should send ids of application and API like we do
now. On
According to this article [1] also, it agrees to send only the mandatory
details in the response. Otherwise we may need to process over-complicated
responses (which contains unwanted information) if we include all API,
Application details in Subscription.
[1]
http://51elliot.blogspot.com/2014/06/r
Hi Chamin/Sanjeewa,
Thank you for the response.
If so, is it okay to allow a large number of multiple API calls for such
scenario?
Or, as Sanjeewa has mentioned, while following REST API best practices, we
could go with the option to send the application name along with the
application ID.
Rega
Hi,
I think what Dushani suggested is to include some essential application or
API fields in subscription response. For example: sending the name of the
API, version and provider as APIInfo and name of the application and the
app creator as the application info. When someone trying to list down
su
