How do I call the images endpoints over HTTP?
Table of Contents
- 1. Endpoints
- 1.1.
GET /api/v1/assets/images - 1.2.
GET /api/v1/assets/images/__none__ - 1.3.
POST /api/v1/assets/images/get-many - 1.4.
POST /api/v1/assets/images - 1.5.
PUT /api/v1/assets/images - 1.6.
POST /api/v1/assets/images/put-many - 1.7.
DELETE /api/v1/assets/images/__none__ - 1.8.
POST /api/v1/assets/images/delete-many - 1.9.
GET /api/v1/assets/images/__none__/versions - 1.10.
GET /api/v1/assets/images/__none__/versions/0
- 1.1.
This file documents the images resource over HTTP, one section per endpoint. Every section exports its own Hurl file into projects/ores.http/scripts/library/. Running a file sends that one request, so a failure names the endpoint it came from.
1. Endpoints
1.1. GET /api/v1/assets/images
List images. It needs a session.
It forwards to assets.v1.images.list.
The request is:
GET /api/v1/assets/images
GET {{base_url}}/api/v1/assets/images
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.2. GET /api/v1/assets/images/__none__
Get one image. It needs a session.
It forwards to assets.v1.images.get.
The request is:
GET /api/v1/assets/images/__none__
GET {{base_url}}/api/v1/assets/images/__none__
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.3. POST /api/v1/assets/images/get-many
Get many images. It needs a session.
It forwards to assets.v1.images.get_many.
The request is:
POST /api/v1/assets/images/get-many
POST {{base_url}}/api/v1/assets/images/get-many
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.4. POST /api/v1/assets/images
Create one image. It needs a session.
It forwards to assets.v1.images.put.
The request is:
POST /api/v1/assets/images
POST {{base_url}}/api/v1/assets/images
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.5. PUT /api/v1/assets/images
Replace one image. It needs a session.
It forwards to assets.v1.images.put.
The request is:
PUT /api/v1/assets/images
PUT {{base_url}}/api/v1/assets/images
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.6. POST /api/v1/assets/images/put-many
Write many images. It needs a session.
It forwards to assets.v1.images.put_many.
The request is:
POST /api/v1/assets/images/put-many
POST {{base_url}}/api/v1/assets/images/put-many
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.7. DELETE /api/v1/assets/images/__none__
Delete one image. It needs a session.
It forwards to assets.v1.images.delete.
The request is:
DELETE /api/v1/assets/images/__none__
DELETE {{base_url}}/api/v1/assets/images/__none__
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.8. POST /api/v1/assets/images/delete-many
Delete many images. It needs a session.
It forwards to assets.v1.images.delete_many.
The request is:
POST /api/v1/assets/images/delete-many
POST {{base_url}}/api/v1/assets/images/delete-many
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.9. GET /api/v1/assets/images/__none__/versions
List the recorded versions of one image. It needs a session.
It forwards to assets.v1.images_versions.list.
The request is:
GET /api/v1/assets/images/__none__/versions
GET {{base_url}}/api/v1/assets/images/__none__/versions
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.10. GET /api/v1/assets/images/__none__/versions/0
Get one recorded version of one image. It needs a session.
It forwards to assets.v1.images_versions.get.
The request is:
GET /api/v1/assets/images/__none__/versions/0
GET {{base_url}}/api/v1/assets/images/__none__/versions/0
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200