Asset Management

Create new asset

Creates a new asset.

post/assets

Request body

user_idstring uuid

titlestring required

creatorstring

subjectstring

descriptionstring

Example request

{
  "user_id": "7bea4732-214f-40e7-9161-4e7241a2b97e",
  "title": "Lorem Ipsum",
  "creator": "pAI-OS",
  "subject": "Lorem Ipsum",
  "description": "Lorem Ipsum"
}

Response

Created

idstring uuid required

user_idstring uuid

titlestring required

creatorstring

subjectstring

descriptionstring

Example response

{
  "id": "7bea4732-214f-40e7-9161-4e7241a2b97e",
  "user_id": "7bea4732-214f-40e7-9161-4e7241a2b97e",
  "title": "Lorem Ipsum",
  "creator": "pAI-OS",
  "subject": "Lorem Ipsum",
  "description": "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua."
}

Changes

Changed in 7 of the 50 revisions of this API.1228

Oct 2, 2024c9062e3a3c541See the full diff
- ○
  the endpoint scheme security jwt was added to the API
  api-security-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Oct 2, 2024936529d30a411See the full diff
- ○
  the endpoint scheme security jwt was removed from the API
  api-security-removed
This revision also has 5 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Sep 18, 2024041ec1a0e4032See the full diff
- ○
  the endpoint scheme security jwt was added to the API
  api-security-added
- ○
  the endpoint scheme security cookieAuth was removed from the API
  api-security-removed
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 8, 2024d53276437f781See the full diff
- ○
  the endpoint scheme security cookieAuth was added to the API
  api-security-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jun 7, 20245ea1c0d602b956See the full diff
- ▲
  added the pattern ^[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$ to the request property user_id
  request-property-pattern-added
- ▲
  added the pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ to the request property creator
  request-property-pattern-added
- ▲
  added the pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ to the request property description
  request-property-pattern-added
- ▲
  added the pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ to the request property subject
  request-property-pattern-added
- ▲
  added the pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ to the request property title
  request-property-pattern-added
- ○
  the creator response's property pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ was added for the status 201
  response-property-pattern-added
- ○
  the description response's property pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ was added for the status 201
  response-property-pattern-added
- ○
  the id response's property pattern ^[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$ was added for the status 201
  response-property-pattern-added
- ○
  the subject response's property pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ was added for the status 201
  response-property-pattern-added
- ○
  the title response's property pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ was added for the status 201
  response-property-pattern-added
- ○
  the user_id response's property pattern ^[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$ was added for the status 201
  response-property-pattern-added
Jun 7, 20243e9b4afe1aeb13See the full diff
- ▲
  the user_id request property type/format changed from string/ to string/uuid
  request-property-type-changed
- ○
  the response optional property id became read-only for the status 201
  response-optional-property-became-read-only
- ○
  the response property id became required for the status 201
  response-property-became-required
- ○
  the response property title became required for the status 201
  response-property-became-required
Jun 4, 2024578e8efc5755614See the full diff
- ▲
  the response property creator became nullable for the status 201
  response-property-became-nullable
- ▲
  the response property description became nullable for the status 201
  response-property-became-nullable
- ▲
  the response property subject became nullable for the status 201
  response-property-became-nullable
- ▲
  the response property user_id became nullable for the status 201
  response-property-became-nullable
- ▲
  the response property id became optional for the status 201
  response-property-became-optional
- ▲
  the response property title became optional for the status 201
  response-property-became-optional
- ○
  the endpoint scheme security jwt was removed from the API
  api-security-removed
- ○
  removed the pattern ^[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$ from the request property user_id
  request-property-pattern-removed
- ○
  removed the pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ from the request property creator
  request-property-pattern-removed
- ○
  removed the pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ from the request property description
  request-property-pattern-removed
- ○
  removed the pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ from the request property subject
  request-property-pattern-removed
- ○
  removed the pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ from the request property title
  request-property-pattern-removed
- ○
  the user_id request property type/format was generalized from string/uuid to string/
  request-property-type-generalized
- ○
  the creator response's property pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ was removed for the status 201
  response-property-pattern-removed
- ○
  the description response's property pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ was removed for the status 201
  response-property-pattern-removed
- ○
  the id response's property pattern ^[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$ was removed for the status 201
  response-property-pattern-removed
- ○
  the subject response's property pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ was removed for the status 201
  response-property-pattern-removed
- ○
  the title response's property pattern ^[A-Za-z0-9\s\-_,.;:()!@#$%&*+=?\/\\|~^'"\[\]{}áéíóúñ©€£¥]+$ was removed for the status 201
  response-property-pattern-removed
- ○
  the user_id response's property pattern ^[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$ was removed for the status 201
  response-property-pattern-removed
- ○
  the response required property id became not read-only for the status 201
  response-required-property-became-not-read-only
This revision also has 32 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history