Attachment uploads
- Print
- PDF
Attachment uploads
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Description
Uploads attachments
Request headers
| Header | Description |
|---|---|
| x-ncp-apigw-timestamp | - It indicates the time elapsed in milliseconds since January 1, 1970, 00:00:00 UTC - Request is considered invalid if the time difference with the API Gateway server is greater than 5 minutes |
| x-ncp-iam-access-key | - Access key ID issued from the NAVER Cloud Platform portal or a sub-account |
| x-ncp-apigw-signature-v2 | - Signature of the body in the above example encrypted with secret key mapped to access key ID - HMAC encryption algorithm is HMAC-SHA256 |
Attachment upload API
Uploads attachments individually (Maximum size: 100 MB)
Request URL
POST
https://workplace.apigw.ntruss.com/common/apigw/v1/file/company/{companyId}
Request path parameters
| Parameter | Type | Size | Requirement status | Description |
|---|---|---|---|---|
| companyId | String | 36 | Y | Integration key (CompanyId) of the customer to query Developers > Default settings > Integration key |
Request body parameters
| Parameter | Type | Size | Requirement status | Description |
|---|---|---|---|---|
| file | File | 100MB | Y | Attachment |
Request examples
POST https://workplace.apigw.ntruss.com/common/apigw/v1/file/company/e770da21-d7d9-405a-9bfc-9da400e13d38
POST /common/apigw/v1/file/company/e770da21-d7d9-405a-9bfc-9da400e13d38
HOST: workplace.apigw.ntruss.com
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZugW
x-ncp-apigw-timestamp: 1505290625682
x-ncp-apigw-api-key: DUxjP4HYTP8V7khBkgywdDHQjKuaYWGrppHKpvdv
x-ncp-iam-access-key: D78BB444D6D3C84CA38A
x-ncp-apigw-signature-v1: WTPItrmMIfLUk/UyUIyoQbA/z5hq9o3G8eQMolUzTEo=
Response examples
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 12 Sep 2020 01:18:11 GMT
Content-Type: application/json;charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Access-Control-Allow-Origin: *
x-ncp-trace-id: 68d1o68pm4cr63gc3169gm4p34
Responses
Returned as HTTP status codes in the response body
| HTTP status code | Response message | Description |
|---|---|---|
| 200 | OK | Normal successful request |
| 201 | Created | Successful resource creation |
| 400 | Bad Request | Request failure |
| 500 | Internal Server Error | - Common server error Error codes in the 400 range indicate client-side errors Error codes in the 500 range indicate server-side errors |
Response examples
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 12 Sep 2020 01:18:11 GMT
Content-Type: application/json;charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Access-Control-Allow-Origin: *
x-ncp-trace-id: 6apj66ssmad1l64dpj6gp32d9h
{
"fileId": "3d799913-3ed8-4771-8620-4cbf88e66aee",
"tenantId": "e770da21-d7d9-405a-9bfc-9da400e13d38",
"companyId": "e770da21-d7d9-405a-9bfc-9da400e13d38",
"fileStat": "TMP",
"fileNm": "Archive 2.zip",
"fileSz": 36569809,
"creYmdt": 1661156834137
}
Was this article helpful?