-
Zextras Carbonio 23.6.0
-
-
- Older Version's Changelogs
- Changelog Version 23.2.0
- Changelog version 23.3.0
- Changelog Version 23.4.0
- Changelog Version 23.5.0
- Changelog Version 23.7.0
- Changelog Version 23.6.0
- Changelog version 23.9.0
- Changelog Version 23.10.0
- Changelog for Release 23.11.0 of Carbonio
- Changelog for Release 23.12.0 of Carbonio
-
-
-
-
Carbonio Community Edition
-
Suite for Zimbra
- Zextras Suite documentation
- Introduction
- Installation Instructions for Zextras Suite
- Licencing of Zextras Suite
- File Management for Licences
- Zextras Backup
- Backup and Restore by Zextras
- Zextras Backup Advanced Methods
- Zextras for Mobile
- Service for Address Books
- Troubleshooting Zextras Mobile
- Powerstore Zextras
- The Indexing of Attachments
- Extractor of External Content
- Delegated Admin Provisioning Zextras Admin
- The Zextras Drive
- Docs Zextras
- Authentique Zextras
- Team Zextras
- Video Server Zextras
- CLI
- next6 back
-
- Changelog for Zextras 3.1.x releases
- Changelog for Zextras Suite 3.2.0
- Changelog for Zextras Suite 3.3.0
- Zextras Suite Changelog - Release 3.4.0
- Changelog for Zextras Suite 3.5.0
- Changelog for Zextras Suite 3.6.0
- Changelog for Zextras Suite 3.7.0
- Changelog for Zextras Suite 3.8.0
- Changelog for Zextras Suite 3.9.0
- Changelog for Zextras Suite 3.10.0
- Changelog for Zextras Suite 3.11.0
- Changelog for Zextras Suite 3.12.0
- Changelog for Zextras Suite 3.13.0
- Changelog for Zextras Suite 3.14.0
- Changelog for Zextras Suite 3.15.0
- Changelog for Zextras Suite 3.16.0
- Changelog for Zextras Suite 3.17.0
- Changelog for Zextras Suite 3.18.0
- Zextras Suite Changelog - Release 3.19.0
- next4 back
This section is for anyone who is experienced with API programming (typically developers) who wishes to communicate with Carbonio Files via its SOAP API. As a result, it is expected that everyone reading this section is familiar with SOAP API calls.
Token of Authentication
Every API request necessitates the use of an authentication token, which may be obtained by using the AuthRequest SOAP command:
This method produces an AuthResponse with the following token:
The token must be used as a cookie on every REST request, which means it must be given to the server through the Cookie header:
API Requests Organisation
Requests to the Carbonio Files API are made as GraphQL queries with the Cookie header specified in the previous section, and are sent as HTTP POST requests to the Carbonio server at the following path:
The body of the request is a JSON-encoded object that contains the operation name, the variables involved, and certain restrictions on them, as well as a GraphQL query. A few examples of queries are given below; information on the components are provided in the next section, and reference documentation for the Carbonio Files GraphQL API is available at https://docs.zextras.com/apidoc/files_meta/.
Queries
- node_id is the node’s unique identification.
- version refers to a file’s version.
- The following ways are possible for a Query:
- The root folders (LOCAL_ROOT and TRASH_ROOT) are returned by getRootsList.
- getNode delivers a node based on the node_id.
- findNodes allows you to locate a node by using keywords and other criteria (shared by/with me, for example).
Mutations
- The terms createFolder, flagNode, trashNode, restoreNode, moveNode, copyNode, and deleteNode are self-explanatory.