Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| technical:api-intro [2025/04/12 16:16] – [API Introduction] system | technical:api-intro [2025/04/12 19:40] (current) – [Common Actions] system | ||
|---|---|---|---|
| Line 15: | Line 15: | ||
| * This also means that the API calls can be done by any other system thus making third party integration a snap. | * This also means that the API calls can be done by any other system thus making third party integration a snap. | ||
| * Each API call has to include a token which is associated with the user that logged in on the RADIUSdesk GUI. | * Each API call has to include a token which is associated with the user that logged in on the RADIUSdesk GUI. | ||
| - | * Most of the API calls will also include a cloud_id to indicate on which cloud the action is appropriate. | + | * Most of the API calls will also include a cloud_id to indicate on which cloud the action is to be applied. |
| + | |||
| + | ====== Common Actions ====== | ||
| + | * Many larger ISPs that makes use of RADIUSdesk prefer it above the commercial one size fits all solutions that already includes CRM and billing components. | ||
| + | * RADIUSdesk allows for easy integration with existing CRM systems and middle-ware. | ||
| + | * See the diagram below which illustrates the possibilities. | ||
| + | |||
| + | <panel type=" | ||
| + | |||
| + | {{: | ||
| + | </ | ||
| + | * Common actions include: | ||
| + | * Adding Profiles. | ||
| + | * Adding Realms. | ||
| + | * Adding Permanent Users. | ||
| + | * Disabling and Enabling Permanent Users. | ||
| + | * Changing Permanent User Profiles. | ||
| + | * Terminating a Permanent User's session. | ||
| + | * Deleting a Permanent User. | ||
| + | * We will cover how to do these actions using the API in dedicated Wiki pages. | ||
| + | |||
| + | |||