> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://www.truework.com/docs/guides/api/getting-started/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://www.truework.com/_mcp/server.

# Make your first Target Employer Order

**Truework's Target Employer Order API enables you to seamlessly integrate robust verification capabilities directly into your application**. In this guide, we'll explore how to use the [Truework Sandbox](/docs/api-reference/sandbox)—a risk-free playground where you can test your integration without touching production data. Get ready to dive in and make your first request with ease!

## Prerequisites

- Set up a [Truework account](https://app.truework.com/requester/signup)
- Generate a Sandbox API Key and [webhook token](https://www.truework.com/docs/api-reference/webhooks) under [developer settings](https://app.truework.com/requester/developer-settings) from your Truework account
- Note the base URL for the Truework Sandbox is `https://api.truework-sandbox.com`

## Creating an order

To create a verification request from your backend application, make a POST request to [`/orders/target-employer`](https://www.truework.com/docs/babbe02b35017-create-a-target-employer-order) using a tool like curl, Postman, or via our built-in [API Explorer](/docs/api-reference/versions/2023-10-30/create-new-target-employer-verification?explorer=true). Making this POST request creates an order that will contain a single verification for the requested employer.

The `/orders/target-employer` endpoint processes your order _asynchronously_. Although you will receive a response instantly, there will be no reports associated with the verification on the order. You will need to retrieve the report(s) once the order is completed, which is detailed in the next section.

<Tabs>
    <Tab title="Request">
        <EndpointRequestSnippet endpoint="POST /orders/target-employer" />
    </Tab>
    <Tab title="Response">
        <EndpointResponseSnippet endpoint="POST /orders/target-employer" />
    </Tab>
</Tabs>

Once created, copy the string returned in the `id` field—we'll need it for the next step.

## Listening for webhooks

Truework uses [webhooks](/docs/api-reference/webhooks) to _asynchronously_ update our partners when a verification is completed. Webhooks are configured under [developer settings](https://app.truework.com/requester/developer-settings) in the Truework app.

There are two types of webhooks: **order completed** and **verification state change**.

Of interest will mostly be the states `completed` and `canceled`:

- A `completed` state indicates that new data is now available on the order
- A `canceled` state indicates that a verification was not able to be completed, but may have user-provided information and/or documents

### Order completed webhook

The `order.completed` webhook will be issued when all employer verifications associated with the order have been `completed` or `canceled`. Once you receive this webhook, you can fetch the order results.

``` json
{
  "hook": {
    "id": 50,
    "event": "order.completed",
    "target": "https://example.com/webhook"
  },
  "data": {
    "order_id": "AAAAAAAAAosABwGqF1AUKAH0-puth1tCzLNar3Jyb4bx3wdVKU99XC26",
  }
}
```

## Getting an order

Now that you've created an order and copied its ID, we can get it from the API to see its current state and other data. To do so, we will need to make an HTTP GET request to the `/orders/{order_id}` endpoint.

<Tabs>
    <Tab title="Request">
        <EndpointRequestSnippet endpoint="GET /orders/{order_id}" />
    </Tab>
    <Tab title="Response">
        <EndpointResponseSnippet endpoint="GET /orders/{order_id}" />
    </Tab>
</Tabs>

After retrieving your order, you should observe the following:

- The `verification_requests` list in the order includes one verification with a `completed` state
- The `reports` field of the verification contains a Verification of Employment and Income (VOIE) report
- If you set up a webhook logger, you should see that the `order.completed` webhook has been triggered

These actions occurred because a special SSN value (`000-00-0000`) was used in the sandbox environment, which automatically processed and completed the verification. You can learn more about the SSNs available for use in the sandbox [here](/docs/api-reference/sandbox/test-cases).

## Moving to production

<Info>A general API service account is recommended to manage the integration (e.g. truework@yourcompany.com).</Info>

When your integration is complete (or nearing completion), follow the steps below:

- Generate your production API Key and webhook token under [developer settings](https://app.truework.com/requester/developer-settings) from your Truework account
- Change the base URL for all backend API calls to Truework from https://api.truework-sandbox.com to https://api.truework.com
- Notify implementations@truework.com you are ready to move to production at least three (3) days prior to the target go live date

## Questions?

Not a problem, we are here to help! Send your questions to implementations@truework.com.