#1

Hi!

We are experiencing an issue with requesting active_entities via Twitter API. Could you please help us with it?

What we do:

  1. We send GET request to https://ads-api.twitter.com/{{version}}/stats/accounts/{{account_id}}/active_entities?end_time=2022-10-27&entity=PROMOTED_TWEET&start_time=2022-10-26
    We tried different dates. Week/month range - does not matter, it’s all the same.

  2. We get 503 Service Unavailable

  3. If we send the same request for some other entity (e.g. entity=CAMPAIGN) we get valid data.

What can be the reason for that?

account_id that we try to fetch stats for is 18ce55339ma. Our app id is 9130162.

#2

Hello,

Thanks for reaching out. We are currently researching on this issue. We will update again

2 Likes
#4

Thank you. We are awaiting.

#5

Hi! I wanted to ask if you have any news to share regarding this case? This has become a major blocker as we are not able to provide service to one of our top customers.

We’d really appreciate if you can prioritize this and provide a quick resolution. Thanks :raised_hands:

#6

Hey,

I have escalated to the team in charge of this. Still awaiting for a response from them.

1 Like
#7

Hey! Any updates?

#8

@jessicagarson @IgorBrigadir hey! Are there any updates on this one? We would really appreciate someone looking into this.

#9

Thanks, @SofiaBoSmartly. I just looked into this internally and saw this had been added to the backlog. I cannot provide an ETA at this time, but I do know the team is currently aware of this.

1 Like
#10

Thanks @jessicagarson really appreciate your response! For context, I would like to accentuate that the impacted customer is a significant spender and we really hope you can prioritize this request. Thanks a lot!

#11

Thanks, @Dev_Smartlyio. I added a note to our internal ticket on this.

#12

Hello! Are there any updates to share regarding this case? Really appreciate if someone can look into this :purple_heart:

#13

Hey! Any updates here?

#14

Hi @SofiaBoSmartly, thank you for your patience!

This issue might be because this request is quite expensive, and it’s failing to complete within the enforced timeout.

Do you think you could consider narrowing the search down using optional endpoint parameters to improve latency? For example, you could include campaign_ids:

https://ads-api.twitter.com/{{version}}/stats/accounts/{{account_id}}/active_entities?start_time=2022-10-26&end_time=2022-10-27&entity=PROMOTED_TWEET&campaign_ids={{campaign_id}}

#15

I see, thank you! It indeed works when we provide campaign ids. But what is the maximum amount of the search results that we would be able to get? (we are trying to understand how many campaign_ids should be included in one request?)

#16

Hi @SofiaBoSmartly,
That would depend on the number of entities each campaign has. If there are a lot of promoted Tweets under each campaign, you would need to include a fewer number of campaign_ids. I would recommend starting at around 5 campaigns, and narrowing it down further to determine a safe number of campaigns to include for your case.