---
title: "Create a test Item and processor token"
method: POST
path: "/sandbox/processor_token/create"
tags: ["plaid"]
---

# Create a test Item and processor token

`POST /sandbox/processor_token/create`

Use the `/sandbox/processor_token/create` endpoint to create a valid `processor_token` for an arbitrary institution ID and test credentials. The created `processor_token` corresponds to a new Sandbox Item. You can then use this `processor_token` with the `/processor/` API endpoints in Sandbox. You can also use `/sandbox/processor_token/create` with the [`user_custom` test username](https://plaid.com/docs/sandbox/user-custom) to generate a test account with custom data.

## Request body

- SandboxProcessorTokenCreateRequest — SandboxProcessorTokenCreateRequest defines the request schema for `/sandbox/processor_token/create`
  - `client_id` string — Your Plaid API `client_id`. The `client_id` is required and may be provided either in the `PLAID-CLIENT-ID` header or as part of a request body.
  - `secret` string — Your Plaid API `secret`. The `secret` is required and may be provided either in the `PLAID-SECRET` header or as part of a request body.
  - `institution_id` string, required — The ID of the institution the Item will be associated with
  - `options` SandboxProcessorTokenCreateRequestOptions — An optional set of options to be used when configuring the Item. If specified, must not be `null`.
    - `override_username` string, nullable — Test username to use for the creation of the Sandbox Item. Default value is `user_good`. You can also use a custom test user — either set this to the username of a custom user configured in the Dashboard, or set it to `user_custom` and pass the JSON-stringified custom user configuration object as `override_password` to define one entirely via API. See [Sandbox Custom Users](https://plaid.com/docs/sandbox/user-custom) for more details.
    - `override_password` string, nullable — Test password to use for the creation of the Sandbox Item. Default value is `pass_good`. You can also use a custom test user — reference one configured in the Dashboard via `override_username`, or set `override_username` to `user_custom` and pass the JSON-stringified custom user configuration object as this field to define one entirely via API. See [Sandbox Custom Users](https://plaid.com/docs/sandbox/user-custom) for more details.

## Response `200`

OK

- SandboxProcessorTokenCreateResponse — SandboxProcessorTokenCreateResponse defines the response schema for `/sandbox/processor_token/create`
  - `processor_token` string, required — A processor token that can be used to call the `/processor/` endpoints.
  - `request_id` string, required — A unique identifier for the request, which can be used for troubleshooting. This identifier, like all Plaid identifiers, is case sensitive.

## Other responses

- `default` — Error response.

---

[API](https://skmtc.net/plaid/apis/the-plaid-api.md) · [All operations](https://skmtc.net/plaid/apis/the-plaid-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/plaid/the-plaid-api/revisions/64c4514ea59b/schema)