Evo Voice

ListAutoCompleteValues

The following routes are available for this service:
All Verbs	/ui/autocomplete/values

**ListAutoCompleteValues** Parameters:
Name	Parameter	Data Type	Required	Description
AccountId	query	string	No	Account ID
CustomerId	query	string	No	Filter by customer ID
Type	query	ValueTypes	No	The type of value
Query	query	string	No	The query text to search for
TypeSpecificFilter	query	string	No	Type specific filter
Value	query	string	No	The value to search for (will only return one result)
PlainText	query	bool	No	Should the results be sent back in plain text or with embedded HTML?
FullInfo	query	bool	No	Include full info?
All	query	bool	No	List all values, only use for small lists.

**ValueTypes** Enum:
NotSpecified
String
Boolean
Number
List
Struct
Transition
Custom
Date
AudioFile
TimeZoneId
PhoneNumber
User
Endpoint
Time
File
FaxNumber
EmailAccount
Customer
Flow
Team
FlowReference
Integration

**ListAutoCompleteValuesResponse** Parameters:
Name	Parameter	Data Type	Required	Description
Values	form	List<AutoCompleteValue>	No

**AutoCompleteValue** Parameters:
Name	Parameter	Data Type	Required	Description
DisplayName	form	string	No	Display name
Value	form	string	No	Value

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /ui/autocomplete/values HTTP/1.1 
Host: evovoice.io 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"accountId":"String","customerId":"String","type":"NotSpecified","query":"String","typeSpecificFilter":"String","value":"String","plainText":false,"fullInfo":false,"all":false}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"values":[{"displayName":"String","value":"String"}]}