Chat Concept Upload Attachment

User Guide > Resources > Chat Concept Upload Attachment

This request add an attachment to a chat concept.
The attachment contents is read from the payload. The name and content-type are set in HTTP headers.

Resource

POST /chats/<OID>/concept/attachment

Whrere OID is the object ID of the chat session.

Parameters

None

headers

Name Description Example

Name	Description	Example
`Content-Type`	The mime content type.	`Content-Type: text/plain`
`Content-Disposition`	The file name, as defined in RFC 2183.	`Content-Disposition: attachment; filename=image.jpg;`
`Content-Length`	The attachment size in bytes.	`Content-Length: 1024`

Content-Type

The mime content type.

Content-Type: text/plain

Content-Disposition

The file name, as defined in RFC 2183.

Content-Disposition: attachment; filename=image.jpg;

Content-Length

The attachment size in bytes.

Content-Length: 1024

Payload

The contents of the attachment.

Response

The created attachment.

Object Response < Attachment >

Context

Authorization

User

Errors

Common Errors

Example

Request

POST https://xelion.nl/api/v1/master/chats/2836127/concept/attachment

Headers

Content-Type: image/jpeg
Content-Disposition: attachment; filename=image.jpg

Payload

.......................................................................................

Response

{
    "object": {
        "originalLocation": "image.jpg",
        "mimeType": "image/jpeg",
        "size": 1060,
        "commonName": "image.jpg",
        "oid": "1808788",
        "objectType": "Attachment"
    }
}