Hey,
For at least the last day, we’ve been unable to make any successful calls to the Sandbox Ads API.
It seems to respond with a 503 with an empty body to every request.
Is anyone else experiencing this?
~ % curl -v 'https://ads-api-sandbox.twitter.com/12/accounts?oauth_consumer_key=[CONSUMER_KEY]&oauth_token=[OAUTH_TOKEN]&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1672137338&oauth_nonce=[OAUTH_NONCE]&oauth_version=1.0&oauth_signature=[OAUTH_SIGNATURE]'
* Trying 104.244.42.131:443...
* Connected to ads-api-sandbox.twitter.com (104.244.42.131) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=US; ST=California; L=San Francisco; O=Twitter, Inc.; CN=*.twitter.com
* start date: Mar 7 00:00:00 2022 GMT
* expire date: Mar 6 23:59:59 2023 GMT
* subjectAltName: host "ads-api-sandbox.twitter.com" matched cert's "*.twitter.com"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS Hybrid ECC SHA384 2020 CA1
* SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x14600dc00)
> GET /12/accounts?oauth_consumer_key=[CONSUMER_KEY]&oauth_token=[OAUTH_TOKEN]&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1672137338&oauth_nonce=[OAUTH_NONCE]&oauth_version=1.0&oauth_signature=[OAUTH_SIGNATURE] HTTP/2
> Host: ads-api-sandbox.twitter.com
> user-agent: curl/7.79.1
> accept: */*
>
< HTTP/2 503
< date: Tue, 27 Dec 2022 10:39:39 UTC
< perf: 7626143928
< server: tsa_o
< set-cookie: guest_id=v1%3A167213757930803562; Max-Age=34214400; Expires=Sat, 27 Jan 2024 10:39:39 GMT; Path=/; Domain=.twitter.com; Secure; SameSite=None
< cache-control: no-cache, no-store, max-age=0
< content-length: 0
< x-transaction-id: 11c1a8f8843c58f2
< timing-allow-origin: https://twitter.com, https://mobile.twitter.com
< strict-transport-security: max-age=631138519
< x-response-time: 103
< x-connection-hash: fafee8a0a276c4f58c649ca8ed384f769d1fd7d4a5ee95ec2d5f3ad1ea4b1034
<
* Connection #0 to host ads-api-sandbox.twitter.com left intact
1 Like
Hi, same thing here, we are getting a 503 error message when making calls to the Sandbox Ads API. Can someone look into this issue?
@Jasl692 could you please help escalate or review this? thank you very much
Hi all,
I just heard back from our engineers that the Sandbox API should be back to normal now. Please test it again!
1 Like
Hi @Jasl692, Happy New Year! Thank you so much for escalating this issue.
We are still experiencing the same error with any endpoint of the Sandbox Ads API. In this case, when trying this endpoint:
ads-api-sandbox.twitter.com/{{version}}/accounts/{{account_id}}/cards/poll
I remain attentive to your response.
Hi @Que_Te_Motiva, happy new year to you too! Our engineers are looking into this now.
Also having this issue. I was able to make a GET request to fetch a list of campaigns, but getting 503 “Service Unavailable” when attempting to create them (Sandbox env).
“Funny” enough, I can see the new campaigns being made when I subsequently fetch them - but for now, I am still getting a 503 when making the POST request.
@Que_Te_Motiva The cards endpoint should be working now, you can test again.
@EulerityVincent We’ll be looking into that.
Hi @Jasl692, thank you very much, I can confirm that the cards endpoint is working now. <3
Is there any update to this? I still get a 503 when creating a campaign in the sandbox, though it apparently is being created (I can again see it in a subsequent GET).
However, I cannot use that campaign ID to create a line item - I once again get a 503 response code, but fetching the line items after the fact does not return anything.
Any updates would be appreciated. It is difficult to test new flows as things currently stand.
