Skip to content
Aether Docs

Reserve an attachment and get a presigned upload URL

POST
/api/v1/organizations/{orgID}/tickets/{ticketID}/attachments
curl --request POST \
  --url https://api.aetherplatform.cloud/api/v1/organizations/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/tickets/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/attachments \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "filename": "example", "content_type": "example", "size_bytes": 1 }'

Reserves a pending attachment slot on the ticket and returns a short-lived presigned PUT URL. The client uploads the file bytes directly to object storage (MinIO/S3) at upload_url with a matching Content-Type; the API never proxies the bytes. The upload is then confirmed by referencing the returned attachment_id in attachment_ids on a subsequent message (see the message endpoint) — that flips the row to attached inside the message transaction. Server-side limits: content_type must be on the allowlist (images, pdf, text, json, yaml, gzip, tar) and size_bytes in (0, 26214400] (25 MiB). Returns 503 when attachment storage is not configured (MINIO_ENDPOINT unset).

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
orgID
required
string format: uuid

Organization UUID.

ticketID
required
string format: uuid

Support ticket UUID.

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
object
filename
required
string
content_type
required

Must be on the server allowlist (images, application/pdf, text/plain, application/json, yaml, gzip, tar). Other types are rejected (422).

string
size_bytes
required

File size in bytes; must be in (0, 26214400] (25 MiB).

integer format: int64
Examplegenerated
{
  "filename": "example",
  "content_type": "example",
  "size_bytes": 1
}

Responses

Section titled “Responses”

201

Section titled “201”

Attachment reserved; upload URL issued.

Media typeapplication/json
object
attachment_id
required

Reference this id in a message’s attachment_ids to confirm the upload.

string format: uuid
upload_url
required

Short-lived presigned PUT URL; upload bytes directly here with the matching Content-Type.

string format: uri
Examplegenerated
{
  "attachment_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
  "upload_url": "https://example.com"
}

400

Section titled “400”

Malformed request — e.g. an invalid path UUID or an unparseable JSON body.

Media typeapplication/json
object
error
required
object
code
required

A stable, machine-readable error code.

string
message
required
string
details
Array<object>
object
field
required
string
code
required
string
message
required
string
Examplegenerated
{
  "error": {
    "code": "example",
    "message": "example",
    "details": [
      {
        "field": "example",
        "code": "example",
        "message": "example"
      }
    ]
  }
}

401

Section titled “401”

Missing or invalid credentials.

Media typeapplication/json
object
error
required
object
code
required

A stable, machine-readable error code.

string
message
required
string
details
Array<object>
object
field
required
string
code
required
string
message
required
string
Examplegenerated
{
  "error": {
    "code": "example",
    "message": "example",
    "details": [
      {
        "field": "example",
        "code": "example",
        "message": "example"
      }
    ]
  }
}

404

Section titled “404”

The requested resource was not found.

Media typeapplication/json
object
error
required
object
code
required

A stable, machine-readable error code.

string
message
required
string
details
Array<object>
object
field
required
string
code
required
string
message
required
string
Examplegenerated
{
  "error": {
    "code": "example",
    "message": "example",
    "details": [
      {
        "field": "example",
        "code": "example",
        "message": "example"
      }
    ]
  }
}

422

Section titled “422”

Request validation failed.

Media typeapplication/json
object
error
required
object
code
required

A stable, machine-readable error code.

string
message
required
string
details
Array<object>
object
field
required
string
code
required
string
message
required
string
Examplegenerated
{
  "error": {
    "code": "example",
    "message": "example",
    "details": [
      {
        "field": "example",
        "code": "example",
        "message": "example"
      }
    ]
  }
}

503

Section titled “503”

Attachment storage is not configured.