Twitter card validation persistent error

cards

#1

We have a Twitter card that is trying to post to an API. We’ve verified that the request has all the necessary parameters. We’ve also verified that the API call is correct by using Paw and Curl. The call returns a 200 ok response.

We then changed the post url and parameters to just call an endpoint that returns a 200 ok response. In all the cases above, the Twitter card validation returns the same response:

Are there any known issues with the twitter card validation?


#2

@gcamgomez: Could you please provide all of the requests you’re making, as well as the responses you’re seeing, so that we can try and repro this? It’s preferable that you use twurl. Thanks!


#3

@juanshishido here’s the raw request I’m making, I’m using Paw:

POST /2.0/twitterCard HTTP/1.1
Authorization: ***** Hidden credentials *****
Content-Type: application/json; charset=utf-8
Cookie: XSRF-TOKEN=eyJpdiI6IjhZK3liYmhqd2Y2TUlkSHRybHB5aEE9PSIsInZhbHVlIjoib3JzXC9udHlERXpqZ3RDdExOOFhcL1wvb21cL1VUSmQzT0J5M1ZjNW5PcFdSN1BaZ0lJMkpjemNDc2xrNkgrNlQ4SUFpQmYyU0QrU3NtcEw2SkVnM09uTEFBPT0iLCJtYWMiOiJmMWNmMWU0ZTJkMjBlNmIzYTMxOGIyNjg5OWRjNjU0ODNmMmVmMzkyM2FiYWEyMDJjNjBlNDkxNDVkMDg1OWU1In0%3D; phone2action-production=eyJpdiI6InpNaUE4YzBGaXBuOVdEKzRJa3ltc0E9PSIsInZhbHVlIjoiamdjZmI4Tk9SdGIzN3ltWFEzUGlJTVp1TFwvbEFTY3pRZG9iODBnS21GR0NhOUlycFdkdWNrU1J0Zk9Cd0hkZXRXTnBuUVF2U3MzN0lvREpXMEs0SGFBPT0iLCJtYWMiOiIwNzI0MjNlNGU3OWRmMGExYWMxNTM2NmIxNDIzN2E2Yjk4ZTk5NzJkOWI2ZTc3YTZmOWU2ZDYyYzkzZmVhNjYyIn0%3D; p2a-completed-campaigns=eyJpdiI6ImlLWDd2NDZ5WWxzblRySitGNVFGZnc9PSIsInZhbHVlIjoiWUZvNEFPQ1ZnZ1JzUFB6dktqRDNyYVp1UFNOU0c0UDY1TEkwY1BRVzc0YkxEVmRGUkpDUnB6YWlHYU5XaG8rbDNadU9DY3NSZlpcL3k0VUFtTWw4cUdRPT0iLCJtYWMiOiI0ZTQxMDJhZDIxNzVkOWRjYmEwZmJiZjEyYjI4M2RmMDA1NGM1YjZkN2JmZDE0Yzg4YWUzYzYwMDQzMTU0MDZjIn0%3D
Host: api.phone2action.com
Connection: close
User-Agent: Paw/3.0.12 (Macintosh; OS X/10.11.2) GCDHTTPRequest
Content-Length: 177

{"campaignid":"4838","name":"NSBAC","email":"kshek@nsbac.org","screen_name":"NSBActionCenter","tw_userId":"1242314714","card":"27gbu","token":"b58eca6e778882155abfe367e4747744"} 

Here’s the response i’m seeing:

HTTP/1.1 200 OK
Access-Control-Allow-Methods: GET, POST, OPTIONS, PUT, PATCH
Access-Control-Allow-Origin: *.phone2action.com
Cache-Control: no-cache
Content-Type: application/json
Date: Mon, 17 Oct 2016 16:11:29 GMT
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Server: Apache
Set-Cookie: XSRF- TOKEN=eyJpdiI6IjhZK3liYmhqd2Y2TUlkSHRybHB5aEE9PSIsInZhbHVlIjoib3JzXC9udHlERXpqZ3RDdExOOFhcL1wvb21cL1VUSmQzT0J5M1ZjNW5PcFdSN1BaZ0lJMkpjemNDc2xrNkgrNlQ4SUFpQmYyU0QrU3NtcEw2SkVnM09uTEFBPT0iLCJtYWMiOiJmMWNmMWU0ZTJkMjBlNmIzYTMxOGIyNjg5OWRjNjU0ODNmMmVmMzkyM2FiYWEyMDJjNjBlNDkxNDVkMDg1OWU1In0%3D; expires=Mon, 17-Oct-2016 18:11:29 GMT; Max-Age=7200; path=/; domain=.phone2action.com
Set-Cookie: phone2action-production=eyJpdiI6InpNaUE4YzBGaXBuOVdEKzRJa3ltc0E9PSIsInZhbHVlIjoiamdjZmI4Tk9SdGIzN3ltWFEzUGlJTVp1TFwvbEFTY3pRZG9iODBnS21GR0NhOUlycFdkdWNrU1J0Zk9Cd0hkZXRXTnBuUVF2U3MzN0lvREpXMEs0SGFBPT0iLCJtYWMiOiIwNzI0MjNlNGU3OWRmMGExYWMxNTM2NmIxNDIzN2E2Yjk4ZTk5NzJkOWI2ZTc3YTZmOWU2ZDYyYzkzZmVhNjYyIn0%3D; expires=Mon, 17-Oct-2016 18:11:29 GMT; Max-Age=7200; path=/; domain=.phone2action.com; HttpOnly
Set-Cookie: p2a-completed-campaigns=eyJpdiI6ImlLWDd2NDZ5WWxzblRySitGNVFGZnc9PSIsInZhbHVlIjoiWUZvNEFPQ1ZnZ1JzUFB6dktqRDNyYVp1UFNOU0c0UDY1TEkwY1BRVzc0YkxEVmRGUkpDUnB6YWlHYU5XaG8rbDNadU9DY3NSZlpcL3k0VUFtTWw4cUdRPT0iLCJtYWMiOiI0ZTQxMDJhZDIxNzVkOWRjYmEwZmJiZjEyYjI4M2RmMDA1NGM1YjZkN2JmZDE0Yzg4YWUzYzYwMDQzMTU0MDZjIn0%3D; expires=Mon, 24-Oct-2016 16:11:29 GMT; Max-Age=604800; path=/; domain=.phone2action.com; HttpOnly
Strict-Transport-Security: max-age=31536000; includeSubDomains;
X-Frame-Options: SAMEORIGIN
Content-Length: 62
Connection: Close

{"success":1,"error":null,"type":"create","advocateid":709083}

When using the twitter card validation, I get the error screenshotted above. Even if I supply the url as “https://example.com” which should ping back a 200 ok response, the validator still says

Result: Failure. Whoops! We were not able to submit card data during our test. Please check your integration by creating a Tweet with this Card, submitting a test lead, and confirming if the lead was submitted to your CRM or marketing automation system. If you are unable to successfully send lead data to your system, please double-check the data settings for this Card to ensure it is setup correctly.


#4

Thanks for providing this information, @gcamgomez. We’re continuing to try to determine the root cause of this issue. We’re treating this with high urgency and will update you once we know more. We appreciate the patience!


#5

@juanshishido has there been any updates! thanks for looking into it


#6

@gcamgomez: You can find more information here. Thanks.


#7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.