@andrs
bump => any thoughts on this issue? @k4rliky has a really good point. My issue is the same as well, and it is from this forum post. How can we create an App via the Twitter Ads API?
If anything, I just want to understand what the point of the APP_LISTs API endpoint is, if it is not to manage, retrieve and use the Apps? It is really very painful to expect and ultimately force the end user to know the APP ID per platform when creating an App card.
Is there a way that you can amend the GET accounts/:account_id/app_lists endpoint to provide the details of the apps related to the account? The POST accounts/:account_id/app_lists does this already. For instance, consider the following:
Request:
twurl -H "https://ads-api.twitter.com" "/0/accounts/18ce53y91ub/app_lists?name=Twitter by Hyfn&app_store_identifiers=com.twitter.android,333903271"
And here is the response.
Response:
{"data_type"=>"app_list", "data"=> {"id"=>"16nyt", "name"=>"Twitter by Hyfn", "apps"=> [{"app_store_identifier"=>"333903271", "os_type"=>"iOS"}, {"app_store_identifier"=>"com.twitter.android", "os_type"=>"Android"}]}, "request"=> {"params"=> {"app_store_identifiers"=>["com.twitter.android", "333903271"], "name"=>"Twitter by Hyfn", "account_id"=>"18ce53yrq2p"}}}
It would be really great if someone could confirm if there are any plans to have the GET accounts/:account_id/app_lists provide these same details.
If not, can you please let me know why this APP_LISTS feature exists, and what to use it for?