With the seventhings asset tracking manager you digitize your internal process in no time and boost creativity and structure.
| username required | string non-empty Your login username for the web app. |
| password required | string non-empty Your secret password. |
| client_id required | string The client_id, request on request |
| grant_type | any Value: "password" |
{- "summary": "Get new oauth token with username and password",
- "value": {
- "username": "your username",
- "password": "S3cR3tP4ßW0rD",
- "client_id": "hash456789012345678901234567890123456789",
- "grant_type": "password"
}
}{- "access_token": "e68f38c2dca2add6c5528e16d7a2b453371e5870",
- "expires_in": 3600,
- "token_type": "Bearer",
- "scope": null,
- "refresh_token": "2b57a8d37baf1ef3a436968da51149b2eddf7f0f",
- "user_id": 1
}Get all objects.
| page | integer <int32> [ 1 .. 1000000 ] Default: 1 Page number of the results to fetch. |
| per_page | integer [ 1 .. 1000 ] Default: 50 The number of results per page. |
object (Filter) Example: filter[<filter_id>]=<filter_name> Fields are defined in Template, so this examples are based on the The filter parameter is a deep object, which means that it can have multiple levels of nesting.
In the first level there is the field name, in the second level there is the operator and
in the third level there are the values or the value.
for example: The exact field name you can find in the field definition list of your customer instance. The known operators which can be used for one value per field you can find here:
Here is the list of the known operators which can be used for multiple values per field:
Here are some examples:
| |
object (Sorting) Example: <sort_field>=<sort_type> Fields are defined in Template, so this examples are based on the In actual parameter, FieldKey should be passed (e.g: Up to columns Filter options available for certain
|
[- {
- "<field_key_1>": "<field_value_1>",
- "<field_key_2>": "<field_value_2>",
- "<field_key_3>": "<field_value_3>"
}
]Get count of all objects.
object (Filter) Example: filter[<filter_id>]=<filter_name> Fields are defined in Template, so this examples are based on the The filter parameter is a deep object, which means that it can have multiple levels of nesting.
In the first level there is the field name, in the second level there is the operator and
in the third level there are the values or the value.
for example: The exact field name you can find in the field definition list of your customer instance. The known operators which can be used for one value per field you can find here:
Here is the list of the known operators which can be used for multiple values per field:
Here are some examples:
|
{- "count": 0
}Create a new object.
| property name* additional property | any |
{- "<field_key_1>": "<field_value_1>",
- "<field_key_2>": "<field_value_2>",
- "<field_key_3>": "<field_value_3>"
}Update a single object.
| objectUuid required | string <uuid> (Uuid) |
| property name* additional property | any |
{- "<field_key_1>": "<field_value_1>",
- "<field_key_2>": "<field_value_2>",
- "<field_key_3>": "<field_value_3>"
}{- "<field_key_1>": "<field_value_1>",
- "<field_key_2>": "<field_value_2>",
- "<field_key_3>": "<field_value_3>"
}Get all rooms.
| page | integer <int32> [ 1 .. 1000000 ] Default: 1 Page number of the results to fetch. |
| per_page | integer [ 1 .. 1000 ] Default: 50 The number of results per page. |
[- {
- "<field_key_1>": "<field_value_1>",
- "<field_key_2>": "<field_value_2>",
- "<field_key_3>": "<field_value_3>"
}
]Get count of all rooms.
object (Filter) Example: filter[<filter_id>]=<filter_name> Fields are defined in Template, so this examples are based on the The filter parameter is a deep object, which means that it can have multiple levels of nesting.
In the first level there is the field name, in the second level there is the operator and
in the third level there are the values or the value.
for example: The exact field name you can find in the field definition list of your customer instance. The known operators which can be used for one value per field you can find here:
Here is the list of the known operators which can be used for multiple values per field:
Here are some examples:
|
{- "count": 0
}Create a new room.
| property name* additional property | any |
{- "<field_key_1>": "<field_value_1>",
- "<field_key_2>": "<field_value_2>",
- "<field_key_3>": "<field_value_3>"
}Update room.
| roomUuid required | string <uuid> (Uuid) |
| property name* additional property | any |
{- "<field_key_1>": "<field_value_1>",
- "<field_key_2>": "<field_value_2>",
- "<field_key_3>": "<field_value_3>"
}{- "<field_key_1>": "<field_value_1>",
- "<field_key_2>": "<field_value_2>",
- "<field_key_3>": "<field_value_3>"
}Get all locations.
| page | integer <int32> [ 1 .. 1000000 ] Default: 1 Page number of the results to fetch. |
| per_page | integer [ 1 .. 1000 ] Default: 50 The number of results per page. |
[- {
- "<field_key_1>": "<field_value_1>",
- "<field_key_2>": "<field_value_2>",
- "<field_key_3>": "<field_value_3>"
}
]Get count of all locations.
object (Filter) Example: filter[<filter_id>]=<filter_name> Fields are defined in Template, so this examples are based on the The filter parameter is a deep object, which means that it can have multiple levels of nesting.
In the first level there is the field name, in the second level there is the operator and
in the third level there are the values or the value.
for example: The exact field name you can find in the field definition list of your customer instance. The known operators which can be used for one value per field you can find here:
Here is the list of the known operators which can be used for multiple values per field:
Here are some examples:
|
{- "count": 0
}Create a new location.
| property name* additional property | any |
{- "<field_key_1>": "<field_value_1>",
- "<field_key_2>": "<field_value_2>",
- "<field_key_3>": "<field_value_3>"
}Update location.
| locationUuid required | string <uuid> (Uuid) |
| property name* additional property | any |
{- "<field_key_1>": "<field_value_1>",
- "<field_key_2>": "<field_value_2>",
- "<field_key_3>": "<field_value_3>"
}{- "<field_key_1>": "<field_value_1>",
- "<field_key_2>": "<field_value_2>",
- "<field_key_3>": "<field_value_3>"
}Get the information about the users.
| page | integer <int32> [ 1 .. 10000 ] Default: 1 Example: page=1 Page number |
| per_page | integer <int32> [ 1 .. 1000 ] Default: 50 Example: per_page=50 Number of items per page |
| sort_by | string Default: "id" Enum: "id" "email" Example: sort_by=id Sort by |
| order | string Default: "asc" Enum: "asc" "ASC" "desc" "DESC" Example: order=asc Sort order direction |
{- "items": [
- {
- "uuid": "f9f9f9f9-f9f9f9-f9f9f9-f9f9f9f9f9f9",
- "id": 9007199254740992,
- "email": "user@example.com",
- "firstname": "Max",
- "lastname": "Miller",
- "display_name": [
- "Max Miller (user@example.com)",
- "user@example.com"
]
}
], - "page": 1,
- "per_page": 50,
- "sort_by": "id",
- "order": "asc",
- "total": 0
}Get the information about the user by uuid.
| userUuid required | string <uuid> (Uuid) |
{- "uuid": "f9f9f9f9-f9f9f9-f9f9f9-f9f9f9f9f9f9",
- "id": 9007199254740992,
- "email": "user@example.com",
- "firstname": "Max",
- "lastname": "Miller",
- "display_name": [
- "Max Miller (user@example.com)",
- "user@example.com"
]
}Get the information about the user by integer id.
| userId required | integer (UserId) [ 0 .. 9007199254740992 ] |
{- "uuid": "f9f9f9f9-f9f9f9-f9f9f9-f9f9f9f9f9f9",
- "id": 9007199254740992,
- "email": "user@example.com",
- "firstname": "Max",
- "lastname": "Miller",
- "display_name": [
- "Max Miller (user@example.com)",
- "user@example.com"
]
}Get a list of Tasks.
| status | string (TaskStatus) Enum: "open" "closed" Example: status=closed Filter Tasks by status |
| deadline_from | string <date> Example: deadline_from=2023-04-01 Filter Tasks by deadline from date |
| deadline_to | string <date> Example: deadline_to=2023-05-01 Filter Tasks by deadline to date |
| assignee | string <uuid> Filter Tasks by assignee |
| author | string <uuid> Filter Tasks by author |
| reference_type | string (TaskReferenceType) Value: "asset" Example: reference_type=asset Filter Tasks by reference type |
[- {
- "uuid": "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11",
- "status": "closed",
- "author": "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11",
- "title": "Refill the printer.",
- "comment": "The printer is running low on ink.",
- "deadline": "2022-04-01",
- "reminders": [
- {
- "unit": "weeks",
- "value": 2
}
], - "recurring_schedule": {
- "unit": "weeks",
- "value": 2
}, - "assignees": [
- "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
], - "reference": {
- "type": "asset",
- "uuid": "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11",
- "name": "Assset name (asset barcode)",
- "id": 1
}, - "attachments": [
- {
- "uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
- "name": "string",
- "type": "string",
- "size": 1,
- "data_uri": "string",
- "thumbnail_uri": "string"
}
]
}
]Create a new Task.
Task to be created
| title required | string The title of the task. |
| comment | string or null A comment that is displayed in the task details. |
| deadline required | string <date> The date and time of the deadline. |
required | Array of objects (TaskTimeInterval) [ 1 .. 2 ] items |
required | object or null A time interval that is used to trigger a task. |
| assignees required | Array of strings <uuid> = 1 items |
required | object (TaskReference) The reference of the task. |
| attachments | Array of strings <uuid> >= 0 items |
| notify | boolean |
{- "title": "Refill the printer.",
- "comment": "The printer is running low on ink.",
- "deadline": "2022-04-01",
- "reminders": [
- {
- "unit": "weeks",
- "value": 2
}
], - "recurring_schedule": {
- "unit": "weeks",
- "value": 2
}, - "assignees": [
- "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
], - "reference": {
- "type": "asset",
- "uuid": "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
}, - "attachments": [
- "7d8296ad-da7c-45f7-b676-9220b3a9d4dc"
], - "notify": true
}Get a Task.
| taskUuid required | string <uuid> |
{- "uuid": "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11",
- "status": "closed",
- "author": "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11",
- "title": "Refill the printer.",
- "comment": "The printer is running low on ink.",
- "deadline": "2022-04-01",
- "reminders": [
- {
- "unit": "weeks",
- "value": 2
}
], - "recurring_schedule": {
- "unit": "weeks",
- "value": 2
}, - "assignees": [
- "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
], - "reference": {
- "type": "asset",
- "uuid": "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11",
- "name": "Assset name (asset barcode)",
- "id": 1
}, - "attachments": [
- {
- "uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
- "name": "string",
- "type": "string",
- "size": 1,
- "data_uri": "string",
- "thumbnail_uri": "string"
}
]
}Update a Task.
| taskUuid required | string <uuid> |
Task to be updated
| title required | string The title of the task. |
| comment | string or null A comment that is displayed in the task details. |
| deadline required | string <date> The date and time of the deadline. |
required | Array of objects (TaskTimeInterval) [ 1 .. 2 ] items |
required | object or null A time interval that is used to trigger a task. |
| assignees required | Array of strings <uuid> = 1 items |
required | object (TaskReference) The reference of the task. |
| attachments | Array of strings <uuid> >= 0 items |
| notify | boolean |
| property name* additional property | any |
{- "title": "Refill the printer.",
- "comment": "The printer is running low on ink.",
- "deadline": "2022-04-01",
- "reminders": [
- {
- "unit": "weeks",
- "value": 2
}
], - "recurring_schedule": {
- "unit": "weeks",
- "value": 2
}, - "assignees": [
- "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
], - "reference": {
- "type": "asset",
- "uuid": "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
}, - "attachments": [
- "7d8296ad-da7c-45f7-b676-9220b3a9d4dc"
], - "notify": true
}Update a Task status.
| taskUuid required | string <uuid> |
Task status
| status | string (TaskStatus) Enum: "open" "closed" The type of the referenced object. |
{- "status": "closed"
}Get all field definitions of a specific template.
| template required | any (AssetTrackingTemplate) Enum: "asset" "room" Example: room The template to get the field definitions for. |
[- {
- "uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
- "field_key": "string",
- "field_type": {
- "name": "ATTACHMENT",
- "constraints": [
- {
- "type": "allowed_values",
- "value": [
- "string"
]
}
]
}, - "label": "general_information",
- "comment": "Additional info about the field",
- "default_value": true,
- "possible_values": [
- true
], - "attributes": [
- {
- "type": "form_group",
- "value": "General"
}
], - "relations": [
- {
- "type": "actual_field",
- "field_uuid": "27cdddf3-a76f-4703-abf6-8f82d1549caf"
}
]
}
]Create a new field definition for a specific template.
| template required | any (AssetTrackingTemplate) Enum: "asset" "room" Example: room The template to get the field definitions for. |
required | FieldTypeAttachment (object) or FieldTypeBarcode (object) or FieldTypeBoolean (object) or FieldTypeDate (object) or FieldTypeDateTime (object) or FieldTypeDecimal (object) or FieldTypeDropdown (object) or FieldTypeFieldValueComparison (object) or FieldTypeLink (object) or FieldTypeLinkedAssets (object) or FieldTypeLinkedLocation (object) or FieldTypeLinkedRoom (object) or FieldTypeLinkedUser (object) or FieldTypeLongText (object) or FieldTypeMoney (object) or FieldTypeNumber (object) or FieldTypeReminder (object) or FieldTypeText (object) (FieldDefinitionFieldType) |
| label required | string (FieldDefinitionLabel) The label or translation key of the field |
| comment | string (FieldDefinitionComment) The comment of the field |
required | (boolean or null) or (number or null) or (string or null) (FieldDefinitionDefaultValue) The default value of the field |
required | Array of booleans or numbers or strings or null (FieldDefinitionPossibleValues) The possible values of the field |
required | Array of FieldAttributeFormGroup (object) or FieldAttributeEditable (object) or FieldAttributeInternal (object) or FieldAttributeMandatory (object) or FieldAttributeMutable (object) or FieldAttributeSystem (object) or FieldAttributeVisible (object) or FieldAttributePreselected (object) or FieldAttributeIndexed (object) or FieldAttributeFormatted (object) or FieldAttributeSorted (object) or FieldAttributeCurrencyCode (object) or FieldAttributeFractionDigits (object) or FieldAttributeNameComponent (object) or FieldAttributeExposed (object) (FieldDefinitionAttributes) The attributes of the field |
required | Array of FieldRelationActualField (object) or FieldRelationExpectedField (object) or FieldRelationActiveWhenValueEqualsOneOf (object) or null (FieldDefinitionRelations) The relations of the field |
{- "field_type": {
- "name": "ATTACHMENT",
- "constraints": [
- {
- "type": "allowed_values",
- "value": [
- "string"
]
}
]
}, - "label": "general_information",
- "comment": "Additional info about the field",
- "default_value": true,
- "possible_values": [
- true
], - "attributes": [
- {
- "type": "form_group",
- "value": "General"
}
], - "relations": [
- {
- "type": "actual_field",
- "field_uuid": "27cdddf3-a76f-4703-abf6-8f82d1549caf"
}
]
}Get a field definition for a specific template.
| template required | any (AssetTrackingTemplate) Enum: "asset" "room" Example: room The template to get the field definitions for. |
| fieldDefinitionUuid required | string <uuid> (Uuid) The UUID of the field definition to get. |
{- "uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
- "field_key": "string",
- "field_type": {
- "name": "ATTACHMENT",
- "constraints": [
- {
- "type": "allowed_values",
- "value": [
- "string"
]
}
]
}, - "label": "general_information",
- "comment": "Additional info about the field",
- "default_value": true,
- "possible_values": [
- true
], - "attributes": [
- {
- "type": "form_group",
- "value": "General"
}
], - "relations": [
- {
- "type": "actual_field",
- "field_uuid": "27cdddf3-a76f-4703-abf6-8f82d1549caf"
}
]
}Update a field definition for a specific template.
| template required | any (AssetTrackingTemplate) Enum: "asset" "room" Example: room The template to get the field definitions for. |
| fieldDefinitionUuid required | string <uuid> (Uuid) The UUID of the field definition to get. |
| uuid required | string <uuid> (Uuid) |
| field_key required | string (FieldDefinitionFieldKey) [ 1 .. 64 ] characters The key of the field |
required | FieldTypeAttachment (object) or FieldTypeBarcode (object) or FieldTypeBoolean (object) or FieldTypeDate (object) or FieldTypeDateTime (object) or FieldTypeDecimal (object) or FieldTypeDropdown (object) or FieldTypeFieldValueComparison (object) or FieldTypeLink (object) or FieldTypeLinkedAssets (object) or FieldTypeLinkedLocation (object) or FieldTypeLinkedRoom (object) or FieldTypeLinkedUser (object) or FieldTypeLongText (object) or FieldTypeMoney (object) or FieldTypeNumber (object) or FieldTypeReminder (object) or FieldTypeText (object) (FieldDefinitionFieldType) |
| label required | string (FieldDefinitionLabel) The label or translation key of the field |
| comment | string (FieldDefinitionComment) The comment of the field |
(boolean or null) or (number or null) or (string or null) (FieldDefinitionDefaultValue) The default value of the field | |
Array of booleans or numbers or strings or null (FieldDefinitionPossibleValues) The possible values of the field | |
required | Array of FieldAttributeFormGroup (object) or FieldAttributeEditable (object) or FieldAttributeInternal (object) or FieldAttributeMandatory (object) or FieldAttributeMutable (object) or FieldAttributeSystem (object) or FieldAttributeVisible (object) or FieldAttributePreselected (object) or FieldAttributeIndexed (object) or FieldAttributeFormatted (object) or FieldAttributeSorted (object) or FieldAttributeCurrencyCode (object) or FieldAttributeFractionDigits (object) or FieldAttributeNameComponent (object) or FieldAttributeExposed (object) (FieldDefinitionAttributes) The attributes of the field |
required | Array of FieldRelationActualField (object) or FieldRelationExpectedField (object) or FieldRelationActiveWhenValueEqualsOneOf (object) or null (FieldDefinitionRelations) The relations of the field |
{- "uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
- "field_key": "string",
- "field_type": {
- "name": "ATTACHMENT",
- "constraints": [
- {
- "type": "allowed_values",
- "value": [
- "string"
]
}
]
}, - "label": "general_information",
- "comment": "Additional info about the field",
- "default_value": true,
- "possible_values": [
- true
], - "attributes": [
- {
- "type": "form_group",
- "value": "General"
}
], - "relations": [
- {
- "type": "actual_field",
- "field_uuid": "27cdddf3-a76f-4703-abf6-8f82d1549caf"
}
]
}Get a list of file resources - available only for superuser.
[- {
- "uuid": "9091afea-81ee-4003-ac76-2ac11e3ddc3f",
- "name": "example.png",
- "type": "image/png",
- "size": 1234,
- "creator_id": 1,
- "created_at": "2022-09-11T13:35:00+00:00",
}
]Get a file resource
| fileUuid required | string <uuid> (Uuid) |
{- "uuid": "9091afea-81ee-4003-ac76-2ac11e3ddc3f",
- "name": "example.png",
- "type": "image/png",
- "size": 1234,
- "creator_id": 1,
- "created_at": "2022-09-11T13:35:00+00:00",
}Suggest the chub-category of given objects.
object (Filter) Fields are defined in Template, so this examples are based on the The filter parameter is a deep object, which means that it can have multiple levels of nesting.
In the first level there is the field name, in the second level there is the operator and
in the third level there are the values or the value.
for example: The exact field name you can find in the field definition list of your customer instance. The known operators which can be used for one value per field you can find here:
Here is the list of the known operators which can be used for multiple values per field:
Here are some examples:
| |
object (Sorting) Fields are defined in Template, so this examples are based on the In actual parameter, FieldKey should be passed (e.g: Up to columns Filter options available for certain
|
{- "filter": {
- "<filter_id>": "<filter_name>"
}, - "sort": {
- "<sort_field>": "<sort_type>"
}
}{- "<object_uuid>": "<mapped_category>"
}Suggested or set price of given objects.
| property name* additional property | any |
{- "<object_uuid>": "<mapped_category>"
}{- "<object_uuid>": "<rest_price_value>"
}Add object to circularity-hub.
additional property | object (PriceAndCategoryMapData) Given category and price |
{- "e8907bf9-90b3-4ea4-998c-242fab57d6a7": {
- "category": "<value>",
- "price": "<value>"
}
}Get all items from circularity-hub.
| page | integer <int32> [ 1 .. 1000000 ] Default: 1 Page number of the results to fetch. |
| per_page | integer [ 1 .. 1000 ] Default: 50 The number of results per page. |
object (Filter) Example: filter[<filter_id>]=<filter_name> Fields are defined in Template, so this examples are based on the The filter parameter is a deep object, which means that it can have multiple levels of nesting.
In the first level there is the field name, in the second level there is the operator and
in the third level there are the values or the value.
for example: The exact field name you can find in the field definition list of your customer instance. The known operators which can be used for one value per field you can find here:
Here is the list of the known operators which can be used for multiple values per field:
Here are some examples:
| |
object (Sorting) Example: <sort_field>=<sort_type> Fields are defined in Template, so this examples are based on the In actual parameter, FieldKey should be passed (e.g: Up to columns Filter options available for certain
|
[- {
- "id": 1,
- "deleted": 0,
- "asset_id": 2,
- "created_at": "2024-05-13 13:30:18",
- "price": 123,
- "category_id": 2,
- "suggested_price": 2244.82,
- "updated_at": "2024-05-13 13:30:18"
}
]Get one item from circularity-hub.
| identifier required | integer |
{- "id": 1,
- "deleted": 0,
- "asset_id": 2,
- "created_at": "2024-05-13 13:30:18",
- "price": 123,
- "category_id": 2,
- "suggested_price": 2244.82,
- "updated_at": "2024-05-13 13:30:18"
}Get all orders from circularity-hub.
| page | integer <int32> [ 1 .. 1000000 ] Default: 1 Page number of the results to fetch. |
| per_page | integer [ 1 .. 1000 ] Default: 50 The number of results per page. |
object (Filter) Example: filter[<filter_id>]=<filter_name> Fields are defined in Template, so this examples are based on the The filter parameter is a deep object, which means that it can have multiple levels of nesting.
In the first level there is the field name, in the second level there is the operator and
in the third level there are the values or the value.
for example: The exact field name you can find in the field definition list of your customer instance. The known operators which can be used for one value per field you can find here:
Here is the list of the known operators which can be used for multiple values per field:
Here are some examples:
| |
object (Sorting) Example: <sort_field>=<sort_type> Fields are defined in Template, so this examples are based on the In actual parameter, FieldKey should be passed (e.g: Up to columns Filter options available for certain
|
[- {
- "id": 1,
- "order_number": "7THX-24-4570-61",
- "created_at": "2024-05-29 13:02:20",
- "user_id": 1,
- "total_price": 152.56,
- "completed": false,
- "cancelled": true,
- "cancellation_reason": "have to cancel because of problems",
- "billing_data": {
- "firstName": "User",
- "lastName": "Seventhings",
- "street": "Hainstraße",
- "house_number": "2",
- "zip_code": "01097",
- "city": "Dresden"
}, - "articles": [
- {
- "id": 1,
- "deleted": 0,
- "asset_id": 1,
- "created_at": "2024-05-29 10:53:43",
- "price": 152.56,
- "category_id": 2,
- "suggested_price": 152.56,
- "updated_at": "2024-05-29 10:53:43",
- "mappedAssetData": {
- "item_image": [
- {
- "type": "image/jpeg",
- "name": "ITEXIA-Example-Chair.jpg",
- "size": 157814,
- "name_on_server": "assets_600f4403392732.09849361.jpg"
}
], - "item_title": "Stuhl Meeting",
- "item_description": "Alle Felder können individuell angepasst werden.",
- "item_main_category": "Möbel",
- "item_actual_location": 1,
- "internal_identifier": "DEV0000004",
- "item_original_purchase_date": "2020-11-02",
- "item_original_purchase_price": 279.9,
- "item_manufacturer": "Vitra",
- "documents": null,
- "item_actual_room": 3,
- "item_last_itexia_update_date": "2024-05-28 08:20:29"
}
}
]
}
]Get one order from circularity-hub.
| identifier required | integer |
{- "id": 1,
- "order_number": "7THX-24-4570-61",
- "created_at": "2024-05-29 13:02:20",
- "user_id": 1,
- "total_price": 152.56,
- "completed": false,
- "cancelled": true,
- "cancellation_reason": "have to cancel because of problems",
- "billing_data": {
- "firstName": "User",
- "lastName": "Seventhings",
- "street": "Hainstraße",
- "house_number": "2",
- "zip_code": "01097",
- "city": "Dresden"
}, - "articles": [
- {
- "id": 1,
- "deleted": 0,
- "asset_id": 1,
- "created_at": "2024-05-29 10:53:43",
- "price": 152.56,
- "category_id": 2,
- "suggested_price": 152.56,
- "updated_at": "2024-05-29 10:53:43",
- "mappedAssetData": {
- "item_image": [
- {
- "type": "image/jpeg",
- "name": "ITEXIA-Example-Chair.jpg",
- "size": 157814,
- "name_on_server": "assets_600f4403392732.09849361.jpg"
}
], - "item_title": "Stuhl Meeting",
- "item_description": "Alle Felder können individuell angepasst werden.",
- "item_main_category": "Möbel",
- "item_actual_location": 1,
- "internal_identifier": "DEV0000004",
- "item_original_purchase_date": "2020-11-02",
- "item_original_purchase_price": 279.9,
- "item_manufacturer": "Vitra",
- "documents": null,
- "item_actual_room": 3,
- "item_last_itexia_update_date": "2024-05-28 08:20:29"
}
}
]
}Update one order.
| identifier required | integer |
| property name* additional property | any |
{- "completed": true,
- "cancelled": true,
- "cancellation_reason": "Item could not be found any more"
}