# API (/docs/guides/destinations/api)



# API [#api]

The Lunch Flow API lets you build custom integrations, dashboards, and automations using your bank transaction data.

## Getting started [#getting-started]

Full API documentation including authentication, endpoints, and code examples is available in the [API Reference](/docs/api/what-is-lunch-flow).

## Setup [#setup]

. Go to **Destinations → Add Destination → API**
. Copy your generated API key
. Use the key in the `x-api-key` header for all requests

## Account access control [#account-access-control]

The API destination includes an **Account Access** settings tab where you can selectively enable or disable which connected accounts are exposed through the API.

<Callout type="info">
  If accounts don't appear in API responses, check the Account Access settings - individual account toggles control their visibility.
</Callout>

## FAQ [#faq]

<Accordions>
  <Accordion title="Can I filter by date range?">
    Date range filtering is not yet available - this is an open feature request you can upvote. API requests return all accessible transactions (up to 90 days for GoCardless connections).
  </Accordion>

  <Accordion title="Can I use Lunch Flow as an open banking provider?">
    Yes - Lunch Flow offers a Platform API for building applications that access financial data on behalf of your users. See the [Platform API docs](/docs/api/platform-api-overview).
  </Accordion>
</Accordions>