Reversions
This method retrieves details about specific revisions, tracking changes made to objects over time. This is useful for auditing purposes and ensures traceability of modifications. Each revision includes an ID, creation date, an optional comment explaining the change, and the user who made the revision.
Token-based authentication with required prefix "Token"
Query parameter comment used to filter results based on specific conditions.
Query parameter date_created used to filter results based on specific conditions.
Filters records where date_created is greater than the given value.
Filters records where date_created is greater than or equal to the given value.
Filters records where date_created is less than the given value.
Filters records where date_created is less than or equal to the given value.
Query parameter id used to filter results based on specific conditions.
Filters records where id is greater than the given value.
Filters records where id is greater than or equal to the given value.
Filters records where id is less than the given value.
Filters records where id is less than or equal to the given value.
Limits the number of records returned in a single page. The maximum is 1000. A higher value is capped at 1000 and the request still succeeds.
Filters records where modified_date is greater than the given value.
Filters records where modified_date is greater than or equal to the given value.
Filters records where modified_date is less than the given value.
Filters records where modified_date is less than or equal to the given value.
Query parameter page used to filter results based on specific conditions.
Query parameter sort used to filter results based on specific conditions.
Query parameter user used to filter results based on specific conditions.
Successful response for status code 200.
Numerical value representing quantity or total amount.
123This field defines the URL of the next page.
http://api.example.org/accounts/?page=4This field defines the URL of the previous page.
http://api.example.org/accounts/?page=2GET /api/v1/remote/1/data-warehouse/reversions/revisions/ HTTP/1.1
Host: sandbox.akinon.com
Authorization: YOUR_API_KEY
Accept: */*
Successful response for status code 200.
{
"count": 123,
"next": "http://api.example.org/accounts/?page=4",
"previous": "http://api.example.org/accounts/?page=2",
"results": [
{
"comment": "text",
"date_created": "2026-01-01T00:00:00.000Z",
"id": 1,
"user": 1
}
]
}This method retrieves details about specific revisions, tracking changes made to objects over time. This is useful for auditing purposes and ensures traceability of modifications. Each revision includes an ID, creation date, an optional comment explaining the change, and the user who made the revision. This endpoint retrieves a specific record by its unique identifier.
Token-based authentication with required prefix "Token"
A unique integer value identifying this revision.
Successful response for status code 200.
A text comment on this revision.
Timestamp indicating when the record was created.
Unique identifier for the record.
The user who created this revision.
Object not found.
GET /api/v1/remote/1/data-warehouse/reversions/revisions/{id}/ HTTP/1.1
Host: sandbox.akinon.com
Authorization: YOUR_API_KEY
Accept: */*
{
"comment": "text",
"date_created": "2026-01-01T00:00:00.000Z",
"id": 1,
"user": 1
}This method provides details about a specific version of an object, capturing the state of the object at the time of revision. When a revision is made, the object version prior to the revision is saved, allowing the system to retain the state of the object before the changes were applied. This includes versioning information such as the ID, associated object ID, the database where the object is stored, the format (e.g., 'json'), and the serialized data representing the object. Additionally, it includes details about the revision that the object version is associated with, its content type, and its representation. This is typically used for tracking changes to objects, enabling version control, and allowing the retrieval of specific historical states of the object for auditing, rollback, or comparison purposes.
Token-based authentication with required prefix "Token"
Query parameter content_type used to filter results based on specific conditions.
Query parameter db used to filter results based on specific conditions.
Query parameter format used to filter results based on specific conditions.
Query parameter id used to filter results based on specific conditions.
Filters records where id is greater than the given value.
Filters records where id is greater than or equal to the given value.
Filters records where id is less than the given value.
Filters records where id is less than or equal to the given value.
Limits the number of records returned in a single page. The maximum is 1000. A higher value is capped at 1000 and the request still succeeds.
Query parameter object_id used to filter results based on specific conditions.
Query parameter object_repr used to filter results based on specific conditions.
Query parameter page used to filter results based on specific conditions.
Query parameter revision used to filter results based on specific conditions.
Query parameter serialized_data used to filter results based on specific conditions.
Query parameter sort used to filter results based on specific conditions.
Successful response for status code 200.
Numerical value representing quantity or total amount.
123This field defines the URL of the next page.
http://api.example.org/accounts/?page=4This field defines the URL of the previous page.
http://api.example.org/accounts/?page=2GET /api/v1/remote/1/data-warehouse/reversions/versions/ HTTP/1.1
Host: sandbox.akinon.com
Authorization: YOUR_API_KEY
Accept: */*
Successful response for status code 200.
{
"count": 123,
"next": "http://api.example.org/accounts/?page=4",
"previous": "http://api.example.org/accounts/?page=2",
"results": [
{
"content_type": 1,
"db": "text",
"format": "text",
"id": 1,
"object_id": "text",
"object_repr": "text",
"revision": 1,
"serialized_data": "text"
}
]
}This method provides details about a specific version of an object, capturing the state of the object at the time of revision. When a revision is made, the object version prior to the revision is saved, allowing the system to retain the state of the object before the changes were applied. This includes versioning information such as the ID, associated object ID, the database where the object is stored, the format (e.g., 'json'), and the serialized data representing the object. Additionally, it includes details about the revision that the object version is associated with, its content type, and its representation. This is typically used for tracking changes to objects, enabling version control, and allowing the retrieval of specific historical states of the object for auditing, rollback, or comparison purposes. This endpoint retrieves a specific record by its unique identifier.
Token-based authentication with required prefix "Token"
A unique integer value identifying this sürüm.
Successful response for status code 200.
The classification or type related to this field.
The database the model under version control is stored in.
The serialization format used by this model.
Unique identifier for the record.
Primary key of the model under version control.
A string representation of the object.
The revision that contains this version.
The serialized form of this version of the model.
Object not found.
GET /api/v1/remote/1/data-warehouse/reversions/versions/{id}/ HTTP/1.1
Host: sandbox.akinon.com
Authorization: YOUR_API_KEY
Accept: */*
{
"content_type": 1,
"db": "text",
"format": "text",
"id": 1,
"object_id": "text",
"object_repr": "text",
"revision": 1,
"serialized_data": "text"
}Last updated
Was this helpful?

