Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{layout}} | ||
| 2 | {{layout-section ac:type="two_right_sidebar"}} | ||
| 3 | {{layout-cell}} | ||
| 4 | {{info}} | ||
| 5 | The information on this page applies to **iSymphony 3.2+**. | ||
| 6 | {{/info}} | ||
| 7 | |||
| 8 | = (% style="color: rgb(0,0,0);" %)Description(%%) = | ||
| 9 | |||
| 10 | The REST Live API allows external applications to query information about the current state of the iSymphony server and execute actions, via HTTP requests, that are normally available in the iSymphony client application. This API can be used to integrate external applications with iSymphony, and provide information for custom iSymphony widget development. | ||
| 11 | {{/layout-cell}} | ||
| 12 | |||
| 13 | {{layout-cell}} | ||
| 14 | {{panel title="On this page:"}} | ||
| 15 | |||
| 16 | |||
| 17 | {{toc maxLevel="2" indent="1"/}} | ||
| 18 | {{/panel}} | ||
| 19 | {{/layout-cell}} | ||
| 20 | {{/layout-section}} | ||
| 21 | |||
| 22 | {{layout-section ac:type="single"}} | ||
| 23 | {{layout-cell}} | ||
| 24 | = Resource Instance IDs = | ||
| 25 | |||
| 26 | All resource instances specify a UUID that is a unique identifier for that specific resource instance. These UUIDs can be used in the REST URLs to access a specific instance of a resource. | ||
| 27 | |||
| 28 | For example the URL below provides access to an extension instance with a UUID of ef2faba9-8557-49c1-9ffc-5a71f41c7a23, in a core server with a UUID of ca5de6c4-17bd-46ce-95a2-8b29c7812ca4: | ||
| 29 | |||
| 30 | {{code}} | ||
| 31 | http://localhost:58080/communication_manager/rest/live/coreServers/ca5de6c4-17bd-46ce-95a2-8b29c7812ca4/extensions/ef2faba9-8557-49c1-9ffc-5a71f41c7a23 | ||
| 32 | {{/code}} | ||
| 33 | |||
| 34 | {{note title="Note on UUID persistance"}} | ||
| 35 | The Live API UUIDs do not persist across restarts of the iSymphony server. If the server is restarted the objects will contain new UUIDs. Also, if an object is destroyed then re-added, even with the same configuration, the UUID that represents that object will be different from the original. | ||
| 36 | {{/note}} | ||
| 37 | |||
| 38 | = Accessing Resource Instances By Symbolic Name = | ||
| 39 | |||
| 40 | In addition to accessing resource instances by UUID, resource instances can also be accessed by their symbolic name. Most, but not all resources contain a symbolic name. The path section **getByName** can be used to access a resource instance by it symbolic name. Documentation for a specific resource will specify if the resource can be accessed by symbolic name, and what the symbolic name property is. | ||
| 41 | |||
| 42 | == Examples == | ||
| 43 | |||
| 44 | The following path will access the extension, with extension number 4224, in the core server, with a slug of default. | ||
| 45 | |||
| 46 | {{code}} | ||
| 47 | http://localhost:58080/communication_manager/rest/live/coreServers/getByName/default/extensions/getByName/4224 | ||
| 48 | {{/code}} | ||
| 49 | |||
| 50 | \\ | ||
| 51 | |||
| 52 | You can mix and match UUIDs and getByName in the REST URLs, like so: | ||
| 53 | |||
| 54 | {{code}} | ||
| 55 | http://localhost:58080/communication_manager/rest/live/coreServers/getByName/default/extensions/ef2faba9-8557-49c1-9ffc-5a71f41c7a23 | ||
| 56 | {{/code}} | ||
| 57 | |||
| 58 | == Document Notation == | ||
| 59 | |||
| 60 | When a parent resource path can be access by UUID and getByName, the path in the documentation will specify the following format: | ||
| 61 | |||
| 62 | {{code}} | ||
| 63 | [{UUID} | getByName/{symbolic_name}] | ||
| 64 | {{/code}} | ||
| 65 | |||
| 66 | This specifies that the instance can be accessed via "UUID" OR "getByName/symbolic_name". {UUID} and {symbolic_name} will be replaced with more specific names. | ||
| 67 | |||
| 68 | = REST Resources = | ||
| 69 | |||
| 70 | The Live API exposes several REST resources that allow access to the current state of specific objects in the system. All current live resources are listed below. Details concerning each resource, and their actions, can be found within the individual resource documentation pages. | ||
| 71 | |||
| 72 | |||
| 73 | |||
| 74 | {{children/}} | ||
| 75 | |||
| 76 | == Notes on Resource Documents == | ||
| 77 | |||
| 78 | Due to the interdependent nature of resources in the system, the resource path information in the documentation is split into several sections. Paths in a specific section may relate or require paths specified in other sections. | ||
| 79 | |||
| 80 | * **Root Resource Paths : **Specifies paths that can be used to access sets (multiple instances), of a resource in relation to a parent resource. | ||
| 81 | * **Instance Resource Paths : **Specifies paths that can be used to access a specific instance of a resource. These paths require a **Root Resource Path**, in most cases, but not all. | ||
| 82 | * **Sub Resource Paths : **Specifies paths that provide access to the child resources of an instance of the resource. These paths require an **Instance Resource Path.** | ||
| 83 | * **Action Paths: **Specifies paths that are used to perform actions on a specific resource instance. These paths require an **Instance Resource Path.** | ||
| 84 | |||
| 85 | \\ | ||
| 86 | {{/layout-cell}} | ||
| 87 | {{/layout-section}} | ||
| 88 | {{/layout}} |