Pennylane

Pennylane (via Apideck)

Access Pennylane 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 Pennylane plumbing.

Beta connector. Pennylane 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: pennylane
• Unified API: Accounting
• Auth type: oauth2
• Status: beta
• Apideck setup guide: Connection guide
• Gotchas: page
• Pennylane docs: https://pennylane.readme.io
• Homepage: https://www.pennylane.com/

At a glance

• Implementation difficulty: moderate — Partner-Issued Credentials Required — OAuth apps are provisioned manually by Pennylane's Partnerships team (no self-service portal); otherwise a standard OAuth authorization-code connect.
• Vendor partnership required: yes (developer portal) — OAuth Client ID and Secret are issued by Pennylane's Partnerships team after manual validation (no fee). The Client Secret is shown only once and cannot be retrieved again — store it immediately, or create a new OAuth app if it is lost. There is no self-service developer portal (developer.pennylane.com does not exist); request credentials via the partnership form.
• Apideck-managed credentials: Not available — consumers supply their own partnership-issued OAuth credentials in every environment.
• Account type required: Active Pennylane account (app.pennylane.com) with at least one company set up.
• Consumer access level: A user with permission to authorize third-party (OAuth) apps for the company.
• Sandbox: available — Provisioned by the Pennylane Partnerships team on request as part of the partnership process — there is no self-service sandbox. Same rate limits as production.
• Costs: No partnership or API fees; consumers need an active Pennylane subscription.
• Rate limits: 25 requests per 5 seconds per token (production and sandbox).
• Authentication: OAuth 2.0 (Authorization Code).
• Webhooks: Virtual webhooks (polling-based change detection) for customer, supplier, invoice, invoice-item, and bill events — created and updated, 10 events across 5 resources. Pennylane's native webhooks are not used.

Important to know:

• There is no stated turnaround for OAuth credential issuance, so provisioning can gate your go-live — budget an unpredictable lead time rather than assuming instant self-service access.
• Pennylane is available in France and Germany only — consumers based in other countries will not have a Pennylane account to connect, so confirm geographic fit before committing.
• Access tokens last 24 hours and refresh tokens are valid for 90 days, rotating on every refresh; both are refreshed automatically by Apideck, but a connection left dormant beyond 90 days must be re-authorized by the consumer.
• The partner onboarding journey is French-first — the partnership request form and parts of Pennylane's documentation are in French.

Facts synced from Apideck's connector metadata API — GET /connector/connectors/pennylane (overview field) is the live, authoritative version.

When to use this skill

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

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

Portable across 34 Accounting connectors

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

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

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

Pennylane via Apideck Accounting

Pennylane is a French/European cloud accounting and finance platform blending bookkeeping with modern UX. Fast-growing in France; expanding across the EU.

Entity mapping

Coverage highlights

• ✅ CRUD on invoices, bills, customers, suppliers
• ✅ Purchase orders and quotes (France-typical sales workflow)
• ✅ Analytic dimensions (cost centre / project tracking)
• ✅ Bank feed statements for reconciliation
• ✅ Attachments on invoices / bills (Pennylane's document-centric model)
• ⚠️ French-specific VAT declaration (CA3) — not exposed; use Proxy
• ❌ Payroll features — separate Pennylane surface
• ❌ Bill automation rules — use Proxy

Auth notes

• Type: OAuth 2.0, managed by Apideck Vault
• Company binding: one Pennylane company per connection.
• French market focus: defaults to French-specific tax codes and reporting; users outside France may see reduced functionality.

Example: create a purchase order

const { data } = await apideck.accounting.purchaseOrders.create({
  serviceId: "pennylane",
  purchaseOrder: {
    supplier_id: "supplier_abc",
    line_items: [{ description: "Widgets", quantity: 10, unit_price: 25.5 }],
    currency: "EUR",
  },
});

Escape hatch: Proxy API

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

See Pennylane'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 Pennylane
• Accounting OpenAPI spec · API Explorer
• apideck-connector-coverage — programmatic coverage checks
• apideck-best-practices — architecture, Vault, pagination, error handling
• apideck-node — TypeScript / Node SDK patterns
• Pennylane official docs