Enter the websocket url of Qlik Sense Engine JSON API. Refer to [this](https://help.qlik.com/en-US/sense-developer/May2023/Subsystems/EngineAPI/Content/Sense_EngineAPI/GettingStarted/connecting-to-engine-api.htm) document for more details about
Example: `wss://server.domain.com:4747` or `wss://server.domain.com[/virtual proxy]`
**Note:** Notice that you have to provide the websocket url here which would begin with either `wss://` or `ws://`
{% /codeInfo %}
{% codeInfo srNumber=2 %}
**displayUrl**: Qlik Sense Base URL
This field refers to the base url of your Qlik Sense Portal, will be used for generating the redirect links for dashboards and charts.
Example: `https://server.domain.com` or `https://server.domain.com/<virtual-proxy-path>`
{% /codeInfo %}
{% codeInfo srNumber=3 %}
Since we use the Qlik Sense Engine APIs, we need to authenticate to those APIs using certificates generated on Qlik Management Console.
In this approach we provide the path of the certificates to the certificate stored in the container or environment running the ingestion workflow.
- **clientCertificate**: This field specifies the path of `client.pem` certificate required for authentication.
- **clientKeyCertificate**: This field specifies the path of `client_key.pem` certificate required for authentication.
- **rootCertificate**: This field specifies the path of `root.pem` certificate required for authentication.
{% /codeInfo %}
{% codeInfo srNumber=4 %}
In this approach we provide the content of the certificates to the relevant field.
- **Client Certificate Value**: This field specifies the value of `client.pem` certificate required for authentication.
- **Client Key Certificate Value**: This field specifies the value of `client_key.pem` certificate required for authentication.
- **Root Certificate Value**: This field specifies the value of `root.pem` certificate required for authentication.
- **Staging Directory Path**: This field specifies the path to temporary staging directory, where the certificates will be stored temporarily during the ingestion process, which will de deleted once the ingestion job is over.
when you are using this approach make sure you are passing the key in a correct format. If your certificate looks like this:
```
-----BEGIN CERTIFICATE-----
MII..
MBQ...
CgU..
8Lt..
...
h+4=
-----END CERTIFICATE-----
```
You will have to replace new lines with `\n` and the final private key that you need to pass should look like this: