> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/uwp/learn-more/add-license.md).

# Add license key

Ready to get a production license for your application? Learn how to purchase a license key and properly use it to avoid watermarked demo/trial mode. Contact sales now for more information! The Apryse

## Getting a production license

Now that you’ve built your application, and tested it in a deployment environment, you might be ready to purchase a license. Please [contact sales](https://apryse.com/form/contact-sales) in order to get a license key.

## Using the license

When you do not want to be in the watermarked demo/trial mode, it is important that you initialize Apryse library with a valid license key before using any Apryse classes.

{% hint style="info" %}
**Please be sure to initialize Apryse SDK before any calls to Apryse APIs.**
{% endhint %}

After `this.InitializeComponent()` of `App.xaml.cs` in your application, add:

{% tabs %}
{% tab title="C#" %}
{% code lineNumbers="true" %}

```csharp
pdftron.PDFNet.Initialize("Insert commercial license key here after purchase");
```

{% endcode %}
{% endtab %}
{% endtabs %}


---

# 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://docs.apryse.com/uwp/learn-more/add-license.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.