-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
2f1965c
commit 96b2149
Showing
20 changed files
with
948 additions
and
948 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,24 +1,24 @@ | ||
| --- | ||
| id: Airtable | ||
| sidebar_class_name: Airtable | ||
| --- | ||
|
|
||
| <img src={require('../../static/img/APIs/Airtable.png').default} width='64px' /> | ||
|
|
||
| # Airtable | ||
|
|
||
| This section is dedicated to the library for working with Airtable API. On this page, all the steps necessary to start working are described | ||
|
|
||
| ## Getting started | ||
|
|
||
| 1. Sign in to Airtable and go to the **[personal tokens creation page](https://airtable.com/create/tokens)**, press **Create new token** | ||
|
|
||
|  | ||
|
|
||
| 2. Enter a name for the new token, select the necessary **scopes** (permissions), and choose the databases and workspaces to which the token will have access | ||
|
|
||
|  | ||
|
|
||
| 3. Copy the new **token** | ||
|
|
||
|  | ||
| --- | ||
| id: Airtable | ||
| sidebar_class_name: Airtable | ||
| --- | ||
|
|
||
| <img src={require('../../static/img/APIs/Airtable.png').default} width='64px' /> | ||
|
|
||
| # Airtable | ||
|
|
||
| This section is dedicated to the library for working with Airtable API. On this page, all the steps necessary to start working are described | ||
|
|
||
| ## Getting started | ||
|
|
||
| 1. Sign in to Airtable and go to the **[personal tokens creation page](https://airtable.com/create/tokens)**, press **Create new token** | ||
|
|
||
|  | ||
|
|
||
| 2. Enter a name for the new token, select the necessary **scopes** (permissions), and choose the databases and workspaces to which the token will have access | ||
|
|
||
|  | ||
|
|
||
| 3. Copy the new **token** | ||
|
|
||
|  |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,62 +1,62 @@ | ||
| --- | ||
| id: Bitrix24 | ||
| sidebar_class_name: Bitrix24 | ||
| --- | ||
|
|
||
| <img src={require('../../static/img/APIs/Bitrix24.png').default} width='64px' /> | ||
|
|
||
| # Bitrix24 | ||
|
|
||
| This section is dedicated to the library for working with Bitrix24 API. On this page, all the steps necessary to start working are described | ||
|
|
||
| ## Getting started | ||
|
|
||
| There are two ways to work with Bitrix24 via API: via **Webhook** and via **local application**. For both options you need: | ||
|
|
||
| 1. Go to **Developers** in the **Applications** section of the sidebar | ||
|
|
||
|  | ||
|
|
||
| 2. Select **Other** | ||
|
|
||
|  | ||
|
|
||
| <hr/><br/> | ||
|
|
||
| ### To work via Webhook | ||
|
|
||
| 1. Select **Incoming Webhook** | ||
|
|
||
|  | ||
|
|
||
| 2. Fill in the necessary permissions in **Permissions Settings** and save the URL of the webhook. This will be used to execute library methods as the **URL** parameter. The optional **Token** parameter will always remain empty in this case | ||
|
|
||
|  | ||
|
|
||
| <hr/><br/> | ||
|
|
||
| ## To work via Local Application | ||
|
|
||
| 1. Select **Local Application** | ||
|
|
||
|  | ||
|
|
||
| 2. Select the path of the handler (if the application does not imply authorization of other users, but only Bitrix management through one administrator account, you can choose any address, for example https://localhost), tick **Use only API** (if you need only the functionality of calling library methods) and fill in the necessary permissions | ||
|
|
||
|  | ||
|
|
||
| 3. Save the **application key** and **application code** | ||
|
|
||
|  | ||
|
|
||
| 4. Using the application key, call the **GetAppAuthLink** function and follow the received link in the browser. After authorization, copy the received code from the address bar (or get it to the handler whose address was specified in point 2) | ||
|
|
||
|  | ||
|
|
||
| 5. Pass the received code, along with the application key and secret, to the **GetToken** function. Save the received **access** and **refresh tokens** | ||
|
|
||
| 6. Tokens have a limited lifetime. To get a new token, you can use the **UpdateToken** function, passing here the refresh token, key and application secret. The refresh creates not only a new access token, but also a refresh token as well | ||
|
|
||
|
|
||
|
|
||
|
|
||
| --- | ||
| id: Bitrix24 | ||
| sidebar_class_name: Bitrix24 | ||
| --- | ||
|
|
||
| <img src={require('../../static/img/APIs/Bitrix24.png').default} width='64px' /> | ||
|
|
||
| # Bitrix24 | ||
|
|
||
| This section is dedicated to the library for working with Bitrix24 API. On this page, all the steps necessary to start working are described | ||
|
|
||
| ## Getting started | ||
|
|
||
| There are two ways to work with Bitrix24 via API: via **Webhook** and via **local application**. For both options you need: | ||
|
|
||
| 1. Go to **Developers** in the **Applications** section of the sidebar | ||
|
|
||
|  | ||
|
|
||
| 2. Select **Other** | ||
|
|
||
|  | ||
|
|
||
| <hr/><br/> | ||
|
|
||
| ### To work via Webhook | ||
|
|
||
| 1. Select **Incoming Webhook** | ||
|
|
||
|  | ||
|
|
||
| 2. Fill in the necessary permissions in **Permissions Settings** and save the URL of the webhook. This will be used to execute library methods as the **URL** parameter. The optional **Token** parameter will always remain empty in this case | ||
|
|
||
|  | ||
|
|
||
| <hr/><br/> | ||
|
|
||
| ## To work via Local Application | ||
|
|
||
| 1. Select **Local Application** | ||
|
|
||
|  | ||
|
|
||
| 2. Select the path of the handler (if the application does not imply authorization of other users, but only Bitrix management through one administrator account, you can choose any address, for example https://localhost), tick **Use only API** (if you need only the functionality of calling library methods) and fill in the necessary permissions | ||
|
|
||
|  | ||
|
|
||
| 3. Save the **application key** and **application code** | ||
|
|
||
|  | ||
|
|
||
| 4. Using the application key, call the **GetAppAuthLink** function and follow the received link in the browser. After authorization, copy the received code from the address bar (or get it to the handler whose address was specified in point 2) | ||
|
|
||
|  | ||
|
|
||
| 5. Pass the received code, along with the application key and secret, to the **GetToken** function. Save the received **access** and **refresh tokens** | ||
|
|
||
| 6. Tokens have a limited lifetime. To get a new token, you can use the **UpdateToken** function, passing here the refresh token, key and application secret. The refresh creates not only a new access token, but also a refresh token as well | ||
|
|
||
|
|
||
|
|
||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,40 +1,40 @@ | ||
| --- | ||
| id: Dropbox | ||
| sidebar_class_name: Dropbox | ||
| --- | ||
|
|
||
| <img src={require('../../static/img/APIs/Dropbox.png').default} width='64px' /> | ||
|
|
||
| # Dropbox | ||
|
|
||
| This section is dedicated to the library for working with Dropbox API. On this page, all the steps necessary to start working are described | ||
|
|
||
| ## Getting started | ||
|
|
||
| 1. Login to [Dropbox Developers](https://www.dropbox.com/developers) | ||
|
|
||
|  | ||
|
|
||
| 1. Go to **App Console** | ||
|
|
||
|  | ||
|
|
||
| 2. Click on **Create app** | ||
|
|
||
|  | ||
|
|
||
| 4. Enter a name for the new application and select **Full Dropbox** | ||
|
|
||
|  | ||
|
|
||
| 5. After creation, on the application page, click **Scoped app** and select the permissions that are necessary to solve your problems. Save **AppKey** and **AppSecret** | ||
|
|
||
|  | ||
|
|
||
| 6. Get the authorization link using the *GetAuthorizationLink()* function and pass it in the browser | ||
|
|
||
|  | ||
|
|
||
| 7. Pass the **received code**, **AppKey** and **AppSecret** to the function *GetToken()*, save the received **access_token** and **refresh_token** | ||
|
|
||
| 8. After the access_token lifetime expires, it can be updated using the function *RefreshToken()* | ||
| --- | ||
| id: Dropbox | ||
| sidebar_class_name: Dropbox | ||
| --- | ||
|
|
||
| <img src={require('../../static/img/APIs/Dropbox.png').default} width='64px' /> | ||
|
|
||
| # Dropbox | ||
|
|
||
| This section is dedicated to the library for working with Dropbox API. On this page, all the steps necessary to start working are described | ||
|
|
||
| ## Getting started | ||
|
|
||
| 1. Login to [Dropbox Developers](https://www.dropbox.com/developers) | ||
|
|
||
|  | ||
|
|
||
| 1. Go to **App Console** | ||
|
|
||
|  | ||
|
|
||
| 2. Click on **Create app** | ||
|
|
||
|  | ||
|
|
||
| 4. Enter a name for the new application and select **Full Dropbox** | ||
|
|
||
|  | ||
|
|
||
| 5. After creation, on the application page, click **Scoped app** and select the permissions that are necessary to solve your problems. Save **AppKey** and **AppSecret** | ||
|
|
||
|  | ||
|
|
||
| 6. Get the authorization link using the *GetAuthorizationLink()* function and pass it in the browser | ||
|
|
||
|  | ||
|
|
||
| 7. Pass the **received code**, **AppKey** and **AppSecret** to the function *GetToken()*, save the received **access_token** and **refresh_token** | ||
|
|
||
| 8. After the access_token lifetime expires, it can be updated using the function *RefreshToken()* |
Oops, something went wrong.