# LEAP Legal Software — API Integration Research

**Date:** 28 April 2026
**Prepared by:** BossLawyerAI
**For:** Boss Lawyers Pty Ltd (Mark Harley, Principal Solicitor)

---

## Executive Summary

LEAP has a **public REST API** available through its Developer Console and API Gateway. It is designed for third-party developers to build apps that integrate with LEAP across desktop, web, and mobile. The API covers matters, contacts, fees/time entries, documents, and schema endpoints. Authentication uses **OAuth 2.0**. LEAP also supports **webhooks** for real-time event notifications (e.g., new matter created, document added). A **Zapier integration** (launched November 2025) provides a no-code route for basic automations. Building a custom BossLawyerAI integration is feasible but requires registering as a LEAP developer and building through their app submission process.

---

## 1. API Availability & Documentation

### 1.1 LEAP Developer Programme

| Item | Detail |
|------|--------|
| **Developer Portal** | https://developer.leap.build/ |
| **Developer Console** | https://console.leap.build/ (register/sign in) |
| **API Reference** | https://leap.build/api-reference/ (requires authentication to view full docs) |
| **API Gateway** | REST API gateway — endpoints accessible after credential provisioning |
| **Marketplace** | https://marketplace.leap.build/ (AU: /en-AU/apps) |
| **Design System** | https://galaxy.leap.build (Galaxy Design System for UI integration) |
| **System Status** | https://status.leaplegalsoftware.com/ |
| **Community** | https://community.leap.com.au/s/ (AU) |

### 1.2 API Type

- **REST API** with JSON responses
- Consistent resource schemas and pagination across modules
- API Gateway architecture (centralised gateway managing access to multiple underlying services)

### 1.3 Authentication

- **OAuth 2.0** — Authorization Code Flow
- Sandbox credentials issued via Developer Console
- Live credentials require app submission and approval by LEAP
- Scoped tokens — permissions managed per-app, per-endpoint
- To add API endpoints to Live credentials, they must first be tested in Sandbox and submitted via App Submission

### 1.4 Available API Domains (Confirmed from Search/Documentation Snippets)

Based on search results, release notes, schema endpoints, and Zapier integration actions:

| Domain | Read | Write | Notes |
|--------|------|-------|-------|
| **Matters** | ✅ | ✅ | Create matters ("cards"), read matter details, update |
| **Contacts/Clients** | ✅ | ✅ | Individuals and organisations |
| **Fees/Time Entries** | ✅ | ✅ | Create fees via API; confirmed by Zapier "Create fees" action |
| **Documents** | ✅ | Likely ✅ | Document metadata; filing to matters |
| **Schema/Layouts** | ✅ | — | Schema endpoints for structural data & layouts of matter types |
| **Calendar/Tasks** | Likely ✅ | Unknown | Tasks, reminders, court dates — core LEAP features |
| **Billing/Invoices** | Likely ✅ | Unknown | Pre-bills, invoices, AR — core features |
| **Trust Accounting** | Likely ✅ | Unknown | Trust ledger — core feature |
| **Users/Permissions** | Likely ✅ | — | Attorneys, paralegals, billing roles |

**Note:** The full API reference is behind authentication at https://leap.build/api-reference/. The exact endpoint list requires registering as a developer and accessing the console.

### 1.5 Webhooks

- **Confirmed available** in the LEAP API
- Can trigger on events such as:
  - Creating a new matter
  - Updating a matter
  - Adding a document
- Enables real-time event-driven integration (no polling required)

### 1.6 Zapier Integration (No-Code Option)

Launched November 2025. Confirmed actions on Zapier:

| Type | Action |
|------|--------|
| **Action** | Create cards (matters) in LEAP |
| **Action** | Create fees in LEAP |
| **Trigger** | Various triggers from LEAP events |

This confirms the API supports at minimum: matter creation and fee/time entry creation programmatically.

### 1.7 Rate Limits

- Not publicly documented
- Described as "tuned for firm-grade throughput" (per Supergood)
- Likely subject to fair-use limits; specifics available after developer registration

### 1.8 API Access Costs

The LEAP Marketplace Developer Terms reference:
- **Developer Console and API Access Fee** — a $ amount (ex. GST)
- **Marketplace Revenue Share Fee** — if distributing via marketplace
- **API Application fees** — likely per-app

Exact amounts not publicly listed — need to register and review terms. For an internal-use integration (not distributed via marketplace), the access fee may be minimal or waived. This needs direct enquiry with LEAP.

---

## 2. What We Want to Build — Feasibility Assessment

### 2a. TIME ENTRIES: Push Billing Narratives to LEAP ✅ HIGH CONFIDENCE

**Feasibility: Achievable**

- Zapier confirms "Create fees in LEAP" is a supported action — meaning the API accepts fee/time entry creation
- Required fields likely: matter ID, date, units/duration, narrative text, fee earner, rate
- BossLawyerAI already generates QLD costs-assessment-compliant narratives with all required fields
- **Integration flow:** BossLawyerAI generates narrative → API call pushes each entry to correct matter in LEAP

### 2b. DOCUMENT MANAGEMENT: Pull/Push Documents ✅ MEDIUM-HIGH CONFIDENCE

**Feasibility: Likely achievable**

- LEAP API includes document metadata endpoints
- Webhooks can trigger on document addition
- Pull: Retrieve documents from LEAP DMS when matter opened or document added
- Push: Upload completed pleadings back to LEAP DMS, filed to correct matter
- **Key question:** Whether document *content* (file binary) is accessible via API or only metadata — needs verification in API reference

### 2c. MATTER SYNC: Two-Way Matter Synchronisation ✅ HIGH CONFIDENCE

**Feasibility: Achievable**

- Matter creation confirmed via API (Zapier "Create cards")
- Matter read/update likely available
- Schema endpoints provide structural data for matter types
- Webhooks trigger on matter create/update — enables LEAP → BossLawyerAI sync
- **Integration flow:**
  - New matter in LEAP → webhook fires → BossLawyerAI creates workspace
  - BossLawyerAI can read matter details (parties, court, dates) from LEAP

### 2d. CONTACT SYNC: Party & Contact Details ✅ HIGH CONFIDENCE

**Feasibility: Achievable**

- Contacts/Clients confirmed as core API domain
- Read: Pull client, other party, solicitor details
- Write: Push ASIC data back to LEAP contact records
- Individuals and organisations both supported

### 2e. CALENDAR/DEADLINES: Pull Upcoming Dates ⚠️ MEDIUM CONFIDENCE

**Feasibility: Likely achievable, needs verification**

- Tasks & Calendaring is a core LEAP module (checklists, reminders, court dates)
- Whether calendar endpoints are exposed in the API needs verification after developer registration
- If not directly via API, could potentially access via Microsoft 365 integration (LEAP syncs with Outlook calendar)

### 2f. BILLING/WIP: Financial Dashboard Data ⚠️ MEDIUM CONFIDENCE

**Feasibility: Likely achievable, needs verification**

- Billing & Trust Accounting is a core LEAP module
- WIP, AR, realization, trust balances are standard LEAP reports
- Whether reporting/financial endpoints are exposed in the API needs verification
- If not via LEAP API directly, Power BI integration exists (LEAP → Power BI for reporting)

---

## 3. Technical Architecture — Recommended Approach

### 3.1 Architecture Options

| Approach | Pros | Cons | Recommendation |
|----------|------|------|----------------|
| **A. Direct API calls from BossLawyerAI** | Simplest, fewest moving parts | Tight coupling, credential management in agent | ❌ Not recommended |
| **B. Middleware service (recommended)** | Clean separation, credential vault, retry logic, audit trail | Additional service to maintain | ✅ **Recommended** |
| **C. Zapier as middleware** | No-code, fast to set up | Limited customisation, per-task costs, latency | ⚠️ Good for Phase 1 quick wins |
| **D. Supergood (third-party adapter)** | Pre-built, handles auth complexity | Vendor dependency, ongoing cost, possible overkill | ❌ Over-engineered for our needs |

### 3.2 Recommended Architecture: Middleware Service

```
┌─────────────────┐     ┌──────────────────────┐     ┌─────────────┐
│  BossLawyerAI   │────▶│  LEAP Integration     │────▶│  LEAP API   │
│  (OpenClaw)     │◀────│  Service (middleware)  │◀────│  Gateway    │
└─────────────────┘     └──────────────────────┘     └─────────────┘
                              │                            │
                              │  OAuth token management    │
                              │  Request queue & retry     │
                              │  Webhook receiver          │
                              │  Audit logging             │
                              │  Data transformation       │
                              ▼                            │
                        ┌──────────────┐                   │
                        │  Credential  │                   │
                        │  Vault       │                   │
                        │  (.env/vault)│                   │
                        └──────────────┘                   │
                                                           │
                        ┌──────────────┐     Webhooks      │
                        │  Webhook     │◀──────────────────┘
                        │  Receiver    │
                        └──────────────┘
```

### 3.3 Credential Management

- OAuth 2.0 tokens stored in encrypted environment variables or a secrets manager
- Refresh token rotation handled by middleware
- Never stored in workspace files or agent memory
- Separate sandbox and production credential sets

### 3.4 Error Handling

- Exponential backoff with retry for transient failures
- Dead-letter queue for failed operations (review and retry manually)
- Idempotency keys on write operations (prevent duplicate time entries)
- Alert Mark on critical failures (e.g., auth token expired)

---

## 4. Alternative Approaches (If API Is Insufficient)

### 4.1 Zapier as Quick-Start Bridge

- **Create fees in LEAP** from Google Sheets rows (BossLawyerAI writes to Sheet → Zapier pushes to LEAP)
- **Create matters** from form submissions
- Limitation: one-directional, limited data fields, Zapier subscription cost
- **Cost:** Zapier Professional ~US$49/month for 2,000 tasks

### 4.2 CSV/XML Import

- LEAP desktop supports import/export for some data
- Time entries *may* be importable via CSV — would need to test
- Less reliable than API, manual step required

### 4.3 Microsoft 365 Integration Path

- LEAP integrates deeply with Outlook (email filing) and Word (document automation)
- Calendar sync via Outlook → could read court dates from Outlook/Microsoft Graph API
- Document filing via Outlook/SharePoint integration

### 4.4 Power BI for Financial Data

- LEAP has Power BI integration for personalised reporting
- Could pull WIP, AR, trust balances via Power BI datasets/API
- Good fallback if LEAP billing API is limited

### 4.5 Supergood (Third-Party Unofficial API)

- Supergood.ai offers a reverse-engineered API adapter for LEAP
- Covers: Contacts & Matters, Time & Expenses, Billing & Trust, Document/Email metadata, Reporting/Audit
- Handles MFA, session management, retry logic
- **Cost:** Not publicly listed — requires assessment call
- **Risk:** Unofficial/reverse-engineered; could break on LEAP updates
- **Use case:** If LEAP's official API doesn't cover a needed endpoint

---

## 5. Recommended Phased Implementation Plan

### Phase 1: Register & Explore (Week 1–2)
**Cost: $0 | Effort: Low**

1. Register as LEAP developer at https://console.leap.build/auth/register
2. Access Sandbox environment and API reference documentation
3. Map available endpoints to our requirements
4. Document exact API capabilities, request/response formats
5. Identify any gaps between available endpoints and our needs

**Deliverable:** Detailed API capability matrix with confirmed endpoints

### Phase 2: Time Entry Push — Quick Win (Week 3–4)
**Cost: Minimal | Effort: Medium**

1. Build middleware service (Node.js or Python) for time entry creation
2. OAuth 2.0 integration with LEAP
3. BossLawyerAI generates costs narrative → middleware pushes to LEAP matter
4. Map: matter ID, date, units, narrative, fee earner (Mark Harley), rate ($800+GST)
5. Test in Sandbox → Submit for Live approval

**Deliverable:** BossLawyerAI can push billing narratives directly to LEAP matters

**Alternative Quick Win:** Use Zapier to bridge immediately while building middleware
- BossLawyerAI writes entries to Google Sheet → Zapier "Create fee" in LEAP
- Gets us running in days, not weeks

### Phase 3: Matter & Contact Sync (Week 5–8)
**Cost: Minimal | Effort: Medium-High**

1. Webhook receiver for new matter/update events from LEAP
2. Auto-create BossLawyerAI workspace when new LEAP matter opened
3. Pull matter details (parties, court, dates) from LEAP
4. Two-way contact sync (including ASIC data push)
5. Matter number mapping between systems

**Deliverable:** New matters in LEAP auto-create workspaces in BossLawyerAI with all relevant details

### Phase 4: Document Management (Week 9–12)
**Cost: Minimal | Effort: High**

1. Document pull from LEAP DMS (SOC, contracts, instructions)
2. Document push (completed pleadings, correspondence) back to LEAP
3. Version tracking and filing to correct matter folders
4. Eliminate document transfer via Telegram

**Deliverable:** Full document lifecycle managed between BossLawyerAI and LEAP DMS

### Phase 5: Calendar, Deadlines & Financial Dashboard (Week 13–16)
**Cost: Minimal | Effort: Medium-High**

1. Calendar/deadline pull from LEAP (or via Microsoft 365 fallback)
2. Court dates, filing deadlines, limitation periods → daily digest
3. WIP, AR, trust balance pull (or via Power BI fallback)
4. Compliance dashboard with critical date tracking

**Deliverable:** Complete practice management dashboard with real-time LEAP data

---

## 6. Cost Estimates

| Item | Estimated Cost | Notes |
|------|---------------|-------|
| LEAP Developer Console access | Unknown — possibly free for internal use | Need to enquire with LEAP |
| LEAP API Access Fee | Unknown — referenced in Marketplace Terms | May apply; enquire directly |
| Zapier (Phase 1 bridge) | ~AU$75/month | Professional plan, 2,000 tasks/month |
| Supergood (if needed) | Unknown — custom pricing | Only if official API insufficient |
| Middleware hosting | ~AU$0–20/month | Can run on existing BOSS-AI server |
| Development time | Internal (BossLawyerAI + Mark) | No external dev cost |
| **Total estimated ongoing cost** | **~AU$0–100/month** | Depending on approach |

---

## 7. Technical Requirements

- **LEAP subscription** with API access enabled (check current plan)
- **LEAP Developer account** (free to register)
- **Node.js or Python** runtime for middleware service
- **Webhook-capable endpoint** (BOSS-AI server or cloud function)
- **SSL certificate** for webhook receiver (HTTPS required)
- **Credential storage** — environment variables minimum; secrets manager preferred

---

## 8. Key Risks & Mitigations

| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|------------|
| LEAP API doesn't cover all needed endpoints | Medium | High | Phase 1 exploration; fallback to Zapier/Power BI/MS365 |
| API access fee is prohibitive | Low | Medium | Enquire before building; Zapier as alternative |
| App submission/approval delays | Medium | Medium | Start Sandbox work immediately; submit early |
| Rate limits restrict bulk operations | Low | Medium | Queue and batch operations; respect rate limits |
| LEAP API changes break integration | Low | High | Version pinning; monitoring; Supergood as fallback |
| OAuth token management complexity | Low | Medium | Standard OAuth 2.0 library handles this |

---

## 9. Immediate Next Steps

1. **Register** at https://console.leap.build/auth/register — Mark to create developer account
2. **Review** full API reference once authenticated — map exact endpoints
3. **Enquire** with LEAP AU about API access fees and internal-use app terms
4. **Test** time entry creation in Sandbox as proof of concept
5. **Decide** Phase 1 approach: direct middleware build vs. Zapier bridge

---

## 10. Key Links

| Resource | URL |
|----------|-----|
| LEAP Developer Portal | https://developer.leap.build/ |
| Developer Console (Register) | https://console.leap.build/auth/register |
| API Reference (requires auth) | https://leap.build/api-reference/ |
| LEAP Marketplace (AU) | https://marketplace.leap.build/en-AU/apps |
| Galaxy Design System | https://galaxy.leap.build |
| Zapier Integration | https://zapier.com/apps/leap-legal/integrations |
| LEAP Community (AU) | https://community.leap.com.au/s/ |
| LEAP System Status | https://status.leaplegalsoftware.com/ |
| Supergood (unofficial adapter) | https://supergood.ai/docs/leap-api |
| LEAP AU Main Site | https://www.leap.com.au/ |

---

*Research completed 28 April 2026. Next action: Mark to register as LEAP developer and review full API reference.*