Third Party Routing REST Endpoints

Third Party Routing
This is the Third Party Routing Service. It is used by Fusion Partners to route work objects from external Queues.
In order to use this service you must register using the '/register' method - this has to be done prior to any other calls to this service because otherwise you will not get any work to route.
The registration only needs to be done once. After a successful registration, the partner name will show up in the Queue Edit and Create screens. You can use those screen to mark a queue as External and then select the Partner that will route the work in that queue. After saving the queue configuration, all work objects that land in that queue will be sent to the partner to be routed, via the '/events' API, along with events related to agents assigned to the queue.
After setting up a queue to be externally routed, partners can get work and agent events by calling '/events' and they can propose agents for work by calling '/proposeAgent'. The agent related events are sent to partners as they happen, for example - when an agent logs in or when agents mark themselves as available for some type of work. This is the way partners that do not have their own toolbar in Fusion can learn about agent availability. We also provide an API called '/fullAgentsStatus' that will return the current status for all agents assigned to the external queue, which includes log in and availability information. Partners can use this API to establish a baseline when they first connect to Fusion, and from then on use the '/events' method to get incremental updates.
You must call the '/events' method in an infinite loop because this is a real-time working system and new events can occur at any moment of time. We interrupt the calls to '/events' because the request usually comes through proxies and we try to avoid issues like timeouts. Once a new work is received by the partner it is expected that the '/proposeAgent' method is called for that work. On each '/events' call, partners can also confirm the events they successfully received in a previous call or otherwise, the same events will be sent again and again, until confirmed.
Please read the documentation available for every method.
Get events
Method: post
Path: /crmUI/svcRest/routing/11.13.18.02/events
Get full agents status
Method: get
Path: /crmUI/svcRest/routing/11.13.18.02/fullAgentsStatus
Propose agents for work
Method: post
Path: /crmUI/svcRest/routing/11.13.18.02/proposeAgents
Register partner
Method: post
Path: /crmUI/svcRest/routing/11.13.18.02/register