Is Bitbucket API down?
Asked by Alice Biometrics:

Hello,

We are using Bitbucket's API in cron jobs and since 2 days ago API requests are returning 500 errors with the following message:![image.png](/t5/image/serverpage/image-id/289666i7B3E05F24DB7598A/image-size/large?v=v2&px=999 "image.png")

However, the [status](https://bitbucket.status.atlassian.com/) page doesn't report any trouble.

Is anybody else experiencing problems?

Thanks


Answers:
author: Theodora Boudale
body: Hi Alice and welcome to the community!

We haven't had an incident affecting our APIs during the last few days.

Could you please let me know the following:

* Which API endpoint is showing this error?
* Run this API call with curl and share the call you are running (after sanitizing private/sensitive data) and the full output you get from the curl command

Kind regards,  
Theodora

comments: author: Alice Biometrics
body: Hi Theodora,

The cron job is executed twice a day and it didn't work from **October 31** to **November 4**.

The first API endpoint that is called in this job is [listing repositories in a workspace](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/#api-repositories-workspace-get). This was the output of a Insomnia call:

```

* Preparing request to https://api.bitbucket.org/2.0/repositories/theworkspace?pagelen=1
* Current time is 2023-11-02T06:53:12.836Z
* Enable automatic URL encoding
* Using default HTTP version
* Enable timeout of 500000ms
* Enable SSL validation
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS alert, close notify (256):
* 0 bytes stray data read before trying h2 connection
* Found bundle for host api.bitbucket.org: 0x10b16ffa0 [can multiplex]
* Trying 18.205.93.6:443...
* Connected to api.bitbucket.org (18.205.93.6) port 443 (#1)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=US; ST=California; L=San Francisco; O=Atlassian US, Inc.; CN=*.bitbucket.org
* start date: Apr 28 00:00:00 2023 GMT
* expire date: Mar 28 23:59:59 2024 GMT
* subjectAltName: host "api.bitbucket.org" matched cert's "*.bitbucket.org"
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
* 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
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* Using Stream ID: 1 (easy handle 0x1341c1800)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):

> GET /2.0/repositories/theworkspace?pagelen=1 HTTP/2
> Host: api.bitbucket.org
> user-agent: insomnia/0.2.1-b
> authorization: Basic BlahBlahBlah
> accept: */*

* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection state changed (MAX_CONCURRENT_STREAMS == 32)!
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):

< HTTP/2 500 
< content-type: text/html
< date: Thu, 02 Nov 2023 06:54:14 GMT
< content-length: 3989


* Received 3.9 KB chunk
* Connection #1 to host api.bitbucket.org left intact
```

I'm assuming the service was experimenting issues those 5 days that are fixed now.

Thanks.


author: Theodora Boudale
body: Hi Alice,

Thank you for the update, it's good to hear that the issue is resolved.

I see no incidents affecting our API during that time and we cannot investigate what happened if the issue is no longer occurring. If you ever come across such an error again, please feel free to reach out.

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud