This allows using an OAuth2 or a search token to authenticate against the Search API.
Specifies that the request (and the Coveo Search API) does not need any kind of authentication.
This flag is only needed for specific setups when your requests are being blocked by your browser. If your queries are executing correctly, you do not need to bother.
Setting this flag will prevent the withCredentials option to be set on the XMLHttpRequest, allowing performing cross-domain requests on a server that returns * in the Access-Control-Allow-Origin HTTP header.
This is the password part of the credentials used to authenticate with the REST API.
This option should only be used for development purposes. Including secret credentials in an HTML page that is sent to a client browser is not secure.
Query string arguments to add to every request to the search endpoint.
eg : {'foo':'bar', 'a':'b'}
Specifies a function that, when called, will arrange for a new search token to be generated.
It is expected to return a Promise that should be resolved with the new token once it's available.
A function which will allow external code to modify all endpoint call parameters before they are sent by the browser.
Used in very specific scenario where the network infrastructure require special request headers to be added or removed, for example.
The uri for the search endpoint. eg: cloudplatform.coveo.com/rest/search
The uri for the Coveo search alerts service. If not specified, will automatically resolve using the restUri otherwise
This is the username part of the credentials used to authenticate with the Search API using Basic Authentication.
This option should only be used for development purposes. Including secret credentials in an HTML page that is sent to a client browser is not secure.
The XmlHttpRequest implementation to use instead of the native one. If not specified, the native one is used.
The possible options when creating a SearchEndpoint