Enabling Pipeline in Bitbucket Cloud using REST API doesn't work suddenly

[Akshay b]

I have been enabling the Bitbucket Pipeline using REST API.

It was working fine for more than a year. But for the last couple of days, I am not able to enable the pipeline. It gives me the below error:

ERROR:

{"type": "error", "error": {"message": "Resource not found"}}

CURL:

curl --url "https://api.bitbucket.org/2.0/repositories/{organization_name}/{repo_slug}/pipelines_config" --user XXXX:ZZZZ --request PUT --header "Content-Type: application/json" --data "{\"enabled\": true}"

Is there any change in the API?

[Caroline R]

Hi, @Akshay b! 

Thank you for reaching out to Atlassian Community!

I was able to enable Pipelines in a repository using the API you mentioned. By the error message you shared with us, the problem seems to be in the repository. If, for example, I change the repository name for some repo that doesn’t exist, I get the same error message:

{"type": "error", "error": {"message": "Resource not found"}}

With that said, could you please check if the workspace/repository name is correct? If it is, would you mind sharing the workspace/repository name here, so I can check if there is a problem with this repo? You can mask the name with ***. 

Looking forward to hearing from you. 

Kind regards,
Caroline