Media Connect Center overview
- Print
- PDF
Media Connect Center overview
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in Classic and VPC
Media Connect Center is a service of NAVER Cloud Platform that combines various media services and Object Storage of NAVER Cloud Platform and helps to integrate and manage the total media services on one screen, including grouping for managing media files, encoding, CDN integration, channel creation, and deployment. Media Connect Center provides APIs to view and set up organizations, members, job grades, and job positions. It works through the GET/POST/PUT/DELETE method calls of the HTTP method.
Common settings
Media Connect Center API URL
https://ncloudmcc.apigw.ntruss.co/ncloudmcc/v1
Request headers
| Item | Required | Description |
|---|---|---|
| x-ncp-apigw-timestamp | Y | Time elapsed since January 1, 1970, 00:00:00 UTC in milliseconds. The request is considered invalid if the time difference from the API Gateway server is 5 minutes or longerx-ncp-apigw-timestamp:{Timestamp} |
| x-ncp-iam-access-key | Y | Value of access key ID issued from NAVER Cloud Platform portalx-ncp-iam-access-key:{Sub Account Access Key} |
| x-ncp-apigw-signature-v2 | Y | Signature encrypted with the access key ID value and secret keyx-ncp-apigw-signature-v2:{API Gateway Signature} |
| x-ncp-region_code | N | Region code (KR)x-ncp-region_code:KR |
| Content-Type | Y | Specifies the request body content type as application/jsonContent-Type: application/json |
Authentication header
API Gateway authentication is required to use the Media Connect Center API. For the API Gateway authentication-related guide, see NAVER Cloud Platform API.
Media Connect Center API request composition
Header
x-ncp-apigw-timestamp:{Timestamp}
x-ncp-iam-access-key:{Sub Account Access Key}
x-ncp-apigw-signature-v2:{API Gateway Signature}
Content-Type:application/json
Body
Json Object
URL
{API_URL}/{resource}
Media Connect Center API request examples
curl -i -s -X POST \
-H "Content-Type:application/json" \
-H "x-ncp-iam-access-key:HrR0s91elfiXEeTSZdwj" \
-H "x-ncp-apigw-timestamp:1700201285710" \
-H "x-ncp-apigw-signature-v2:GOWtfeX5Su8r8uvCyHfgb9RGCu0CwQP//eexqzhZTc4=" \
"https://ncloudmcc.apigw.ntruss.com/ncloudmcc/v1/companies/{CompanyID}/depts/dept019" \
-d "{\"name\": \"sales\", \"sortOrd\":0}"
Common errors
Media Connect Center API errors provide the details through error messages within the HTTP status codes and body responses.
HTTP status code
| HTTP status code | Response message | Description |
|---|---|---|
| 200 | OK | Succeeded; when there is response data |
| 201 | Create | Creation succeeded; when there is no response data |
| 204 | No Content | Succeeded; when there is no response data |
| 400 | Bad Request | When there is an incorrect request |
| 401 | Unauthorized | Authentication failed |
| 403 | Forbidden | Unauthorized |
| 404 | Not Found | When there is an incorrect URL or the target resource not found |
| 500 | Internal Server Error | Other errors not defined |
Error message format
{
"error": {
"errorCode": "300",
"message": "Not Found Exception"
}
}
Was this article helpful?