Clean documentation
This commit is contained in:
@@ -8,7 +8,7 @@ All the following routes require the usual authentication header. But you can al
|
||||
|
||||
- For the download routes, you can use a token generated by the `/internal/services/documents/v1/companies/:company_id/download/token` route (see bellow).
|
||||
- All the routes can use a query string `?public_token=token` to authenticate the user.
|
||||
- All the routes can use a query string `?twake_tab_token=token` to authenticate the user in the context of a channel tab for instance.
|
||||
- All the routes can use a query string `?tdrive_tab_token=token` to authenticate the user in the context of a channel tab for instance.
|
||||
|
||||
# Navigation and drive capabilities
|
||||
|
||||
@@ -299,9 +299,9 @@ Used to create a zip archive containing the requested drive items ( files and fo
|
||||
|
||||
**Auth required** : Yes
|
||||
|
||||
# Tabs (for Twake)
|
||||
# Tabs (for TDrive)
|
||||
|
||||
If you want to use the Twake tabs, you must store the configuration of the tabs in the database.
|
||||
If you want to use the TDrive tabs, you must store the configuration of the tabs in the database.
|
||||
|
||||
## Get tab configuration
|
||||
|
||||
|
||||
Reference in New Issue
Block a user