Overview
The LedgerSync API portal operates in two environments: Sandbox and Live (Production). All new API accounts begin in Sandbox mode, which uses test keys and fake data. To use the API with real production traffic, you must request and receive approval for Live access.
Live access is not granted automatically — it requires a manual review and approval by the LedgerSync team.
Understanding the Two Environments
Sandbox
- Default environment for all new API accounts
- Uses test API keys and fake/sample data
- Safe environment for building and testing your integration
- No real bank data or production traffic
Live (Production)
- Uses real API keys and live production traffic
- Required to connect to actual bank accounts and retrieve real data
- Access must be explicitly approved by LedgerSync
How to Request Live API Access
Step 1: Log in to the LedgerSync API Portal
Go to portal.ledgersyncappv2.com and sign in with your LedgerSync credentials. By default, you will land on the Sandbox environment.
Step 2: Switch to the Live Environment
In the top-right corner of the dashboard, click the environment dropdown (shown as Sandbox). Select Live from the menu.
Step 3: Submit a Request for Access
Once switched to the Live environment, you will see the following message:
"You don't have access to the Live environment yet. Submit a request to get started."
Click the Request access button to submit your request to the LedgerSync team.
Step 4: Await Approval
The LedgerSync team will review your request. Once approved, your account will be upgraded from Sandbox to Live, and you will have access to production API keys and real bank data.
What Happens After Approval
- Your account will be granted access to the Live environment in the portal
- You can generate production API keys under API Keys in the left menu
- All API calls made with Live keys will process real bank data and production traffic
- Sandbox remains available for continued testing alongside your Live integration
Important Notes
- Do not use Sandbox keys in a production environment — they will not return real data
- Live API keys should be kept secure and never shared publicly
- If you need assistance after submitting your request, contact support@ledgersync.com
Need Help?
If you have questions about API access or the approval process, reach out to our team:
Related Articles
- Article 7: LedgerSync API
Related Articles
LedgerSync API: Authentication & API Keys
Overview Every request to the LedgerSync API must be authenticated with a secret key passed as a Bearer token. This article explains how API keys work, the difference between sandbox and live keys, and how to keep them secure. How to Authenticate ...
LedgerSync API Pricing
Overview The LedgerSync API is billed per active client, per 30-day billing cycle — the same volume-based pricing structure as the LedgerSync app. When you use the API, billing switches to the API plan. If you're already a LedgerSync customer, there ...
LedgerSync API Overview: What You Can Build
Overview The LedgerSync API gives you one uniform REST API for your users' bank data — accounts, balances, transactions, and statements — across multiple bank data sources, with no plumbing to build yourself. You link a bank account once and receive ...
LedgerSync API: Getting Started (Quickstart Guide)
Overview This guide walks you through linking your first bank account and pulling real transaction data using the LedgerSync API — from your first sandbox key to a live data response. The full flow takes about 15 minutes in sandbox. Sandbox base URL: ...
LedgerSync API — Webhooks & Transaction Deduplication (transactionHash)
Overview This article is for LedgerSync API partners. The LedgerSync API supports webhook notifications and a stable transaction hash field to help your integration handle real-time events and deduplicate transactions across bank reconnections. ...