> For the complete documentation index, see [llms.txt](https://developer.ultimo.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.ultimo.net/api-guide/rest/additional-security.md).

# Additional security

For cloud customers on Azure, additional security is available for the REST API. Without additional security measures, anyone in possession of the API key secret is able to connect to the API endpoint.

## IP filtering

It is possible to add IP address range validations per API key. Use '-' to allow everything in between and ';' to use multiple ranges. Keep in mind: this is a whitelist. All IP addresses not on the whitelist will not be able to connect.

Support for both IPv4 and IPv6 address range validation is available. When only one of them is filled, the other is completely blocked. Example: when IPv4 is filled, no one can connect with a IPv6 address.

Note: IP filtering on API keys have no relation with IP filtering options for logging on to the Ultimo application.

## Client certificates

It is possible to specify a certificate thumbprint per API key. The client connecting to the API endpoint should always send the certificate that meets the certificate thumbprint on the API key when sending a request.

When a certificate thumbprint is used on an API key, the URL of the API endpoint is different than without a client certificate. Instead of using the standard URL:

> <https://customer.ultimo.net/api/v1/>

Use the following URL:

> https\://**api-**&#x63;ustomer.ultimo.net/api/v1/

A cUrl command example of sending a request with a client certificate:

```
curl --cert C:\temp\client.crt --key c:\temp\client.key -X GET "https://api-customer.ultimo.net/api/v1/object/Article" -H "accept: application/json" -H "ApiKey: [ApiKey]"
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.ultimo.net/api-guide/rest/additional-security.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.