POST /collections/fork/{collection_uid}
This endpoint allows you to create a fork from an existing collection.
On successful creation of the collection, the response returns the collection name
, id
, uid
along with fork
information.
You can also specify the context of a workspace to fork a collection in by passing the workspace
as a query param.
Requires API Key as
X-Api-Key
request header orapikey
URL query parameter.
Servers
- https://api.getpostman.com
Path parameters
Name | Type | Required | Description |
---|---|---|---|
collection_uid |
String | Yes |
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Query parameters
Name | Type | Required | Description |
---|---|---|---|
workspace |
String | No |
Workspace ID is required to create a fork |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
name |
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.