This is a short introduction on how to implement your software as a provider:
\nThe Concept:
Alution's Provider API is fundamentally a REST API with a unique approach. While you can use the standard Alution API as a typical REST API, Alution also offers an alternative, more straightforward method that doesn't require changes to your code whenever we update our fields.
How It Works:
Instead of sending data in the predefined structure, you provide us with a representation of your database schema, including validation details, in a JSON Schema format. This allows us to understand your column names, data types, and validation rules.
Steps to Implement:
\nSend us your database schema in JSON Schema format, including column details and validation rules.
\nMap your schema fields in Alution under Settings > Provider Field Mapping.
\nOnce mapped, you can directly POST your table entries formatted in your own schema directly to Alution.cloud without extra code modifications or data formatting.
\nThis approach simplifies integration, making it easier to keep your existing data formats and workflows intact while seamlessly syncing with Alution.
\nAdditionally: Append ?relations=customFieldSchemas to each show or index request to retrieve your group with the mapped values within your column fields.
Before importing or managing provider data, you need access to the system via a bearer token. You can create this token through the user's credentials. You can use the Administrator user (the user with ID 1), as this account is not limited by permissions or groups and always has full system access. This makes it ideal for provider scenarios. While you can use any user, remember that a user without proper permissions may be limited in what they can do.
\n","event":[{"listen":"prerequest","script":{"id":"2a9f1f1b-aec7-4a46-91cd-90e887d19886","type":"text/javascript","packages":{},"exec":[""]}},{"listen":"test","script":{"id":"f9af6dc4-8d8f-4709-88c5-fc7a6365c83b","type":"text/javascript","packages":{},"exec":[""]}}],"_postman_id":"4d95fa80-7a3f-4ef3-b1ed-194c9a718ed8","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}}},{"name":"Custom Field Schemas","item":[{"name":"Custom Field Schemas Create","id":"dafb10e1-48e9-4c87-a999-d77c0cd5f79c","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"type\":\"contacts\", \n \"group\":\"MyCustomUniqueGroupName\",\n \"schema\": {\n \"$schema\":\"http://json-schema.org/schema#\",\n \"type\":\"object\",\n \"properties\": {\n \"MyDatabaseContactNameColumn\": {\n \"minLength\":0,\n \"maxLength\":50,\n \"type\":\"string\",\n \"description\": \"Name of Contact\"\n },\n \"MyDatabaseContactLegalFormColumn\": {\n \"minLength\":0,\n \"maxLength\":10,\n \"type\":\"string\",\n \"description\": \"Legal Form of Contact\"\n }\n }\n }\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/custom-field-schemas","urlObject":{"path":["custom-field-schemas"],"host":["https://dev.alution.test/api/v1"],"query":[],"variable":[]}},"response":[{"id":"d36b6732-ebd4-4ae3-a7f6-3251ab46b94e","name":"Custom Field Schemas Create","originalRequest":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"type\":\"contacts\", \n \"group\":\"MyCustomUniqueGroupName\",\n \"schema\": {\n \"$schema\":\"http://json-schema.org/schema#\",\n \"type\":\"object\",\n \"properties\": {\n \"MyDatabaseContactNameColumn\": {\n \"minLength\":0,\n \"maxLength\":50,\n \"type\":\"string\",\n \"description\": \"Name of Contact\"\n },\n \"MyDatabaseContactLegalFormColumn\": {\n \"minLength\":0,\n \"maxLength\":10,\n \"type\":\"string\",\n \"description\": \"Legal Form of Contact\"\n }\n }\n }\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/custom-field-schemas"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Server","value":"nginx/1.27.4"},{"key":"Content-Type","value":"application/json"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Connection","value":"keep-alive"},{"key":"Vary","value":"Accept-Encoding"},{"key":"X-Powered-By","value":"PHP/8.4.4"},{"key":"Cache-Control","value":"no-cache, private"},{"key":"Date","value":"Thu, 24 Jul 2025 08:46:19 GMT"},{"key":"Access-Control-Allow-Origin","value":"*"},{"key":"Content-Encoding","value":"gzip"}],"cookie":[],"responseTime":null,"body":"{\n \"data\": [\n {\n \"id\": 3,\n \"group\": \"MyCustomUniqueGroupName\",\n \"name\": \"MyDatabaseContactNameColumn\",\n \"type\": \"string\",\n \"description\": \"Name of Contact\",\n \"rules\": [\n \"min:0\",\n \"max:50\"\n ]\n },\n {\n \"id\": 4,\n \"group\": \"MyCustomUniqueGroupName\",\n \"name\": \"MyDatabaseContactLegalFormColumn\",\n \"type\": \"string\",\n \"description\": \"Legal Form of Contact\",\n \"rules\": [\n \"min:0\",\n \"max:10\"\n ]\n }\n ]\n}"}],"_postman_id":"dafb10e1-48e9-4c87-a999-d77c0cd5f79c"},{"name":"Custom Field Schemas Show","id":"7c217b61-33f0-4a4f-b278-9ee0c541f693","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"body":{"mode":"raw","raw":"","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/custom-field-schemas/{{custom_field_sch1ema}}","urlObject":{"path":["custom-field-schemas","{{custom_field_sch1ema}}"],"host":["https://dev.alution.test/api/v1"],"query":[],"variable":[]}},"response":[],"_postman_id":"7c217b61-33f0-4a4f-b278-9ee0c541f693"}],"id":"58121c85-21f9-4282-8bdd-81d9d7027930","description":"When creating a custom schema, you need to specify the following key components:
\ntype: Defines the category of data. Options include:
\"contacts\" (default for contact information)
\"addresses\"
\"users\"
\"projects\"
\"products\"
group: A unique identifier for your schema group. It must:
Be the same across all of your schemas
\nClearly indicate which software or system the group belongs to
\nschema: A JSON Schema object describing the structure of your data, closely resembling your database tables to facilitate development and data handling.
typeSpecify the data category relevant to your schema. Example options:
\n\"type\": \"contacts\"\n\nCopy
\nChoose the appropriate type from the list above.
\ngroupProvide a unique and descriptive name for your schema group. This helps identify the schema’s purpose and its association to your software.
Example:
\"group\": \"MyCustomUniqueGroupName\"\n\nMake sure this name is unique and indicates which software or system the schema belongs to.
\nschemaDefine your data structure using JSON Schema standards. Keep it as close as possible to your database structure to simplify development and data synchronization.
\nSchema example:
\n\"schema\": {\n \"$schema\": \"http://json-schema.org/schema#\",\n \"type\": \"object\",\n \"properties\": {\n // Define each column, ensuring the name resembles your database's column names.\n // Add descriptions for clarity, and validations to ensure data integrity.\n \"ContactName\": {\n \"minLength\": ,\n \"maxLength\": 50,\n \"type\": \"string\",\n \"description\": \"Kontaktname\"\n }\n }\n}\n\nNotes:
\nThe property names should match your database columns.
\nProvide descriptive text for each property.
\nInclude validation rules such as minLength, maxLength, type, etc., to prevent validation errors during data import or update.
Ensure the schema accurately reflects your data structure for seamless integration.
\nThe response from the update endpoint includes three key fields to guide your synchronization process:
\nforce_update (boolean):
If set to true, this indicates that the user has changed the group's mapping configuration and requested a resync Essentially, it’s a prompt to resynchronize your data with the latest mappings.
fields (array):
Contains a list of the fields that are currently mapped and accepted by the endpoint. This helps you understand which data fields you should include on the update.
overridable (array):
Lists the fields that are available to be mapped. If you don’t provide your own default mappings, you can ignore this and allow users to decide which fields to map via the interface. Alternatively, you can use these to automatically map fields yourself and simplify the process.
Usage tip:
\nIf force_update is true, proceed to refresh (update) all relevant entries from your database into Alution to ensure sync consistency.
Use the fields list to know which data points are relevant and should be updated.
Leverage overridable to determine which fields you can pre-map or offer for mapping, streamlining the setup or automation process.
This step is optional but highly recommended, especially the first time you synchronize data with Alution. Providing a default mapping reduces the need for users to manually map each field, streamlining the setup process.
\nTo do this, send a mappings object in your PATCH request to the endpoint, where:
Keys are the overridable fields provided by Alution (as specified in the overridable array from the response).
Values are your database column names, as defined in your schema or your system's CustomFieldSchema.
You can retrieve all available fields via a GET request to the same endpoint, which will return the list of overridable fields.
\nAfter PATCHING:
You will receive a response containing an array where:
Keys are your database column names.
\nValues are booleans (true or false) indicating whether the mapping for that field was successfully updated.
This way, you can verify which mappings were successfully applied and handle any fields that failed to update accordingly.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}},"urlObject":{"path":["custom-field-schemas","mappings"],"host":["https://dev.alution.test/api/v1"],"query":[{"key":"group","value":"MyCustomUniqueGroupName"},{"key":"type","value":"contacts"}],"variable":[]}},"response":[{"id":"ce0c21bd-4570-494d-a9fe-eb2f21aee47b","name":"Mappings Update","originalRequest":{"method":"PATCH","header":[],"body":{"mode":"raw","raw":"{\n \"mappings\": {\n \"name\": \"MyDatabaseContactNameColumn\",\n \"legal_form\": \"MyDatabaseContactLegalFormColumn\"\n }\n}","options":{"raw":{"language":"json"}}},"url":{"raw":"https://dev.alution.test/api/v1/custom-field-schemas/mappings?group=MyCustomUniqueGroupName&type=contacts","host":["https://dev.alution.test/api/v1"],"path":["custom-field-schemas","mappings"],"query":[{"key":"group","value":"MyCustomUniqueGroupName"},{"key":"type","value":"contacts"}]}},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Server","value":"nginx/1.27.4"},{"key":"Content-Type","value":"application/json"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Connection","value":"keep-alive"},{"key":"Vary","value":"Accept-Encoding"},{"key":"X-Powered-By","value":"PHP/8.4.4"},{"key":"Cache-Control","value":"no-cache, private"},{"key":"Date","value":"Thu, 24 Jul 2025 08:47:03 GMT"},{"key":"Access-Control-Allow-Origin","value":"*"},{"key":"Content-Encoding","value":"gzip"}],"cookie":[],"responseTime":null,"body":"{\n \"updated\": {\n \"MyDatabaseContactNameColumn\": true,\n \"MyDatabaseContactLegalFormColumn\": true\n }\n}"}],"_postman_id":"3d0879cb-c90e-4607-b481-32868aa622a3"}],"id":"72c3bebf-30dd-4984-9b0a-9704866f8eb7","description":"Mappings are used to indicate which of your database columns are associated with a specific custom field schema and are currently mapped.
\n","_postman_id":"72c3bebf-30dd-4984-9b0a-9704866f8eb7","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}}},{"name":"Contacts","item":[{"name":"Contacts Create","id":"6aa9a890-8462-434f-a01b-37ba04e6e1a0","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"identifier\": \"MY-UNIQUE-ID\",\n \"MyCustomUniqueGroupName\": {\n \"MyDatabaseContactNameColumn\": \"My Column Value\"\n }\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/contacts","description":"identifierPurpose: A unique key that identifies each record.
\nRequirements:
\nShould match your database table's primary key.
\nMust be unique across all systems to avoid conflicts.
\nIf your ID is just a number, prefix it with a short code representing your software (e.g., \"serp-1\" for \"Super-ERP\" with ID 1).
Example:\"serp-1\" instead of \"1\".
Important:
Never use just a number like \"1\" alone, as it could conflict with IDs from Alution.
Enclose your data fields inside the unique group you specified when importing your custom schema.
\nPurpose:
\nEnsures the data abides by your schema's validation rules.
\nData will only be processed if the fields are correctly mapped.
\nNote:
\nUnmapped fields, even if present in your group, will be ignored.
\nIf your table has few fields and the total request size stays under 10MB, you can send all fields at once without special handling.
\nThis data structure is used for both creating new records and updating existing ones for each model in your provider group.
\n","urlObject":{"path":["contacts"],"host":["https://dev.alution.test/api/v1"],"query":[],"variable":[]}},"response":[],"_postman_id":"6aa9a890-8462-434f-a01b-37ba04e6e1a0"},{"name":"Contacts Update","id":"51442db7-fa64-47fc-aa09-fe9f55887801","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"PATCH","header":[],"body":{"mode":"raw","raw":"{\n \"identifier\": \"MY-UNIQUE-ID\",\n \"MyCustomUniqueGroupName\": {\n \"MyDatabaseContactLegalFormColumn\": \"GmbH\"\n }\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/contacts/{{identifier}}","description":"identifierPurpose: A unique key that identifies each record.
\nRequirements:
\nShould match your database table's primary key.
\nMust be unique across all systems to avoid conflicts.
\nIf your ID is just a number, prefix it with a short code representing your software (e.g., \"serp-1\" for \"Super-ERP\" with ID 1).
Example:\"serp-1\" instead of \"1\".
Important:
Never use just a number like \"1\" alone, as it could conflict with IDs from Alution.
Enclose your data fields inside the unique group you specified when importing your custom schema.
\nPurpose:
\nEnsures the data abides by your schema's validation rules.
\nData will only be processed if the fields are correctly mapped.
\nNote:
\nUnmapped fields, even if present in your group, will be ignored.
\nIf your table has few fields and the total request size stays under 10MB, you can send all fields at once without special handling.
\nThis data structure is used for both creating new records and updating existing ones for each model in your provider group.
\n","urlObject":{"path":["contacts","{{identifier}}"],"host":["https://dev.alution.test/api/v1"],"query":[],"variable":[]}},"response":[],"_postman_id":"51442db7-fa64-47fc-aa09-fe9f55887801"},{"name":"Contacts Index","id":"b057963c-5e52-4efb-aa71-d000ce86aa91","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/contacts?relations=customFieldSchemas&perPage=10&page=1","urlObject":{"path":["contacts"],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Appending customFieldSchemas as a value to the relationsparameter, will ensure that your data is
\n","type":"text/plain"},"key":"relations","value":"customFieldSchemas"},{"description":{"content":"Set the number of entries loaded per page. Keep in mind that loading too many entries or large items may cause a 403 error due to response size limitations in Nginx. It's better to keep the page size smaller and perform more frequent iterations, which is usually the more reliable approach.
\n","type":"text/plain"},"key":"perPage","value":"10"},{"description":{"content":"The page you want to request.
\n","type":"text/plain"},"key":"page","value":"1"}],"variable":[]}},"response":[],"_postman_id":"b057963c-5e52-4efb-aa71-d000ce86aa91"},{"name":"Contacts Show","id":"2fb72617-8fe2-4011-8008-6f4ef0c62f70","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/contacts/{{contact_identifier}}?relations=customFieldSchemas","urlObject":{"path":["contacts","{{contact_identifier}}"],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Appending customFieldSchemas as a value to the relationsparameter, will ensure that your data is
\n","type":"text/plain"},"key":"relations","value":"customFieldSchemas"}],"variable":[]}},"response":[],"_postman_id":"2fb72617-8fe2-4011-8008-6f4ef0c62f70"}],"id":"a10da4c2-40c3-4317-9bb5-048410243bc3","description":"Contacts can be viewed as a folder, which has a name and contains multiple addresses. For example, a company named \"Jane Doe LLC\" might be represented as a contact named \"Jane Doe LLC\" or simply \"Jane Doe.\" Inside this contact, you store the addresses associated with the company, which might or might not be named after their locations.
\nFor instance, the company \"Jane Doe\" has a primary address in Germany and another in the USA, both belonging to the same company. These addresses are grouped together within the same contact.
\nIt's important to note that an address must always be within a contact. If your system does not support multiple addresses for a single contact, you should generate a separate contact for each address, ideally using the same or similar name. This approach has no negative effects and is a legitimate way to structure your data, especially when multiple addresses are not inherently supported.
\n","_postman_id":"a10da4c2-40c3-4317-9bb5-048410243bc3","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}}},{"name":"Addresses","item":[{"name":"Addresses Create","id":"3221fc43-6ebf-4cb2-9b70-4d35e7c7c33c","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"identifier\": \"MY-UNIQUE-ID\",\n \"MyCustomUniqueGroupName\": {\n \"MyOwnColumnName\": \"My Column Value\"\n }\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/contacts/{{contact_identifier}}/addresses","description":"identifierPurpose: A unique key that identifies each record.
\nRequirements:
\nShould match your database table's primary key.
\nMust be unique across all systems to avoid conflicts.
\nIf your ID is just a number, prefix it with a short code representing your software (e.g., \"serp-1\" for \"Super-ERP\" with ID 1).
Example:\"serp-1\" instead of \"1\".
Important:
Never use just a number like \"1\" alone, as it could conflict with IDs from Alution.
Enclose your data fields inside the unique group you specified when importing your custom schema.
\nPurpose:
\nEnsures the data abides by your schema's validation rules.
\nData will only be processed if the fields are correctly mapped.
\nNote:
\nUnmapped fields, even if present in your group, will be ignored.
\nIf your table has few fields and the total request size stays under 10MB, you can send all fields at once without special handling.
\nThis data structure is used for both creating new records and updating existing ones for each model in your provider group.
\n","urlObject":{"path":["contacts","{{contact_identifier}}","addresses"],"host":["https://dev.alution.test/api/v1"],"query":[],"variable":[]}},"response":[],"_postman_id":"3221fc43-6ebf-4cb2-9b70-4d35e7c7c33c"},{"name":"Addresses Index","id":"6b4a970e-44e1-41a5-9dcd-11eefc56269a","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/contacts/{{contact_identifier}}/addresses?relations=customFieldSchemas&perPage=10&page=1","urlObject":{"path":["contacts","{{contact_identifier}}","addresses"],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Appending customFieldSchemas as a value to the relationsparameter, will ensure that your data is
\n","type":"text/plain"},"key":"relations","value":"customFieldSchemas"},{"description":{"content":"Set the number of entries loaded per page. Keep in mind that loading too many entries or large items may cause a 403 error due to response size limitations in Nginx. It's better to keep the page size smaller and perform more frequent iterations, which is usually the more reliable approach.
\n","type":"text/plain"},"key":"perPage","value":"10"},{"description":{"content":"The page you want to request.
\n","type":"text/plain"},"key":"page","value":"1"}],"variable":[]}},"response":[],"_postman_id":"6b4a970e-44e1-41a5-9dcd-11eefc56269a"},{"name":"Addresses Show","id":"0c41c57a-0a0f-47e9-9048-886cc903d2c4","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/contacts/{{contact_identifier}}/addresses/{{address_identifier}}?relations=customFieldSchemas","urlObject":{"path":["contacts","{{contact_identifier}}","addresses","{{address_identifier}}"],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Appending customFieldSchemas as a value to the relationsparameter, will ensure that your data is
\n","type":"text/plain"},"key":"relations","value":"customFieldSchemas"}],"variable":[]}},"response":[],"_postman_id":"0c41c57a-0a0f-47e9-9048-886cc903d2c4"}],"id":"50d0c85b-2d1f-4d55-94b3-433d18594066","description":"Addresses describe the physical location of a company, as previously mentioned in the Contacts section. An address represents the entity that holds tickets, users, and projects in place within the system.
\nAddresses are required to be contained within a contact. It is recommended to name the primary address similarly to the contact name, and indicate whether it is primary or secondary by including this in the address name.
\nFor example, if the contact is \"Jane Doe LLC,\" a primary address could be named \"Jane Doe LLC - Primary\" and a secondary address \"Jane Doe LLC - Secondary.\"
\nThis naming convention helps prevent confusion for users, as Alution allows searching for contacts and addresses. If addresses are only called \"Primary\" or \"Secondary,\" it can be difficult to distinguish between different entries when multiple addresses or contacts share the same name. Clear, descriptive naming improves search accuracy and usability.
\n","_postman_id":"50d0c85b-2d1f-4d55-94b3-433d18594066","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}}},{"name":"Users","item":[{"name":"Users Create","id":"0eb49a5e-1339-44d5-8530-8eb899430011","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"identifier\": \"MY-UNIQUE-ID\",\n \"MyCustomUniqueGroupName\": {\n \"MyOwnColumnName\": \"My Column Value\"\n }\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/contacts/{{contact_id}}/addresses/{{address_id}}/users","description":"identifierPurpose: A unique key that identifies each record.
\nRequirements:
\nShould match your database table's primary key.
\nMust be unique across all systems to avoid conflicts.
\nIf your ID is just a number, prefix it with a short code representing your software (e.g., \"serp-1\" for \"Super-ERP\" with ID 1).
Example:\"serp-1\" instead of \"1\".
Important:
Never use just a number like \"1\" alone, as it could conflict with IDs from Alution.
Enclose your data fields inside the unique group you specified when importing your custom schema.
\nPurpose:
\nEnsures the data abides by your schema's validation rules.
\nData will only be processed if the fields are correctly mapped.
\nNote:
\nUnmapped fields, even if present in your group, will be ignored.
\nIf your table has few fields and the total request size stays under 10MB, you can send all fields at once without special handling.
\nThis data structure is used for both creating new records and updating existing ones for each model in your provider group.
\n","urlObject":{"path":["contacts","{{contact_id}}","addresses","{{address_id}}","users"],"host":["https://dev.alution.test/api/v1"],"query":[],"variable":[]}},"response":[],"_postman_id":"0eb49a5e-1339-44d5-8530-8eb899430011"},{"name":"Users Index","id":"79c5adee-28e3-427e-9ff5-71beb0a55c32","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/contacts/{{contact_identifier}}/addresses/{{address_identifier}}/users?relations=customFieldSchemas&perPage=10&page=1","urlObject":{"path":["contacts","{{contact_identifier}}","addresses","{{address_identifier}}","users"],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Appending customFieldSchemas as a value to the relationsparameter, will ensure that your data is
\n","type":"text/plain"},"key":"relations","value":"customFieldSchemas"},{"description":{"content":"Set the number of entries loaded per page. Keep in mind that loading too many entries or large items may cause a 403 error due to response size limitations in Nginx. It's better to keep the page size smaller and perform more frequent iterations, which is usually the more reliable approach.
\n","type":"text/plain"},"key":"perPage","value":"10"},{"description":{"content":"The page you want to request.
\n","type":"text/plain"},"key":"page","value":"1"}],"variable":[]}},"response":[],"_postman_id":"79c5adee-28e3-427e-9ff5-71beb0a55c32"},{"name":"Users Show","id":"5548a3c5-f6d3-451a-a0fb-18ca1deadfbc","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/contacts/{{contact_identifier}}/addresses/{{address_identifier}}/users/{{user_udentifier}}?relations=customFieldSchemas","urlObject":{"path":["contacts","{{contact_identifier}}","addresses","{{address_identifier}}","users","{{user_udentifier}}"],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Appending customFieldSchemas as a value to the relationsparameter, will ensure that your data is
\n","type":"text/plain"},"key":"relations","value":"customFieldSchemas"}],"variable":[]}},"response":[],"_postman_id":"5548a3c5-f6d3-451a-a0fb-18ca1deadfbc"}],"id":"a9c9cbfc-67b0-4f39-baf7-070abf8bf046","description":"In Alution, users are not only individuals with full system access; they can also represent a person at a company's location, such as an employee or contact.
\nIt is mandatory that a user is always created within an address. This is because, in Alution, users are associated directly with addresses. For example, if Mr. Jon Doe works at the primary address of \"Jane Doe LLC,\" the user record for Jon Doe will be linked to that specific address. This setup allows you to see exactly where the user is located when viewing their details.
\nThis approach is also useful when dealing with guest access, as it enables limiting user permissions to only information related to their address or company.
\nIn Alution, the distinction between a customer or contact user and an employee/worker is made via the group permission \"can consume license.\"
\nIf the user has this permission enabled, they are considered an employee and will be billed or valued as such.
\nIf not, they are treated as a contact user or guest, with limited access.
\nThis structure helps manage user roles, permissions, and billing appropriately, based on their relationship to the company and their intended system usage.
\n","_postman_id":"a9c9cbfc-67b0-4f39-baf7-070abf8bf046","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}}},{"name":"Projects","item":[{"name":"Projects Create","id":"a88057c9-35ba-42c1-bb71-e61a20f27786","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"identifier\": \"MY-UNIQUE-ID\",\n \"MyCustomUniqueGroupName\": {\n \"MyOwnColumnName\": \"My Column Value\"\n }\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/contacts/{{contact_identifier}}/addresses/{{address_identifier}}/projects","description":"identifierPurpose: A unique key that identifies each record.
\nRequirements:
\nShould match your database table's primary key.
\nMust be unique across all systems to avoid conflicts.
\nIf your ID is just a number, prefix it with a short code representing your software (e.g., \"serp-1\" for \"Super-ERP\" with ID 1).
Example:\"serp-1\" instead of \"1\".
Important:
Never use just a number like \"1\" alone, as it could conflict with IDs from Alution.
Enclose your data fields inside the unique group you specified when importing your custom schema.
\nPurpose:
\nEnsures the data abides by your schema's validation rules.
\nData will only be processed if the fields are correctly mapped.
\nNote:
\nUnmapped fields, even if present in your group, will be ignored.
\nIf your table has few fields and the total request size stays under 10MB, you can send all fields at once without special handling.
\nThis data structure is used for both creating new records and updating existing ones for each model in your provider group.
\n","urlObject":{"path":["contacts","{{contact_identifier}}","addresses","{{address_identifier}}","projects"],"host":["https://dev.alution.test/api/v1"],"query":[],"variable":[]}},"response":[],"_postman_id":"a88057c9-35ba-42c1-bb71-e61a20f27786"},{"name":"Projects Index","id":"7e23ec34-2482-48cd-8cfe-56e3fa49b506","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/contacts/{{contact_identifier}}/addresses/{{address_identifier}}/projects?relations=customFieldSchemas&perPage=10&page=1","urlObject":{"path":["contacts","{{contact_identifier}}","addresses","{{address_identifier}}","projects"],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Appending customFieldSchemas as a value to the relationsparameter, will ensure that your data is
\n","type":"text/plain"},"key":"relations","value":"customFieldSchemas"},{"description":{"content":"Set the number of entries loaded per page. Keep in mind that loading too many entries or large items may cause a 403 error due to response size limitations in Nginx. It's better to keep the page size smaller and perform more frequent iterations, which is usually the more reliable approach.
\n","type":"text/plain"},"key":"perPage","value":"10"},{"description":{"content":"The page you want to request.
\n","type":"text/plain"},"key":"page","value":"1"}],"variable":[]}},"response":[],"_postman_id":"7e23ec34-2482-48cd-8cfe-56e3fa49b506"},{"name":"Projects Show","id":"e8b9f880-0b2e-4e03-9e2f-fc03bacad08b","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/contacts/{{contact_identifier}}/addresses/{{address_identifier}}/projects/{{project_identifier}}/?relations=customFieldSchemas","urlObject":{"path":["contacts","{{contact_identifier}}","addresses","{{address_identifier}}","projects","{{project_identifier}}",""],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Appending customFieldSchemas as a value to the relationsparameter, will ensure that your data is
\n","type":"text/plain"},"key":"relations","value":"customFieldSchemas"}],"variable":[]}},"response":[],"_postman_id":"e8b9f880-0b2e-4e03-9e2f-fc03bacad08b"}],"id":"5063fe0f-cbbe-4e3e-b0a7-bb9b481c0554","description":"Projects are currently represented as a group entity in the system. When syncing projects to an address, the project will become available for selection during ticket creation. This setup allows you to directly associate a ticket with a project at the moment of closing or when transferring data back to your software, facilitating seamless project management and integration.
\n","_postman_id":"5063fe0f-cbbe-4e3e-b0a7-bb9b481c0554","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}}},{"name":"Products","item":[{"name":"Products Create","id":"24a8436b-d57d-43ab-8507-ace814a54f5e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"identifier\": \"MY-UNIQUE-ID\",\n \"MyCustomUniqueGroupName\": {\n \"MyOwnColumnName\": \"My Column Value\"\n }\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/products","description":"identifierPurpose: A unique key that identifies each record.
\nRequirements:
\nShould match your database table's primary key.
\nMust be unique across all systems to avoid conflicts.
\nIf your ID is just a number, prefix it with a short code representing your software (e.g., \"serp-1\" for \"Super-ERP\" with ID 1).
Example:\"serp-1\" instead of \"1\".
Important:
Never use just a number like \"1\" alone, as it could conflict with IDs from Alution.
Enclose your data fields inside the unique group you specified when importing your custom schema.
\nPurpose:
\nEnsures the data abides by your schema's validation rules.
\nData will only be processed if the fields are correctly mapped.
\nNote:
\nUnmapped fields, even if present in your group, will be ignored.
\nIf your table has few fields and the total request size stays under 10MB, you can send all fields at once without special handling.
\nThis data structure is used for both creating new records and updating existing ones for each model in your provider group.
\n","urlObject":{"path":["products"],"host":["https://dev.alution.test/api/v1"],"query":[],"variable":[]}},"response":[],"_postman_id":"24a8436b-d57d-43ab-8507-ace814a54f5e"},{"name":"Products Index","id":"04098a94-57e3-4f73-92e3-e62c94cd94ee","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/products?relations=customFieldSchemas&perPage=10&page=1","urlObject":{"path":["products"],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Appending customFieldSchemas as a value to the relationsparameter, will ensure that your data is
\n","type":"text/plain"},"key":"relations","value":"customFieldSchemas"},{"description":{"content":"Set the number of entries loaded per page. Keep in mind that loading too many entries or large items may cause a 403 error due to response size limitations in Nginx. It's better to keep the page size smaller and perform more frequent iterations, which is usually the more reliable approach.
\n","type":"text/plain"},"key":"perPage","value":"10"},{"description":{"content":"The page you want to request.
\n","type":"text/plain"},"key":"page","value":"1"}],"variable":[]}},"response":[],"_postman_id":"04098a94-57e3-4f73-92e3-e62c94cd94ee"},{"name":"Products Show","id":"622b1333-35d0-4a42-b934-76099cc77bd4","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/products/{{product_identifier}}?relations=customFieldSchemas","urlObject":{"path":["products","{{product_identifier}}"],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Appending customFieldSchemas as a value to the relationsparameter, will ensure that your data is
\n","type":"text/plain"},"key":"relations","value":"customFieldSchemas"}],"variable":[]}},"response":[],"_postman_id":"622b1333-35d0-4a42-b934-76099cc77bd4"}],"id":"d82f75ca-a42a-479f-9ad9-a3983843f249","description":"Products are currently managed exclusively via the API. This is a crucial component, especially if your system is used for time-tracking or if products need to be added directly within a ticket.
\nProducts can be linked directly to a ticket or combined with a time record, which will be used when transferring a time-entry along with a closed ticket back to your software. For example, when a ticket is closed and a transfer-type is specified, the associated products and time-records will be included in the transfer, ensuring comprehensive and accurate data synchronization.
\n","_postman_id":"d82f75ca-a42a-479f-9ad9-a3983843f249","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}}},{"name":"Transfer-Types","item":[{"name":"Transfer-Types","id":"844dd011-6032-405f-8505-1847b22ff922","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"identifier\": \"MY-UNIQUE-ID\",\n \"MyCustomUniqueGroupName\": {\n \"MyOwnColumnName\": \"My Column Value\"\n }\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/transfer-types","description":"identifierPurpose: A unique key that identifies each record.
\nRequirements:
\nShould match your database table's primary key.
\nMust be unique across all systems to avoid conflicts.
\nIf your ID is just a number, prefix it with a short code representing your software (e.g., \"serp-1\" for \"Super-ERP\" with ID 1).
Example:\"serp-1\" instead of \"1\".
Important:
Never use just a number like \"1\" alone, as it could conflict with IDs from Alution.
Enclose your data fields inside the unique group you specified when importing your custom schema.
\nPurpose:
\nEnsures the data abides by your schema's validation rules.
\nData will only be processed if the fields are correctly mapped.
\nNote:
\nUnmapped fields, even if present in your group, will be ignored.
\nIf your table has few fields and the total request size stays under 10MB, you can send all fields at once without special handling.
\nThis data structure is used for both creating new records and updating existing ones for each model in your provider group.
\n","urlObject":{"path":["transfer-types"],"host":["https://dev.alution.test/api/v1"],"query":[],"variable":[]}},"response":[],"_postman_id":"844dd011-6032-405f-8505-1847b22ff922"},{"name":"Transfer-Types Index","id":"8aff6918-3fca-4eda-bc76-44d21f56d27c","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/contacts?relations=customFieldSchemas&perPage=10&page=1","urlObject":{"path":["contacts"],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Appending customFieldSchemas as a value to the relationsparameter, will ensure that your data is
\n","type":"text/plain"},"key":"relations","value":"customFieldSchemas"},{"description":{"content":"Set the number of entries loaded per page. Keep in mind that loading too many entries or large items may cause a 403 error due to response size limitations in Nginx. It's better to keep the page size smaller and perform more frequent iterations, which is usually the more reliable approach.
\n","type":"text/plain"},"key":"perPage","value":"10"},{"description":{"content":"The page you want to request.
\n","type":"text/plain"},"key":"page","value":"1"}],"variable":[]}},"response":[],"_postman_id":"8aff6918-3fca-4eda-bc76-44d21f56d27c"},{"name":"Transfer-Types Show","id":"2f4b1cfa-61ca-441d-94af-a3869d427937","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/contacts/MY-UNIQUE-ID?relations=customFieldSchemas","urlObject":{"path":["contacts","MY-UNIQUE-ID"],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Appending customFieldSchemas as a value to the relationsparameter, will ensure that your data is
\n","type":"text/plain"},"key":"relations","value":"customFieldSchemas"}],"variable":[]}},"response":[],"_postman_id":"2f4b1cfa-61ca-441d-94af-a3869d427937"}],"id":"9d001285-2b67-4285-853e-e0960ce6a316","description":"Transfer-Types are definitions provided by your software to specify the category or nature of a process, such as offers, invoices, projects, or other document types. Transfer-Types typically include offers, invoices, projects, purchase orders, and delivery notes.
\nWhen a ticket is closed, a Transfer-Type can be selected to indicate what the ticket should represent and where it should be added within your system. Some ERPs allow creating custom categories, but at their core, these are variations of the same concept. These transfer-types enable synchronization to Alution, allowing customers to activate custom transfer options.
\nFor instance, closing a ticket could automatically add the ticket to the \"Tickets\" category inside your ERP system. If your system does not support custom categories, you need to define at least one transfer-type to enable the transfer of tickets into your system effectively.
\n","_postman_id":"9d001285-2b67-4285-853e-e0960ce6a316","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}}},{"name":"Transfers","item":[{"name":"Transfers Index","id":"74a44a98-a1e0-4a67-ac4b-2049d6310295","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/transfers?type=ticket&relations=transferable.timeRecords.recordType.product.customFieldSchemas,transferable.products.customFieldSchemas,transferable.address.customFieldSchemas,transferable.project.customFieldSchemas","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}},"urlObject":{"path":["transfers"],"host":["https://dev.alution.test/api/v1"],"query":[{"description":{"content":"Currently, only \"ticket\" is available.
\n","type":"text/plain"},"key":"type","value":"ticket"},{"description":{"content":"Optional relationships to retrieve all related data associated with this Ticket transfer, such as products, time records, etc., and the ticket itself.
\n","type":"text/plain"},"key":"relations","value":"transferable.timeRecords.recordType.product.customFieldSchemas,transferable.products.customFieldSchemas,transferable.address.customFieldSchemas,transferable.project.customFieldSchemas"}],"variable":[]}},"response":[{"id":"d51c611b-ec89-4a8f-8419-e442448a37ae","name":"Transfers Index","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://dev.alution.test/api/v1/transfers?type=ticket&relations=transferable.timeRecords.recordType.product.customFieldSchemas,transferable.products.customFieldSchemas,transferable.address.customFieldSchemas,transferable.project.customFieldSchemas","host":["https://dev.alution.test/api/v1"],"path":["transfers"],"query":[{"key":"type","value":"ticket","description":"Currently, only \"ticket\" is available."},{"key":"relations","value":"transferable.timeRecords.recordType.product.customFieldSchemas,transferable.products.customFieldSchemas,transferable.address.customFieldSchemas,transferable.project.customFieldSchemas","description":"Optional relationships to retrieve all related data associated with this Ticket transfer, such as products, time records, etc., and the ticket itself."}]}},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Server","value":"nginx/1.27.4"},{"key":"Content-Type","value":"application/json"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Connection","value":"keep-alive"},{"key":"Vary","value":"Accept-Encoding"},{"key":"X-Powered-By","value":"PHP/8.4.4"},{"key":"Cache-Control","value":"no-cache, private"},{"key":"Date","value":"Fri, 25 Jul 2025 09:12:23 GMT"},{"key":"Access-Control-Allow-Origin","value":"*"},{"key":"Content-Encoding","value":"gzip"}],"cookie":[],"responseTime":null,"body":"{\n \"data\": [\n {\n \"id\": 1,\n \"transferred_at\": null,\n \"response_status\": null,\n \"response_message\": null,\n \"response_data\": null,\n \"transferable_type\": \"ticket\",\n \"transferable_id\": 1,\n \"custom_date\": null,\n \"transfer_type_reference\": null,\n \"transferType\": {\n \"id\": 1,\n \"identifier\": \"bsoft-vg-1\",\n \"name\": \"Rechnungsvorgang\",\n \"description\": \"Der Ticket wird beim Übertragen in eine Rechnung innerhalb von Buttlersoft umgewandelt.\\n\\n\",\n \"definitions\": null,\n \"is_active\": 1,\n \"is_globally_available\": 1,\n \"icon\": \"\",\n \"related_type\": \"ticket\",\n \"created_at\": null,\n \"updated_at\": null,\n \"deleted_at\": null,\n \"reference_template\": \"\"\n },\n \"transferable\": {\n \"id\": 1,\n \"title\": \"Drucker funktioniert nicht\",\n \"description\": null,\n \"address_id\": 42,\n \"closed_at\": \"2025-07-25T09:09:29.000000Z\",\n \"closed_by\": 1,\n \"reopened_at\": null,\n \"reopened_by\": null,\n \"created_at\": \"2025-07-25T08:31:11.000000Z\",\n \"created_by\": 1,\n \"transfer_note\": null,\n \"review_survey_requested\": 0,\n \"is_locked\": 0,\n \"reference\": null,\n \"address\": {\n \"id\": 42,\n \"identifier\": \"bsoft-kdr-1069\",\n \"name\": \"Dr. Dovie Stanton\",\n \"email\": \"rolfson.coby@example.org\",\n \"phone\": \"+1-678-252-8594\",\n \"fax\": \"ut\",\n \"floor_number\": \"dolores\",\n \"street_name\": \"Ramon Larkin\",\n \"street_number\": \"Nienow Tunnel\",\n \"zip_code\": \"75686-0798\",\n \"city\": \"Lake Shawna\",\n \"state_province\": \"ab\",\n \"country\": \"Somalia\",\n \"website\": \"explicabo\",\n \"description\": \"Nam quia dolorem voluptatem perferendis quae laborum. Nobis commodi et sit eum aperiam expedita. Non omnis deleniti qui molestias repellat quibusdam.\",\n \"latitude\": \"67.317146\",\n \"longitude\": \"-55.578271\",\n \"is_primary_address\": 1,\n \"BpNexT\": {\n \"AnsNr\": null,\n \"AdrNr\": null,\n \"AendDat\": \"1970-01-01T13:37:00.0000000Z\"\n }\n },\n \"project\": null,\n \"timeRecords\": [\n {\n \"id\": 1,\n \"run_seconds\": 2280,\n \"paused_seconds\": 0,\n \"total_seconds\": 2280,\n \"math_script_result\": 4,\n \"finished_recording\": 1,\n \"recorded_by\": 1,\n \"updated_by\": 1,\n \"record_type_id\": 1,\n \"started_at\": \"2025-07-25T11:37:00.000000Z\",\n \"finished_at\": \"2025-07-25T12:15:00.000000Z\",\n \"created_at\": \"2025-07-25T09:08:12.000000Z\",\n \"updated_at\": \"2025-07-25T09:09:14.000000Z\",\n \"timeRecordObject\": {\n \"content\": \"Verbindung zum Drucker von Frau Dr. Dr. Rebeka Nitzsche via Fernwartung hergestellt
Diagnose des Problems (Verbindungs- und Treiberprobleme) durchgeführt
Software- und Treiberaktualisierungen eingespielt
Einstellungen am Drucker überprüft und angepasst
Netzwerkverbindung stabilisiert
Drucker erfolgreich getestet und Funktion bestätigt
Dienstleistung per Fernwartung
durchgeführt von Administrator am 25.07.2025
von 13:37 Uhr bis 14:15 Uhr
1 AW entspricht 10 min
durchgeführte Tätigkeiten:
Verbindung zum Drucker von Frau Dr. Dr. Rebeka Nitzsche via Fernwartung hergestellt
Diagnose des Problems (Verbindungs- und Treiberprobleme) durchgeführt
Software- und Treiberaktualisierungen eingespielt
Einstellungen am Drucker überprüft und angepasst
Netzwerkverbindung stabilisiert
Drucker erfolgreich getestet und Funktion bestätigt
After you have fetched a transfer and successfully handled the ticket within your software, you must notify Alution about the outcome. This involves PATCHing the transfer object with status information to indicate whether the transfer was successful or if it failed, along with the reason for failure if applicable.
\nImportant notes:
\nOnce a ticket has been transferred successfully, it cannot be reopened (via the frontend view).
\nDuring an ongoing transfer, the user can cancel or retry the transfer, but after completion, the ticket's state is final.
\nYou should include the following fields:
\nresponse_status:
An integer representing the HTTP status code indicating the transfer result such like
200 for success (transfer completed successfully).
422 for failed transfer (unprocessed entity), which should include a response_message explaining the reason.
any other matching HTTP status code
\nresponse_message (optional):
A string containing the reason for failure or additional information.
response_data (optional):
An array containing related data if needed. Currently, it can be empty or omitted.
When set to 200, Alution marks the transfer as successful:
\nThe ticket will be locked.
\nIf configured, a badge job will be triggered.
\nThe transfer object will be removed upon future GET requests to the index endpoint.
\nWhen set to 422 or other error codes, Alution will interpret this as a failure and handle it accordingly, with the response_message providing the reason.
Transfers in Alution are the process of moving a ticket or data from alution into your software. This could mean converting a ticket into an invoice, sending it to an external system.
\nOnce a transfer is completed successfully, the ticket becomes locked and cannot be reopened. If the transfer fails, it remains possible to retry or cancel the process.
\n","_postman_id":"f4fe76a8-9841-48bf-9703-04e32731b05a","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}}},{"name":"Providers","item":[{"name":"Providers Create","id":"bfa232bf-e84e-4130-96f2-bacf1d787381","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"name\": \"Buttlersoft\",\n \"description\": \"Keeping track of your customers, while providing the cleanest services!\",\n \"group\": \"BSoft\",\n \"legal_name\": \"Victoria Housekeeping Co.\",\n \"privacy_policy_url\": \"https://bsoft.com/privacy\",\n \"support_url\": \"https://bsoft.com/support\",\n \"manual_field_mapping_disabled\": false\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/providers","urlObject":{"path":["providers"],"host":["https://dev.alution.test/api/v1"],"query":[],"variable":[]}},"response":[{"id":"b311955f-11a1-41c9-935a-8de82876c982","name":"Providers Create","originalRequest":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"name\": \"Buttlersoft\",\n \"description\": \"Keeping track of your customers, while providing the cleanest services!\",\n \"group\": \"BSoft\",\n \"legal_name\": \"Victoria Housekeeping Co.\",\n \"privacy_policy_url\": \"https://bsoft.com/privacy\",\n \"support_url\": \"https://bsoft.com/support\"\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/providers"},"status":"Created","code":201,"_postman_previewlanguage":"json","header":[{"key":"Server","value":"nginx/1.27.4"},{"key":"Content-Type","value":"application/json"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Connection","value":"keep-alive"},{"key":"X-Powered-By","value":"PHP/8.4.4"},{"key":"Cache-Control","value":"no-cache, private"},{"key":"Date","value":"Wed, 23 Jul 2025 10:44:50 GMT"},{"key":"Access-Control-Allow-Origin","value":"*"}],"cookie":[],"responseTime":null,"body":"{\n \"id\": 1,\n \"name\": \"Buttlersoft\",\n \"description\": \"Keeping track of your customers, while providing the cleanest services!\",\n \"group\": \"BSoft\",\n \"legal_name\": \"Victoria Housekeeping Co.\",\n \"privacy_policy_url\": \"https://bsoft.com/privacy\",\n \"support_url\": null,\n \"created_at\": \"2025-07-23T10:44:50.000000Z\",\n \"updated_at\": \"2025-07-23T10:44:50.000000Z\"\n}"}],"_postman_id":"bfa232bf-e84e-4130-96f2-bacf1d787381"},{"name":"Providers Show","id":"215052c1-eff4-4430-b9b5-9a221fca4822","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":false},"method":"GET","header":[],"url":"https://dev.alution.test/api/v1/providers/{{group_or_id}}?relations=settings","urlObject":{"path":["providers","{{group_or_id}}"],"host":["https://dev.alution.test/api/v1"],"query":[{"key":"relations","value":"settings"}],"variable":[]}},"response":[],"_postman_id":"215052c1-eff4-4430-b9b5-9a221fca4822"}],"id":"ed8bceb7-80f0-4876-8cf0-247c41d7ad63","description":"Registering as a Provider and Binding Your Group
\nTo maximize your integration's capabilities, you have the option to register your group as a provider and associate it with your software or organization. While optional, this step is highly recommended to enhance your user experience and streamline operations.
\nWhy Register Your Group as a Provider?
For example, if your group is named \"MyCustomGroup\", registering it as a provider allows you to:
Display your legal company name to users for clarity and branding
\nProvide support and privacy policy URLs to foster transparency and build trust
\nAdd ProviderSettings to your provider, enabling you to offer customized, user-specific settings directly within your application
Advantages of Utilizing ProviderSettings
Integrating ProviderSettings enables you to deliver configuration options tailored to individual users without developing a custom settings interface from scratch. While direct integration of settings within your app is perfectly valid—especially for first-party integrations—utilizing provider settings through Alution offers added benefits:
Automatic Settings Page Generation: Alution will generate a dedicated settings interface under the \"Integrations\" section based on your defined ProviderSettings.
Simplified User Configuration: Users can easily adjust their preferences without navigating away from their workflow, reducing support overhead and improving user satisfaction.
\nPractical Example:
Suppose your application manages contact categories such as \"Customer\" and \"Vendor\". You want users to choose whether to sync all contacts, only customers, or only vendors. You can define a ProviderSetting for this choice.
When users access the integration via Alution, they will see a dropdown menu with these options and can select their preferred sync setting directly—without needing to access your server or application interface. Your system can then retrieve this setting via a single API call, enabling seamless and flexible contact synchronization.
\n","_postman_id":"ed8bceb7-80f0-4876-8cf0-247c41d7ad63","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}}},{"name":"Provider-Settings","item":[{"name":"Provider-Settings Create","id":"2c8e46fe-fcdb-4289-9545-927cc62b3e27","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"name\": \"categories_to_sync\",\n \"friendly_name\": \"Categories to Sync\",\n \"description\": \"Select which categories should be synced between Buttlersoft and Alution.\",\n \"type\": \"array\",\n \"options\": {\n \"vendor\": \"Sync Vendors\",\n \"customer\": \"Sync Customers\"\n },\n \"validation_rules\": {\n \"required\": true,\n \"*\": [\n \"string\",\n \"distinct\",\n \"in:customer,vendor\"\n ]\n },\n \"value\": [\n \"customer\"\n ]\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/providers/{{group_or_id}}/settings","description":"integer
\ndouble
\nboolean
\narray
\nstring
\nvalidation_rules are a critical part of defining provider settings, ensuring that user-provided values are valid, consistent, and within expected bounds.
These rules are specified as an object (associative array), where each key represents a validation rule, and the value provides parameters or details
\nThe type will always be automatically validated
The * rule indicates that the array value will be used to validate each entry within the array object itself.
\nNote: \"required\" and \"nullable\" are booleans. Set the value to true if you want them to be applied; otherwise, they are not applied. The only exception is if the entire array is a string array—then, including only the key (e.g., \"required\" or [\"required\"]) is enough.
The validation rules allowed rules, including but not limited to:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}},"urlObject":{"path":["providers","{{group_or_id}}","settings"],"host":["https://dev.alution.test/api/v1"],"query":[],"variable":[]}},"response":[{"id":"92296e38-f06e-4ff9-9a8d-15cc98177ce3","name":"Provider-Settings Create","originalRequest":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"name\": \"categories_to_sync\",\n \"friendly_name\": \"Categories to Sync\",\n \"description\": \"Select which categories should be synced between Buttlersoft and Alution.\",\n \"type\": \"array\",\n \"options\": {\n \"vendor\": \"Sync Vendors\",\n \"customer\": \"Sync Customers\"\n },\n \"validation_rules\": {\n \"required\": true,\n \"*\": [\n \"string\",\n \"distinct\",\n \"in:customer,vendor\"\n ]\n },\n \"value\": [\n \"customer\"\n ]\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/providers/{{group_or_id}}/settings"},"status":"Created","code":201,"_postman_previewlanguage":"json","header":[{"key":"Server","value":"nginx/1.27.4"},{"key":"Content-Type","value":"application/json"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Connection","value":"keep-alive"},{"key":"X-Powered-By","value":"PHP/8.4.4"},{"key":"Cache-Control","value":"no-cache, private"},{"key":"Date","value":"Fri, 25 Jul 2025 13:26:48 GMT"},{"key":"Access-Control-Allow-Origin","value":"*"}],"cookie":[],"responseTime":null,"body":"{\n \"id\": 12,\n \"name\": \"categories_to_sync\",\n \"friendly_name\": \"Categories to Sync\",\n \"description\": \"Select which categories should be synced between Buttlersoft and Alution.\",\n \"type\": \"array\",\n \"options\": {\n \"vendor\": \"Sync Vendors\",\n \"customer\": \"Sync Customers\"\n },\n \"validation_rules\": {\n \"required\": true,\n \"*\": [\n \"string\",\n \"distinct\",\n \"in:customer,vendor\"\n ]\n },\n \"value\": [\n \"customer\"\n ]\n}"},{"id":"ef9b1675-7c1a-4a5e-a0ca-fd00332179bd","name":"2. Provider-Settings Create","originalRequest":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"name\": \"my_double\",\n \"friendly_name\": \"My Double\",\n \"type\": \"double\",\n \"validation_rules\": [\n \"nullable\"\n ]\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/providers/{{group_or_id}}/settings"},"status":"Created","code":201,"_postman_previewlanguage":"json","header":[{"key":"Server","value":"nginx/1.27.4"},{"key":"Content-Type","value":"application/json"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Connection","value":"keep-alive"},{"key":"X-Powered-By","value":"PHP/8.4.4"},{"key":"Cache-Control","value":"no-cache, private"},{"key":"Date","value":"Fri, 25 Jul 2025 14:21:36 GMT"},{"key":"Access-Control-Allow-Origin","value":"*"}],"cookie":[],"responseTime":null,"body":"{\n \"id\": 14,\n \"name\": \"my_double\",\n \"friendly_name\": \"My Double\",\n \"description\": null,\n \"type\": \"null\",\n \"options\": null,\n \"validation_rules\": [\n \"nullable\"\n ],\n \"value\": null\n}"},{"id":"0240b9ee-4a35-42db-94d7-d3d40da6e17e","name":"3. Provider-Settings Create","originalRequest":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"name\": \"my_bool\",\n \"friendly_name\": \"My Bool\",\n \"type\": \"boolean\",\n \"value\": true\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/providers/{{group_or_id}}/settings"},"status":"Created","code":201,"_postman_previewlanguage":"json","header":[{"key":"Server","value":"nginx/1.27.4"},{"key":"Content-Type","value":"application/json"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Connection","value":"keep-alive"},{"key":"X-Powered-By","value":"PHP/8.4.4"},{"key":"Cache-Control","value":"no-cache, private"},{"key":"Date","value":"Fri, 25 Jul 2025 14:22:55 GMT"},{"key":"Access-Control-Allow-Origin","value":"*"}],"cookie":[],"responseTime":null,"body":"{\n \"id\": 15,\n \"name\": \"my_bool\",\n \"friendly_name\": \"My Bool\",\n \"description\": null,\n \"type\": \"boolean\",\n \"options\": null,\n \"validation_rules\": null,\n \"value\": true\n}"}],"_postman_id":"2c8e46fe-fcdb-4289-9545-927cc62b3e27"},{"name":"Provider-Settings Update","id":"eb59ee44-9e92-4d1e-9590-4cc2c0a9219f","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"PUT","header":[],"body":{"mode":"raw","raw":"{\n \"name\": \"categories_to_sync\",\n \"friendly_name\": \"Categories to Sync\",\n \"description\": \"Select which categories should be synced between Buttlersoft and Alution.\",\n \"type\": \"array\",\n \"options\": {\n \"vendor\": \"Sync Vendors\",\n \"customer\": \"Sync Customers\"\n },\n \"validation_rules\": {\n \"required\": true,\n \"*\": [\n \"string\",\n \"distinct\",\n \"in:customer,vendor\"\n ]\n },\n \"value\": [\n \"vendor\"\n ]\n}","options":{"raw":{"language":"json"}}},"url":"https://dev.alution.test/api/v1/providers/{{group_or_id}}/settings/{{name_or_id}}","description":"Updating an existing ProviderSetting uses the same validation approach as creation. To update a setting, you need to send the complete object containing all relevant properties, including any changes, as a PUT request to the designated endpoint. This means the payload must represent the full, updated configuration of the ProviderSetting, not just the modified fields.
\nKey points:
\nThe full ProviderSetting object must be included in the request payload.
\nAll required fields, like name, type, validation_rules, etc., should be provided.
Validation rules are processed the same way during updates, ensuring data integrity with each change.
\nPartial updates (patches) are not supported unless explicitly specified; always send the complete object.
\nUsing the 'minimal' display option will return a single JSON object containing key-value pairs of name and value.
\n","type":"text/plain"},"key":"display","value":"minimal"}],"variable":[]}},"response":[{"id":"21af0f97-6d68-490f-9378-96887f28da54","name":"Default - Provider-Settings Index","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://dev.alution.test/api/v1/providers/{{group_or_id}}/settings","host":["https://dev.alution.test/api/v1"],"path":["providers","{{group_or_id}}","settings"],"query":[{"key":"display","value":"minimal","description":"Using the 'minimal' display option will return a single JSON object containing key-value pairs of name and value.","disabled":true}]}},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Server","value":"nginx/1.27.4"},{"key":"Content-Type","value":"application/json"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Connection","value":"keep-alive"},{"key":"Vary","value":"Accept-Encoding"},{"key":"X-Powered-By","value":"PHP/8.4.4"},{"key":"Cache-Control","value":"no-cache, private"},{"key":"Date","value":"Fri, 25 Jul 2025 14:14:32 GMT"},{"key":"Access-Control-Allow-Origin","value":"*"},{"key":"Content-Encoding","value":"gzip"}],"cookie":[],"responseTime":null,"body":"{\n \"data\": [\n {\n \"id\": 2,\n \"name\": \"auto_sync_enabled\",\n \"friendly_name\": \"Automatische Synchronisation\",\n \"description\": \"Wenn aktiviert, werden Änderungen automatisch übertragen. (nach Prüfintervall in Minuten)\",\n \"type\": \"boolean\",\n \"options\": null,\n \"validation_rules\": null,\n \"value\": true\n },\n {\n \"id\": 1,\n \"name\": \"categories_to_sync\",\n \"friendly_name\": \"Categories to Sync\",\n \"description\": \"Select which categories should be synced between Buttlersoft and Alution.\",\n \"type\": \"array\",\n \"options\": {\n \"vendor\": \"Sync Vendors\",\n \"customer\": \"Sync Customers\"\n },\n \"validation_rules\": {\n \"*\": [\n \"string\",\n \"distinct\",\n \"in:customer,vendor\"\n ],\n \"required\": true\n },\n \"value\": [\n \"vendor\"\n ]\n },\n {\n \"id\": 3,\n \"name\": \"update_interval_minutes\",\n \"friendly_name\": \"Prüfintervall in Minuten\",\n \"description\": \"Geben Sie hier eine Zahl zwischen 1 und 60 an, die den Minutenabstand festlegt, in dem geprüft werden soll, ob Änderungen vorliegen, die synchronisiert werden müssen.\",\n \"type\": \"integer\",\n \"options\": null,\n \"validation_rules\": {\n \"max\": 60,\n \"min\": 1,\n \"required\": true\n },\n \"value\": 50\n }\n ]\n}"},{"id":"42a8c1a7-0847-4798-b8e1-61fecd079501","name":"Minimal - Provider-Settings Index","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://dev.alution.test/api/v1/providers/{{group_or_id}}/settings?display=minimal","host":["https://dev.alution.test/api/v1"],"path":["providers","{{group_or_id}}","settings"],"query":[{"key":"display","value":"minimal","description":"Using the 'minimal' display option will return a single JSON object containing key-value pairs of name and value."}]}},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Server","value":"nginx/1.27.4"},{"key":"Content-Type","value":"application/json"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Connection","value":"keep-alive"},{"key":"Vary","value":"Accept-Encoding"},{"key":"X-Powered-By","value":"PHP/8.4.4"},{"key":"Cache-Control","value":"no-cache, private"},{"key":"Date","value":"Fri, 25 Jul 2025 14:14:52 GMT"},{"key":"Access-Control-Allow-Origin","value":"*"},{"key":"Content-Encoding","value":"gzip"}],"cookie":[],"responseTime":null,"body":"{\n \"auto_sync_enabled\": true,\n \"categories_to_sync\": [\n \"vendor\"\n ],\n \"update_interval_minutes\": 50\n}"}],"_postman_id":"fcf55aab-3ae9-4b67-a2e1-df683ee8269c"}],"id":"be68a357-4de8-4b4d-bc8e-f8583fbee88b","description":"ProviderSettings allow you to define configurable options that your users can manage directly within the Alution settings.
Benefits of Using ProviderSettings in Alution:
\nAutomated Settings UI: When you define ProviderSettings, Alution automatically generates a user-friendly configuration page, simplifying setup and management.
Reduced Development Effort: You avoid building custom preference UI components, leveraging Alution’s built-in form generation to streamline deployment.
\nExample Use Case:
Suppose your app manages contact synchronization with categories including \"Customer\" and \"Vendor\". You can create a ProviderSetting that offers a dropdown for users to select whether to sync all contacts, only customers, or only vendors. Once configured within Alution, users can select their preference directly through the provided interface. Your backend can then retrieve this setting via a single API call, enabling tailored, flexible synchronization processes aligned with user choices.
The Provider API uses the same endpoint as the regular User API.
\nSince tickets cannot be mapped by either the User or the Provider API, they cannot be resolved through your provided group and therefore columnfields cannot be autoresolved. However, because Alution already recognizes your identifiers (which are typically constructed using your database IDs with a specific prefix), you still can use your identifiers instead of Alution numeric IDs when creating or updating tickets.
\nBy default, Alution does not interpret identifiers passed to the endpoint. To enable identifier-based resolution, include the field \"identifier\" in your request body. When identifier is provided:
\nAlution recognizes that the ticket is being created by a Provider.
\nAll standard _id fields are disabled and replaced with _identifier fields.
\nAlution will first attempt to resolve entities using your provided identifiers.
\nAs a fallback, you may still include Alution’s internal ID, but it must be placed inside the _identifier field rather than _id (since _id fields are prohibited when \"identifier\" is set).
\nAs a provider, you can easily create tickets through the API. However, please note that currently only a limited set of ticket features is available via the Provider API. Additional functionality will be added in future updates.
\nAt this time, providers can only create and update tickets via the API. All other ticket-related actions must be performed through the frontend or the User API.
\nThese limitations are subject to change, but for now, please keep them in mind when implementing ticket creation or updates as a provider.
\n","_postman_id":"95995ecd-4a0c-4b4b-ba6f-72911a382b41","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]},"isInherited":true,"source":{"_postman_id":"08318820-cdd9-46ce-b82c-62251e9eddc4","id":"08318820-cdd9-46ce-b82c-62251e9eddc4","name":"API/v1 for Provider","type":"collection"}}}],"auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{barer_api_token}}"}]}},"event":[{"listen":"prerequest","script":{"id":"5e1b41af-d997-4318-8163-1f4062baebd3","type":"text/javascript","packages":{},"exec":[""]}},{"listen":"test","script":{"id":"866f9aa0-e43b-4080-8dec-5312c55dd671","type":"text/javascript","packages":{},"exec":[""]}}],"variable":[{"key":"tenant","value":"dev","type":"string"},{"key":"tld","value":"test","type":"string"},{"key":"domain","value":"alution","type":"string"},{"key":"schema","value":"https","type":"string"},{"key":"base_url","value":"https://dev.alution.test","type":"string"},{"key":"api_path","value":"/api/v1","type":"string"},{"key":"api_url","value":"https://dev.alution.test/api/v1","type":"string"}]}