Quickstart

This walkthrough sends a standard ACH payment to a new recipient.

Create a user API key

Public API v2 only accepts user API keys. In the Slash dashboard, open Settings → API keys and choose Create API key. The secret is shown once; store it on your server. The key acts as you, so before starting make sure your user has:

access to the target legal entity
access to view accounts, manage recipients, and initiate ACH transfers
a request IP on the legal entity’s enabled IP allowlist

Keys created under a legal entity’s API management page are not accepted by v2 and return 403 user_api_key_required. See Authentication for details. Set these values in your shell:

export SLASH_API_KEY="..."
export SLASH_LEGAL_ENTITY_ID="le_..."

Choose the source balance

List Accounts, then list the virtual accounts in the Account you want to debit:

curl "https://api.slash.com/v2/accounts" \
  -H "X-API-Key: ${SLASH_API_KEY}" \
  -H "x-legal-entity: ${SLASH_LEGAL_ENTITY_ID}"

curl --get "https://api.slash.com/v2/virtual-accounts" \
  -H "X-API-Key: ${SLASH_API_KEY}" \
  -H "x-legal-entity: ${SLASH_LEGAL_ENTITY_ID}" \
  --data-urlencode "accountId=sa_group_..."

Save the selected subaccount_... id as fromAccount.

Create the recipient

A recipient is who you pay. It does not hold bank instructions.

curl "https://api.slash.com/v2/recipients" \
  -X POST \
  -H "X-API-Key: ${SLASH_API_KEY}" \
  -H "x-legal-entity: ${SLASH_LEGAL_ENTITY_ID}" \
  -H "X-Idempotency-Key: vendor-1042" \
  -H "Content-Type: application/json" \
  --data '{
    "name": "Acme Supplies",
    "recipientType": "vendor",
    "recipientLegalName": "Acme Supplies LLC",
    "recipientEmail": "payments@example.com"
  }'

Save the returned le_c_... id.

Save the bank destination

Create a US bank-account destination for the recipient:

curl "https://api.slash.com/v2/destinations" \
  -X POST \
  -H "X-API-Key: ${SLASH_API_KEY}" \
  -H "x-legal-entity: ${SLASH_LEGAL_ENTITY_ID}" \
  -H "X-Idempotency-Key: destination-vendor-1042" \
  -H "Content-Type: application/json" \
  --data '{
    "recipientId": "le_c_...",
    "type": "bank_account",
    "name": "Operating account",
    "accountNumber": "123456789",
    "routingNumber": "021000021",
    "accountType": "checking",
    "beneficiary": {
      "name": "Acme Supplies LLC",
      "address": {
        "line1": "1 Market Street",
        "city": "New York",
        "state": "NY",
        "postalCode": "10005",
        "countryCode": "US"
      }
    }
  }'

Save the returned destination id.

Create the ACH transfer

curl "https://api.slash.com/v2/transfers/ach" \
  -X POST \
  -H "X-API-Key: ${SLASH_API_KEY}" \
  -H "x-legal-entity: ${SLASH_LEGAL_ENTITY_ID}" \
  -H "X-Idempotency-Key: invoice-1042-attempt-1" \
  -H "Content-Type: application/json" \
  --data '{
    "amount": {
      "amount": 1250,
      "currency": "USD"
    },
    "fromAccount": "subaccount_...",
    "destinationId": "le_contact_destination_...",
    "description": "Invoice 1042",
    "ach": {
      "speed": "standard"
    }
  }'

The response is an ACH Transfer. Save its transfer_intent_... id.

Follow the transfer

Retrieve the Transfer to follow its lifecycle:

curl "https://api.slash.com/v2/transfers/ach/transfer_intent_..." \
  -H "X-API-Key: ${SLASH_API_KEY}" \
  -H "x-legal-entity: ${SLASH_LEGAL_ENTITY_ID}"

Read the ACH lifecycle before deciding which statuses are final.

Reconcile account activity

List every Transaction associated with the Transfer:

curl --get "https://api.slash.com/v2/transactions" \
  -H "X-API-Key: ${SLASH_API_KEY}" \
  -H "x-legal-entity: ${SLASH_LEGAL_ENTITY_ID}" \
  --data-urlencode "transferId=transfer_intent_..."

Transaction responses use camelCase. Their signed amountCents values describe each account impact.

Get started

Working with the API

Core objects

Money movement

Cards

Bill pay

Invoicing

Accounting

Create a user API key

​Create a user API key

Create a user API key