> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/interface-options/api/representational-state-transfer-rest-api/rest-api-creating-the-client-certificate.md).

# REST API - creating the client certificate

Create and assign a client certificate for REST API authentication.

The client certificate lets Command Centre trust the caller. Create it on the PC that will connect to the REST API.

> ⚠️ On Windows, use PowerShell. `New-SelfSignedCertificate` is **not available on Windows 7**.

## Steps

1. Run **PowerShell** as Administrator.
2. Create the certificate:

   ```powershell
   New-SelfSignedCertificate -certstorelocation cert:\currentuser\my -dnsname GallagherRestClientCert
   ```

   This creates the certificate in **Current User → Personal → Certificates**.
3. Copy the **Thumbprint** from the certificate's **Details** tab, then paste it into the **Client Certificate Thumbprint** field of the REST Client (API Key tab).
4. Add **Network Service** permission to the certificate.

***

🔗 **Related**

* [REST API - Certificates](/knowledge-hub/products/cc-software/configure/interface-options/api/representational-state-transfer-rest-api/rest-api-certificates.md). How client and server trust fit together.
* [REST API - Setting up REST API in Command Center](/knowledge-hub/products/cc-software/configure/interface-options/api/representational-state-transfer-rest-api/rest-api-setting-up-rest-api-in-command-center.md). Where the thumbprint is pinned.


---

# 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://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/interface-options/api/representational-state-transfer-rest-api/rest-api-creating-the-client-certificate.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.
