McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 191

↗ View in doc context
page
191
source
finesse/v12.5/developer-guide/developer-guide.md
chunk_id
finesse::v12.5::developer-guide::developer-guide::175

Asynchronous Errors If an error occurs after the initial validation is complete, an error notification is sent over XMPP to the Media notification. The requestId is included in the response XML. The ErrorMedia parameter in the ApiError information indicates the Media Routing Domain to which the error applies. Media—Get Media This API allows a user to get a copy of a Media object for a specified agent. This API can be used to return only nonvoice Media objects. https://<FQDN>/finesse/api/User/<id>/Media/<mrdId> URI: https://finesse1.xyz.com/finesse/api/User/1234/Media/5001 Example URI: Users can only act on their own Media objects. Security Constraints: GET HTTP Method: — Content Type: XML Input/Output Format: — HTTP Request: id (required): The ID of the user mrdId (required): The ID of the Media Routing Domain Request Parameters: 200: Success 400: Bad Request (for example, malformed or incomplete request) 400: Parameter Missing 401: Unauthorized (for example, the user is not authenticated in the Web Session) 404: Not Found (for example, the user ID or mrdId is not known) HTTP Response: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 175 Cisco Finesse Desktop APIs Media—Get Media