POST /repositories/{workspace}/{repo_slug}

Creates a new repository.

Note: In order to set the project for the newly created repository, pass in either the project key or the project UUID as part of the request body as shown in the examples below:

$ curl -X POST -H "Content-Type: application/json" -d '{
    "scm": "git",
    "project": {
        "key": "MARS"
    }
}' https://api.bitbucket.org/2.0/repositories/teamsinspace/hablanding

$ curl -X POST -H "Content-Type: application/json" -d '{
    "scm": "git",
    "project": {
        "key": "{ba516952-992a-4c2d-acbd-17d502922f96}"
    }
}' https://api.bitbucket.org/2.0/repositories/teamsinspace/hablanding

The project must be assigned for all repositories. If the project is not provided, the repository is automatically assigned to the oldest project in the workspace.

Note: In the examples above, the workspace ID teamsinspace, and/or the repository name hablanding can be replaced by UUIDs.

Servers

https://api.bitbucket.org/2.0

Path parameters

Name	Type	Required	Description
`repo_slug`	String	Yes	This can either be the repository slug or the UUID of the repository, surrounded by curly-braces, for example: `{repository UUID}`.
`workspace`	String	Yes	This can either be the workspace ID (slug) or the workspace UUID surrounded by curly-braces, for example: `{workspace UUID}`.

Request headers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/json"

Request body fields

Name	Type	Required	Description
`size`	Integer	No
`description`	String	No
`uuid`	String	No	The repository's immutable id. This can be used as a substitute for the slug segment in URLs. Doing this guarantees your URLs will survive renaming of the repository by its owner, or even transfer of the repository to a different user.
`has_issues`	Boolean	No	The issue tracker for this repository is enabled. Issue Tracker features are not supported for repositories in workspaces administered through admin.atlassian.com.
`created_on`	String	No
`fork_policy`	String	No	Controls the rules for forking this repository. allow_forks: unrestricted forking no_public_forks: restrict forking to private forks (forks cannot be made public later) no_forks: deny all forking Possible values: `"no_public_forks"` `"no_forks"` `"allow_forks"`
`has_wiki`	Boolean	No	The wiki for this repository is enabled. Wiki features are not supported for repositories in workspaces administered through admin.atlassian.com.
`links`	Object	No
`links.html`	Object	No	A link to a resource related to this object.
`links.html.href`	String	No
`links.html.name`	String	No
`links.watchers`	Object	No	A link to a resource related to this object.
`links.watchers.href`	String	No
`links.watchers.name`	String	No
`links.self`	Object	No	A link to a resource related to this object.
`links.self.href`	String	No
`links.self.name`	String	No
`links.commits`	Object	No	A link to a resource related to this object.
`links.commits.href`	String	No
`links.commits.name`	String	No
`links.forks`	Object	No	A link to a resource related to this object.
`links.forks.href`	String	No
`links.forks.name`	String	No
`links.clone[]`	Array	No
`links.clone[].href`	String	No
`links.clone[].name`	String	No
`links.hooks`	Object	No	A link to a resource related to this object.
`links.hooks.href`	String	No
`links.hooks.name`	String	No
`links.pullrequests`	Object	No	A link to a resource related to this object.
`links.pullrequests.href`	String	No
`links.pullrequests.name`	String	No
`links.avatar`	Object	No	A link to a resource related to this object.
`links.avatar.href`	String	No
`links.avatar.name`	String	No
`links.downloads`	Object	No	A link to a resource related to this object.
`links.downloads.href`	String	No
`links.downloads.name`	String	No
`is_private`	Boolean	No
`scm`	String	No	Possible values: `"git"`
`name`	String	No
`full_name`	String	No	The concatenation of the repository owner's username and the slugified name, e.g. "evzijst/interruptingcow". This is the same string used in Bitbucket URLs.
`type`	String	Yes
`updated_on`	String	No
`language`	String	No

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.