> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slash.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Slash API overview

> Automate financial workflows across your Slash workspace.

The Slash API gives you programmatic access to the financial and operational
workflows in your workspace.

<CardGroup cols={2}>
  <Card title="Accounts and balances">
    Discover financial products, balances, and virtual accounts.
  </Card>

  <Card title="Cards and spend">
    Manage cards, spending controls, authorizations, and card activity.
  </Card>

  <Card title="Money movement">
    Create transfers, manage recipients, and follow payment lifecycles.
  </Card>

  <Card title="Operations">
    Automate invoices, expenses, approvals, and other back-office workflows.
  </Card>

  <Card title="Accounting and reconciliation">
    Read transaction activity and connect financial events to your accounting
    systems.
  </Card>

  <Card title="Webhooks">
    React to resource changes without polling every endpoint.
  </Card>
</CardGroup>

Treat the API Reference as the contract for request fields, response objects,
and supported actions.

## Request basics

Every request uses `https://api.slash.com`, an `X-API-Key` header carrying a
[user API key](/docs/v2/get-started/authentication), and an `x-legal-entity`
header naming the legal entity to act on.

JSON fields and query parameters use camelCase. Standard HTTP headers retain
their documented hyphenated names.

Resource ids are opaque. Store them and pass them back unchanged rather than
inferring behavior from their prefixes.

## Build a reliable integration

* Use [idempotency keys](/docs/v2/get-started/idempotency) for writes that
  require them.
* Follow [cursor pagination](/docs/v2/get-started/pagination) until
  `nextCursor` is absent.
* Branch on documented [error codes](/docs/v2/get-started/errors), not message
  text.
* Consume [webhooks](/docs/v2/webhooks/overview) and retrieve current resource
  state after receiving an event.

Start with the [quickstart](/docs/v2/get-started/quickstart), then use the
concept and workflow guides for the part of the product you are integrating.