SourceDeploy Overview
- Print
- PDF
SourceDeploy Overview
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Overview
SourceDeploy API is provided in RESTful format. To make SourceDeploy Rest API calls, API Gateway and Sub Account must be authenticated.
For more information on API calls via API Gateway, see API Gateway Manual. An API request message consists of the following:
Common settings
API URL
Available in Classic
| Region | API URL |
|---|---|
| Korea (KR) | https://sourcedeploy.apigw.ntruss.com/api/v1 |
Available in VPC
| Region | API URL |
|---|---|
| Korea (KR) | https://vpcsourcedeploy.apigw.ntruss.com/api/v1 |
| Singapore (SGN) | https://vpcsourcedeploy.apigw.ntruss.com/api/sg-v1 |
| Japan (JPN) | https://vpcsourcedeploy.apigw.ntruss.com/api/jp-v1 |
Request headers
| Header name | Description |
|---|---|
| x-ncp-apigw-timestamp | This is the number of milliseconds that have elapsed since January 1, 1970 00:00:00 UTC. If the time difference compared to the APIGW server is more than 5 minutes, the request is considered invalid |
| x-ncp-iam-access-key | API Key issued from NAVER Cloud Platform or AccessKey issued from Sub Account |
| x-ncp-apigw-signature-v2 | A signature that encrypts the Body with SecretKey mapped to the AccessKey HmacSHA256 is used as the HMAC encryption algorithm |
Was this article helpful?