POST /apps/{appId}/branches/{branchName}/deployments
Creates a deployment for a manually deployed Amplify app. Manually deployed apps are not connected to a repository.
Servers
- https://amplify.{region}.amazonaws.com
- https://amplify.{region}.amazonaws.com.cn
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
branchName |
String | Yes |
The name for the branch, for the job. |
appId |
String | Yes |
The unique ID for an Amplify app. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
X-Amz-Content-Sha256 |
String | No | |
X-Amz-Credential |
String | No | |
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
X-Amz-Date |
String | No | |
X-Amz-Algorithm |
String | No | |
X-Amz-SignedHeaders |
String | No | |
X-Amz-Security-Token |
String | No | |
X-Amz-Signature |
String | No |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
fileMap |
Object | No |
An optional file map that contains the file name as the key and the file content md5 hash as the value. If this argument is provided, the service will generate a unique upload URL per file. Otherwise, the service will only generate a single upload URL for the zipped files. |
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.