---
title: "Create an Inbound transfer"
method: POST
path: "/v1/inbound_transfers"
tags: ["inboundTransfers"]
---

# Create an Inbound transfer

`POST /v1/inbound_transfers`

Create an inbound transfer to fund your financial account
from an externally linked bank account.
In Production, this requires that an external bank account has been setup
and verified for your account through the Chariot Dashboard.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `amount` number, required — The amount of the transfer in cents. This amount must be positive.
  - `account_id` string, required — The identifier of the financial account that will receive the transfer.
  - `description` string — An arbitrary string attached to the object. Often useful for displaying to users.

## Response `201`

The inbound transfer was created

- InboundTransfer — An inbound transfer represents a transfer of funds from an external bank account to a financial account.
  - `id` string, required — The unique identifier for the inbound transfer
  - `amount` integer, required — The amount of the inbound transfer in minor currency units (cents). This amount must be positive.
  - `description` string — An arbitrary string attached to the object. Often useful for displaying to users.
  - `status` 'pending' | 'completed' | 'canceled' | 'failed' — The status of the inbound transfer. An Inbound Transfer is `pending` if it created and the funds haven't been received yet. The status changes to `completed` when the funds have been received and the balance of the financial account has been updated. The status changes to `canceled` if the transfer is canceled. The status changes to `failed` if the transfer fails.
  - `created_at` string, date-time, required — The date and time the inbound transfer was created
  - `updated_at` string, date-time — The date and time the inbound transfer was last updated

## Other responses

- `400` — The request is invalid or contains invalid parameters
- `401` — Unauthorized. The request is missing the security (OAuth2 Bearer token) requirements and the server is unable to verify the identify of the caller.
- `403` — Access denied
- `409` — Resource Conflicts
- `500` — Internal Server Error

---

[API](https://skmtc.net/chariot-giving/apis/chariot-api-4.md) · [All operations](https://skmtc.net/chariot-giving/apis/chariot-api-4/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/chariot-giving/chariot-api-4/versions/c194d399d515/schema)