Limit on Number of Countries when geo-casting

narrowcasting
targeting
geo
api

#1

Is there a limit on the number of narrowcast_place_ids you can define when publishing a tweet? I’ve noticed failures when testing with 25 & 100 place ids.


#2

Hi @grantal!

Curious: are you seeing that 25 works and 100 doesn’t? Or that it fails on both 25 and 100, but intermittently?

If intermittent, can you provide example requests for both instances?

Thanks!


#3

I was seeing it fail at 25 & 100 consistently, but succeeding at 10 targets.


#4

Here’s an example

Request Headers:
Host: api.twitter.com
User-Agent: Guzzle/3.9.3 curl/7.30.0 PHP/5.3.29
Content-Type: application/x-www-form-urlencoded; charset=utf-8
Via: 1.1 GuzzleCache/3.9.3
Authorization: [SANITIZED]
Request Post Fields:
status: michelle testing targeting
narrowcast_place_ids: 9f4e63426a3f3da2,ac26bceca6c10474,b0b7e818ce3fec3f,b4260f742fbc8d32,b631437cf2f16804,b83e1dfa68cc396c,ba1b68ac534ec439,be13fe9d62b80d9e,c027ef7e8f9b3ee2,c08f5915ceeeb806,c29833e68a86e703,c3b85cf1d8b226f2,c4320f726d222937,c659cb4912229666,cc896d5380524db4,d1531c51dd2bc3a4,d3e226ca18cd4ae8,d73762e172ac7c37,d8b99808049c05db,df4a2798d032e321,e0f46cd26fe3d713,e222580e9a58b499,e3e9c55876b99760,e44e7dc567815e87e8,e7c97cdfef3a741a,ea5eca163987d547,eb1b809cd6457a58,ee84ba0d0454651a,efc23cd34689b068,efe591bd99ea52c0,f0af1239cbebb474,f3bfc7dcc928977f,fa07565662daf560,fa1e0cb60ddedc05,fc6282dff859b848

And this is the response:
Response Headers:
HTTP/1.1 403 Forbidden
cache-control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
content-disposition: attachment; filename=json.json
content-length: 84
content-type: application/json;charset=utf-8
date: Wed, 02 Sep 2015 17:41:50 GMT
expires: Tue, 31 Mar 1981 05:00:00 GMT
last-modified: Wed, 02 Sep 2015 17:41:50 GMT
pragma: no-cache
server: tsa_b
set-cookie: lang=en; Path=/, guest_id=v1%3A144121570999671731; Domain=.twitter.com; Path=/; Expires=Fri, 01-Sep-2017 17:41:50 UTC
status: 403 Forbidden
strict-transport-security: max-age=631138519
x-access-level: read-write-directmessages
x-connection-hash: c267f47cbb3fac62a512c4511cc22084
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-response-time: 58
x-transaction: c46e6c5a4b31df75
x-tsa-request-body-time:
[2015-09-02 17:41:52] request_id=bd145f85-c4e2-4025-b78a-84cf071cf441, 0
x-twitter-response-tags: BouncerCompliant
x-xss-protection: 1; mode=block
Via: 1.1 GuzzleCache/3.9.3
X-Cache-Lookup: MISS from GuzzleCache
X-Cache: MISS from GuzzleCache
Warning: 110 GuzzleCache/3.9.3 “Response is stale”

Response Body:
{“errors”:[{“code”:190,“message”:“Status creation failed: Tweet creation failed.”}]}


#5

Quick question: have you tried subsets of the IDs to see if they work/are valid individually?

When I use the ID ac26bceca6c10474 alone, it fails with the given error. But when I do ba1b68ac534ec439,be13fe9d62b80d9e, it works fine.


#6

Ah, I have not. Thanks for the tip.


#7

Did that help? Would love to know if you’re unblocked!


#8

Not sure quite yet we need to go back and refresh all our geo-casting ids because we appear to have a fair amount of stale ids. Do how often these are updated? Can you confirm there is no hard limit when creating an organic tweet?