Pennylane is automatable through its API

Pennylane is automatable today through its public API. The Company API token guide says an Essential plan or higher and an executive or accountant role are required. The token is sent as Authorization Bearer. The example call is GET https://app.pennylane.com/api/external/v2/me and the response is JSON. A token is read-only or read-and-write, and it expires after 1 month, 6 months, 12 months, or never. A missing scope returns 403. OAuth 2.0 authorization code is documented for integration partners and for firm-level access. Registering an OAuth app goes through the Partnerships team. The example token response has expires_in 86400, and the guide says access tokens expire after 24 hours. Refresh tokens last 90 days and rotate on use. The API choice guide says the Company API covers sales documents, purchases, accounting entries, and reports such as the trial balance and FEC. The Firm API is for a client portfolio. The Firm Group API is on request. Rate limiting allows 25 requests every 5 seconds per token, and a 429 includes retry-after. Webhooks are documented and marked beta. Pennylane POSTs to an HTTPS endpoint the integration registers. The official MCP server at https://mcp.pennylane.com/mcp uses OAuth 2.1 with PKCE and Streamable HTTP. It is read-only. Company access needs Essentiel or above. The MCP guide says the Free, Starter, and Basic plans are not eligible. The tool reference lists customers, invoices, suppliers, ledger lines, the trial balance, VAT and tax returns, and a read-only operations pair. The guide says writes are planned and that write access uses the API. Zapier, Make, Power Automate, and n8n catalog pages were not opened. Computer-use viability is unassessed. The API scores 7. The MCP server scores 6 because the read surface is broad and writes are absent. The API is the best path because it can create and update records.

Best path today: api · Overall automatability: 7/10