...

1. Agents

1. Get a List of Agents;
2. Get information about a particular Agent.

2. Inbound calls

Upon an incoming call, Webitel sends an HTTP request to the Customer's web service, where the GET request (parameter cid-CallerID Number) contains the client's number if defined. In response, we receive JSON with the parameters necessary for routing:

...

• event - information about the event:
  • offering - distribution per Agent, 
  • bridged - Agent answer;
• direction - direction of the call: 
  
  • inbound - incoming, 
  • outbound - outgoing or dialer call; 
• queue - identifier of the incoming Queue or dialer;
• member - subscriber identifier ( needed for postprocessing);
• attempt - identifier of the dialer's dialing attempt (required for postprocessing);
• uuid - call identifier;
• agent - identifier of the Agent or his extension number (need to agree on the format);
• cid - client's telephone number.

3. Outgoing call

To make an outgoing call from the Customer's system, the Agent must have a registered SIP phone (software or hardware) and a token to fulfill requests.

...

{
	"destination": "Destination number", // required
		"from": {
		"extension": "Extensions" // required
	},
	"params": {
		"audio": true,
		"auto_answer": true,
		"record": true,
		"variables": {
			"additionalProp1": "string", // Additional variables for the client can be used for statistics and outgoing call routing.
			"additionalProp2": "string",
			"additionalProp3": "string"
		}
	}
}

4. Dialer

4.1. Download Members to the Dialer

Lists of Members are loaded into each Dialer separately.

To download Members to the Dialer, you must have the identifier of the Dialer and the administrator's token key.

POST request examples:

• Add only one Member: https://swagger.webitel.com/#/MemberService/CreateMember
• Add an array of Members: https://swagger.webitel.com/#/MemberService/CreateMemberBulk

To load Members into the Dialer concerning a particular Agent, you must use the Bucket. A Bucket is created for each Agent for which a Member must be bound. Thus, when downloading a Member, the Bucket of the responsible Agent is indicated. To do this, use the POST request block: