live key] --> B[Copy one message
into your AI] B --> C[Open a secure link
and choose your bank] C --> D[See transactions
in your software] ``` ## 1. Get your live key Do these steps in order. If you have already completed a step, move to the next one. Click or tap any screenshot to enlarge it.
KEEP USING THIS SAME CHAT
Keep all your replies here so the AI remembers your setup. It will ask for one thing at a time and explain where to find it. If you do not know an answer, say so. When it asks for your key, follow its instructions for saving it privately in your app. Never share your bank password in the chat.KEEP USING THIS SAME CHAT
Describe what happened and paste the message below into the chat you used above. Let the AI check its work. If that conversation is gone, start a new one. Paste the setup message from [section 2](#2-connect-your-bank-with-ai), explain that your app is already built, and ask it to inspect the existing setup before changing anything. Then paste the message below. ```markdown fix-my-connection.md theme={null} Check your own code against this list, one line at a time, and fix anything that does not match. - The API host is https://api.ledgersyncappv2.com/v3, with my live key stored only on the server. Never print the key or signing secret. - The live update receiver is reachable over HTTPS and its subscription points to that address. - Every connection id you saved looks like con_SOURCE_NUMBER, never con_ followed by a plain uuid. - client_id is on every accounts, transactions and statements request. - You branch on error.code, not on the HTTP status or the message text. - The webhook signature is built from timestamp + "." + the raw body, not the body on its own, and you reject timestamps over 5 minutes old. - Every POST carries an Idempotency-Key, and a retry of that request reuses the same value instead of generating a new one. - download_url is joined to the API host, not the /v3 URL, and sent with my key. - Nothing looks up a Client by external_id or metadata, because both come back empty. It uses the cli_ id. Tell me in plain words what you changed. ``` Still stuck? Email [support@ledgersync.com](mailto:support@ledgersync.com) with what you were doing and we will help. Do not include your key or bank password. *** Building this by hand instead? The [Quickstart](/guides/quickstart) covers the developer steps. # Check images Source: https://docs.ledgersyncappv2.com/guides/checks List an account's paper checks and download their images. When a bank exposes scanned images of the paper checks written against an account, LedgerSync captures them and serves them alongside that account's transactions. Checks hang off an **account**, so every route below is nested under one: ``` GET /v3/accounts/{account_id}/checks # list GET /v3/accounts/{account_id}/checks/{check_id} # one check GET /v3/accounts/{account_id}/checks/{check_id}/download # the image bytes ```cli_9f2a4c1b...] --> B[Connection
con_FINICITY_41294] B --> C[Account
acc_FINICITY_...] C --> D[Transactions
txn_FINICITY_...] C --> E[Statements] ``` Two things to internalize now, because they save debugging later: * **You never see bank credentials.** The user types them into a LedgerSync-hosted widget. You just open a URL. * **The data source is chosen for you.** LedgerSync routes each institution to Finicity, MX, or FDE server-side. There is no `source` parameter — the id you pass (`ins_...`) already encodes everything.
cli_...] --> B[Connection
con_...] B --> C[Account
acc_...] C --> D[Transaction
txn_...] C --> E[Statement] ``` | Object | What it is | | - | - | | **Client** | Your record of one end-user. You set `external_id`; our id looks like `cli_01HXYZ...`. | | **Connection** | One linked bank for a Client. A Client can have many. Aggregator sources only — uploaded-statement (`PDF`) data has no Connection. | | **Account** | A checking, savings, card, or loan account. Exposed by a Connection, or — for uploaded-statement (`PDF`) data — directly under the Client with `connection_id: null`. | | **Transaction / Statement** | The actual data on an Account. (Statements aren't served for `PDF` accounts.) |