> For the complete documentation index, see [llms.txt](https://legacy-docs.usesmileid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy-docs.usesmileid.com/getting-started/run-your-first-test-job.md).

# Run Your First Test Job

Now that you have selected a product and your integration method, follow this step-by-step guide to run your first Smile ID job in the Sandbox environment:

* Generate a signature.
* [Create a callback endpoint](/further-reading/faqs/how-do-i-setup-a-callback.md) (for asynchronous API use).
* Write your integration code.
* Test your integration in the Sandbox environment.

## Generate Your Signature

Signatures ensure that it's your system initiating a request to ours and verify your authorization to execute a job. The simplest way to generate your signature is by using one of our [server-side libraries](/integration-options/server-to-server.md). Alternatively, you can follow the detailed instructions on the [using signature](/integration-options/rest-api/signing-your-api-request.md) page under the REST API section of our documentation. You will need your API Key and Partner ID, available in the developer section of [the portal](https://portal.usesmileid.com/security-settings).

Confirm that you are in the right environment (`Sandbox` or `Production`) by toggling to the desired environment.

![Environment toggle button](/files/ldbRHZt1Fqk5GqGoFPoI)

## Create a Callback Endpoint

If you're using a Smile ID product that provides asynchronous responses, you'll need to set up a callback API to receive these responses. Learn more about setting up a callback in our [FAQs](/further-reading/faqs/how-do-i-setup-a-callback.md).

## Write Your Integration Code

Depending on your chosen Smile ID [product](/getting-started/choose-a-product.md) and [integration option](/getting-started/choose-an-integration-option.md), refer to the relevant documentation to guide you in writing your integration code.

## Test Your Integration in the Sandbox Environment

All job responses during your testing phase will be displayed in the job list within the partner portal. Use this list to verify that the results of your test jobs meet your expectations.

![Partner account job list page](/files/IWe5juBrtQWi5d26wiF9)

{% hint style="info" %}
Testing with "real" ID numbers is not permitted until you [complete your KYC](/getting-started/complete-your-kyc.md) and transition to the [production environment](/getting-started/go-live.md). For products requiring ID information, a list of sample IDs for all our supported ID Types is available [here](/supported-id-types/for-individuals-kyc/backed-by-id-authority/test-data.md).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://legacy-docs.usesmileid.com/getting-started/run-your-first-test-job.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.