Banqup

Skill apideck-libraries/api-skills/skills/banqup

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.

Install

npx -y skills add apideck-libraries/api-skills --skill banqup

Assembled 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

banqUP 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 banqUP. Routes through Apideck with serviceId "banqup".

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.5 KB, ~1.6k tokens by cl100k_base, as published. Nobody here has run it

banqUP (via Apideck)

Access banqUP 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, Campfire 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 banqUP plumbing.

Beta connector. banqUP 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: banqup
Unified API: Accounting
Auth type: oauth2
Status: beta
Gotchas: page
banqUP docs: https://banqup.com
Homepage: https://banqup.com/

When to use this skill

Activate this skill when the user explicitly wants to work with banqUP — for example, "create an invoice in banqUP" or "reconcile payments in banqUP". This skill teaches the agent:

Which Apideck unified API covers banqUP (Accounting)
The correct serviceId to pass on every call (banqup)
banqUP-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, or apideck-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 banqUP
const { data } = await apideck.accounting.invoices.list({
  serviceId: "banqup",
});

Portable across 34 Accounting connectors

The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from banqUP to another Accounting connector is a one-string change — no rewrite, no new SDK.

// Today — banqUP
await apideck.accounting.invoices.list({ serviceId: "banqup" });

// 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 banqUP 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.

banqUP via Apideck Accounting

banqUP is a Belgian cloud invoicing and business banking platform targeting SMBs and accountants. Apideck coverage is invoice-focused.

Entity mapping

banqUP entity	Apideck Accounting resource
Invoice	`invoices`
Customer	`customers`

Coverage highlights

✅ Invoices (CRUD)
✅ Customers
⚠️ AP / bills — not in current Apideck mapping; use Proxy
❌ Payments, journal entries, ledger accounts — use Proxy
❌ Business banking features — separate banqUP API surface

Auth notes

Type: OAuth 2.0, managed by Apideck Vault
Organization binding: one banqUP organization per connection.
Belgium-focused: Belgian compliance (PEPPOL e-invoicing, Belgian VAT) built-in.
Coverage is narrow: this connector currently exposes only invoices + customers. If you need full accounting breadth, pick a different Belgian connector (e.g. exact-online).

Example: create an invoice

const { data } = await apideck.accounting.invoices.create({
  serviceId: "banqup",
  invoice: {
    customer_id: "cust_abc",
    invoice_date: "2026-04-18",
    line_items: [
      { description: "Consulting", quantity: 5, unit_price: 120 },
    ],
    currency: "EUR",
  },
});

Escape hatch: Proxy API

When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call banqUP directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on banqUP'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: banqup" \
  -H "x-apideck-downstream-url: <target endpoint on banqUP>" \
  -H "x-apideck-downstream-method: GET"

See banqUP'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), campfire (beta), clearbooks-uk (beta), digits (beta), dualentry, exact-online, exact-online-nl (beta), and 25 more.