Upload API Reference

This section explains how to upload an image for editing by sending a direct request to our API.

Uploading an image for editing via API

Image upload endpoint allows you to upload an image directly from your computer or server for editing, instead of providing an image URL.

To upload an image, attach an image file as body part of multipart/form-data. The other body part of multipart/form-data should be the same as JSON for a regular image editing request, except there is no input image URL option there. See Image edit contract for more info.

Image Edit Upload

Specifies:

• how the image will be processed (operations)
• where it will be stored (output)

post

/v1-beta1/image/edit/upload

Authorizations

OAuth2PasswordBearerOAuth2PasswordBearer

Body

fileFilerequired

dataDatarequired

Responses

application/json

application/json

application/json

application/json

application/json

application/json

cURL

JavaScript

Python

HTTP

cURL

curl -L \
  --request POST \
  --url '/v1-beta1/image/edit/upload' \
  --header 'Content-Type: multipart/form-data' \
  --data '{"file":"text","data":"text"}'

200

401

402

403

422

429

200

{
  "data": {
    "input": {
      "ext": "text",
      "mps": 1,
      "mime": "text",
      "format": "text",
      "width": 1,
      "height": 1
    },
    "output": {
      "ext": "text",
      "mps": 1,
      "mime": "text",
      "format": "text",
      "width": 1,
      "height": 1,
      "tmp_url": "text",
      "object_key": "text",
      "object_bucket": "text",
      "object_uri": "text",
      "claid_storage_uri": "text"
    },
    "profiling": {}
  }
}

Successful Response

Request

HTTP

POST /v1-beta1/image/edit/upload HTTP/1.1
Host: api.claid.ai
Authorization: Bearer {YOUR_API_KEY}
Content-Type: multipart/form-data; boundary="boundary"

--boundary
Content-Disposition: form-data; name="file"; filename="the_image"

< ./the_image.jpg

--boundary
Content-Disposition: form-data; name="data"
Content-Type: application/json

{
  "operations": {
    "resizing": {
      "width": 1000
    },
    "background": {
      "remove": false
    }
  }
}

--boundary--

cURL

curl -X POST --location "https://api.claid.ai/v1-beta1/image/edit/upload" --http1.1 \
    -H "Host: api.claid.ai" \
    -H "Authorization: Bearer {YOUR_API_KEY}" \
    -H "Content-Type:multipart/form-data" \
    -F "file=@./the_image.jpg;filename=the_image.jpg" \
    -F "data={\"operations\":{\"resizing\":{\"width\":1000},\"background\":{\"remove\":false}}};type=application/json"

Request headers

Content-Type: multipart/form-data; boundary="boundary"
Authorization: Bearer {YOUR_API_KEY}

In order to send a request, you should set a Content-Type header to let our system know that you are providing a valid form data payload and an Authorization header with a generated API key to identify yourself as a Claid user.

The form data payload should have two blocks of data (body parts), with a delimiter (boundary) separating each block.

The block with an image file should have a Content-Disposition header equal to form-data with two required keys: a name key with a value equal to file and a filename key that will be assigned to an output result image (it is better not to include the extension in a filename, as it can be overwritten by Output options).

Content-Disposition: form-data; name="file"; filename="the_image"

The block with edit operations should have two headers: a Content-Disposition header equal to form-data with a name key with a value equal to data and a Content-Type header to let our system know that you are providing a valid JSON payload.

Content-Disposition: form-data; name="data"
Content-Type: application/json

Response body and headers

The response body and headers is equal to response body and headers of regular image edit request. See the Read a response and Response Headers to learn more.