---
title: "Request recipient details"
method: POST
path: "/v2/information-requests"
---

# Request recipient details

`POST /v2/information-requests`

## Request

- Base URL: `https://api.slash.com`
- URL: `https://api.slash.com/v2/information-requests`
- Auth: API key in header `X-API-Key`

Email an existing recipient a secure form asking for any combination of payment destination details, an address, and tax details. Submitted destinations appear in `GET /v2/destinations`, the address replaces the recipient's `address`, and tax details are returned by `GET /v2/recipients/{recipientId}/tax-details`. A recipient can have at most one pending information request. Use an information request that accepts `bank_account` to create queued ACH, realtime or wire transfers while awaiting the recipient's bank details.

## Headers

- `X-Idempotency-Key` string, required

## Request body

- InformationRequestCreate: Ask a recipient to securely provide payment, address, or tax details. Crypto addresses collected through this flow are not exposed as destinations.
  - `recipientId` string, required: The recipient to ask.
  - `requestedInformation` object, required: Information the recipient may provide through the secure form.
    - `destinationTypes` string[]: Payment destination types the recipient may add. Submitted destinations appear in `GET /v2/destinations`.
    - `address` true: Ask for the recipient's address. The submitted address replaces the recipient's `address`.
    - `tax` true: Ask for the recipient's tax details: legal name, tax classification, and taxpayer identification number. Read them with `GET /v2/recipients/{recipientId}/tax-details`.
  - `requesterName` string, required: Name shown to the recipient in the request email and secure form.
  - `ccEmails` string[]
  - `note` string: Optional message shown to the recipient.

## Response `200`

Information request created and sent.

- InformationRequest: A request asking a recipient to securely provide payment, address, or tax details. A requested crypto address is collected through the recipient flow but is not exposed by the API v2 Destination collection.
  - `id` string, required: Information request id.
  - `recipientId` string, required: The recipient that received the request.
  - `status` 'pending' | 'submitted' | 'canceled', required: Current recipient response state.
  - `requestedInformation` object, required: Information the recipient may provide through the secure form.
    - `destinationTypes` string[]: Payment destination types the recipient may add.
    - `address` true: Present when the request asks for the recipient's address.
    - `tax` true: Present when the request asks for the recipient's tax details.
  - `sentToEmail` string, email, required: Email address to which Slash sent the request.
  - `ccEmails` string[], required
  - `requesterName` string, required: Name shown to the recipient in the request email and secure form.
  - `note` string
  - `sentAt` string, date-time, required
  - `firstSubmittedAt` string, date-time
  - `lastSubmittedAt` string, date-time
  - `canceledAt` string, date-time
  - `createdAt` string, date-time, required

## Other responses

- `400`: - `invalid_request (request shape)` — The body, query, or headers failed validation, or a required header is missing. `details` has one entry per failing location, keyed by JSON pointer or header name.
- `401`: - `unauthorized` — API key authentication is missing or invalid.
- `403`: - `feature_not_enabled` — The feature this request uses is not enabled for the legal entity. Contact Slash support to enable it. - `forbidden` — The credential is not permitted to perform this action on the resource. When the resource is a field of the request, `details` names that `field` and the `id` it received. - `forbidden (legal entity)` — The credential is not permitted to act for the selected legal entity. - `not_available` — Public API v2 is not yet available. Use [Public API v1](https://docs.slash.com/introduction) in the meantime. - `user_api_key_required` — The API key is scoped to a legal entity rather than a user. Every v2 request needs a user API key, created under Settings → API keys in the Slash dashboard, together with the `x-legal-entity` header.
- `404`: - `not_found` — No resource matches the identifier. When the identifier is a field of the request, `details` names that `field` and the `id` it received.
- `409`: - `information_request_already_pending` — A recipient can have one pending information request at a time; cancel the pending one first. - `recipient_email_missing` — Information requests are emailed to the recipient, and this recipient has no email address. - `conflict (idempotency key reused)` — A consumed `X-Idempotency-Key` was reused; the original response is not replayed.
- `429`: The request exceeded the applicable rate limit. The response body is plain text, not the error object; clients must not depend on its wording.
- `500`: - `internal` — Slash could not complete the request. Quote `referenceId` when contacting Slash support.

## Changes

- **2026-10-16** `8b5d371ffeea`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/slashfi/apis/slash-public-api/changes/v2/information-requests/post.md)

---

[API](https://skmtc.dev/slashfi/apis/slash-public-api.md) - [All operations](https://skmtc.dev/slashfi/apis/slash-public-api/llms.txt) - [OpenAPI document](https://skmtc.dev/slashfi/apis/slash-public-api/revisions/eaed2d63c9e2?raw)