Getting 500 on calling a particular repo's PRs from today morning.

[Nitesh Chandel]

I have created an OAuth app. I was getting all the data from the APIs.

From today morning, for a particular repo I am getting a 500 on calling the /pullrequests API. 

This is the error message I am getting:

{
message: 'Something went wrong',
id: '67cd96d51ca449e1935e7609419c29af'
}

Is there something going on bitbucket side?

[Rilwan Ahmed]

Hi @Nitesh Chandel ,

Welcome to the community !!

some known causes of 500s on /pullrequests

• Corrupted pull request metadata in the repo.

• Pull requests referencing deleted branches.

• Excessively large diff metadata (esp. with older repos migrated from Bitbucket Server).

• API filters with malformed values (e.g. q=state="OPEN" AND something=).

Confirm the exact endpoint:
GET https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pullrequests
or something like that
GET https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pullrequests?q=...

If you have filters (like q=state="OPEN") or pagination params, note them — sometimes malformed queries trigger 500s.

Try this with curl or Postman:
curl -u username:app_password \
https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pullrequests

Try pagination explicitly
https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pullrequests?pagelen=10

If it’s reproducible only on that repo, You can:

1. Capture the exact failing request and response (status, headers, body).

2. Open a ticket with Atlassian Support → https://support.atlassian.com/contact

3. Provide the repo slug, workspace, and error ID.
   Atlassian Support can use that ID to locate the backend error logs.