Wave
One abstraction, 146 SaaS connectors. Agent skills for Apideck's Unified API — integrate Salesforce, QuickBooks, BambooHR, Jira, Shopify and 140+ more by changing one string.
npx -y skills add apideck-libraries/api-skills --skill waveAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Wave integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Wave. Routes through Apideck with serviceId "wave".
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
6.9 KB, ~1.7k tokens by cl100k_base, as published. Nobody here has run it
Wave (via Apideck)
Access Wave through Apideck's Accounting unified API — one of 34 Accounting connectors that share the same method surface. Code you write here ports to Access Financials, Acumatica, banqUP and 30 other Accounting connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Wave plumbing.
Beta connector. Wave is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.
Quick facts
- Apideck serviceId:
wave - Unified API: Accounting
- Auth type: oauth2
- Status: beta
- Apideck setup guide: Connection guide
- Gotchas: page
- Wave docs: https://developer.waveapps.com
- Homepage: https://www.waveapps.com/
When to use this skill
Activate this skill when the user explicitly wants to work with Wave — for example, "create an invoice in Wave" or "reconcile payments in Wave". This skill teaches the agent:
- Which Apideck unified API covers Wave (Accounting)
- The correct
serviceIdto pass on every call (wave) - Wave-specific auth and coverage caveats
For the full method surface (parameters, pagination, filtering), use your language SDK skill:
apideck-node,apideck-python,apideck-dotnet,apideck-java,apideck-go,apideck-php, orapideck-rest
For the raw OpenAPI spec:
- Accounting: https://specs.apideck.com/accounting.yml · API Explorer
Minimal example (TypeScript)
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
// List invoices in Wave
const { data } = await apideck.accounting.invoices.list({
serviceId: "wave",
});
Portable across 34 Accounting connectors
The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from Wave to another Accounting connector is a one-string change — no rewrite, no new SDK.
// Today — Wave
await apideck.accounting.invoices.list({ serviceId: "wave" });
// Tomorrow — same code, different connector
await apideck.accounting.invoices.list({ serviceId: "access-financials" });
await apideck.accounting.invoices.list({ serviceId: "acumatica" });
This is the compounding advantage of using Apideck over integrating Wave directly: code against the unified Accounting API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
Wave via Apideck Accounting
Wave is a free US/CA accounting platform popular with small businesses and freelancers. Coverage is read-oriented for reporting, and invoicing is the primary write path.
Entity mapping
| Wave entity | Apideck Accounting resource |
|---|---|
| Invoice | invoices |
| Customer | customers |
| Vendor | suppliers |
| Account | ledger-accounts |
| Product | invoice-items |
| Sales Tax | tax-rates |
| Bank Account | bank-accounts |
| Business | company-info |
| P&L, Balance Sheet | profit-and-loss, balance-sheet |
| Bank Feed Statements | bank-feed-statements |
Coverage highlights
- ✅ Invoices (CRUD)
- ✅ Customers, suppliers, products
- ✅ Tax rates and chart of accounts
- ✅ Financial reports (P&L, Balance Sheet)
- ✅ Bank feed statements
- ⚠️ Bill / expense management — limited; use Proxy for Wave's specific bill endpoints
- ❌ Payroll — Wave Payroll is a separate product surface
- ❌ Receipt scanning — Wave-specific feature
Auth notes
- Type: OAuth 2.0, managed by Apideck Vault
- Business binding: one Wave business per connection. Multi-business users need separate connections.
- GraphQL upstream: Wave's API is GraphQL; Apideck translates unified REST calls into GraphQL queries. For complex reads, the Proxy API forwards raw GraphQL.
Example: list customers with contact details
const { data } = await apideck.accounting.customers.list({
serviceId: "wave",
fields: "id,display_name,email,phone,addresses",
});
Escape hatch: Proxy API
When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Wave directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Wave's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: wave" \
-H "x-apideck-downstream-url: <target endpoint on Wave>" \
-H "x-apideck-downstream-method: GET"
See Wave's API docs for available endpoints.
Sibling connectors
Other Accounting connectors that share this unified API surface (same method signatures, just change serviceId):
access-financials (beta), acumatica (beta), banqup (beta), campfire (beta), clearbooks-uk (beta), digits (beta), dualentry, exact-online, and 25 more.
See also
- Apideck connection guide for Wave
- Accounting OpenAPI spec · API Explorer
apideck-connector-coverage— programmatic coverage checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- Wave official docs