The API Report CardAPI Index
Holded

Holded API

holded.com

Holded ships a public REST API with 293 v1 endpoints spanning sales, inventory, accounting, CRM, and treasury; keys are self-serve on any paid plan. Quirks bite: a custom 'key' auth header, only the first key can write, no v1 webhooks, and rate limits surface as undocumented 429s.

Last verified: July 2026Accounting & Tax
API GRADE
D+
VERIFIED JUL 2026

SCORECARD

ExistenceGOODPublic REST API with 293 documented v1 endpoints and a published v2 OpenAPI spec at developers.holded.com.
AccessGOODAPI keys are self-serve under Settings > Developers on any paid tier from EUR 14.50/mo; not on the free trial.
CoverageGOOD293 v1 endpoints across nine areas: sales, inventory, accounting, contacts, CRM, projects, HR, calendar, treasury.
AuthPOORA custom 'key' header instead of Bearer; only the first key ever created can write, and every key has full account access.
Docs & DXPOORNo first-party webhooks in v1, so integrators poll; SDKs are community-built despite 'official SDK' marketing.
StabilityMIXEDv1 stays the production surface while v2 (Bearer auth, cursor pagination) targets June 2026 GA; 429s arrive undocumented.
MORE FROM THE REPORT CARD
Supergood: Holded has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Holded scores D+ on the API Report Card. Holded ships a public REST API with 293 v1 endpoints spanning sales, inventory, accounting, CRM, and treasury; keys are self-serve on any paid plan. Quirks bite: a custom 'key' auth header, only the first key can write, no v1 webhooks, and rate limits surface as undocumented 429s.

Tried to integrate with Holded?
SOURCES
No native first-party webhook system in v1 - the production API surface still in use today has no event subscription model, forcing integrators to poll for changes; webhooks remain 'coming soon' in v2 with no firm GA date for production-grade event delivery holded.com β†—
Only the FIRST API key generated on an account has read+write capability; all subsequent API keys are read-only, an unusual restriction that forces account owners to share the single bidirectional key across integrations or revoke/regenerate it (with cascading breakage) when an integration must be rotated help.holded.com β†—
API keys do not inherit user role-based permissions and do not allow custom access scoping - any API key has full account-wide access, creating principle-of-least-privilege violations and a single-point-of-compromise risk help.holded.com β†—
Authentication uses a custom 'key' HTTP header rather than the standard Authorization: Bearer convention, breaking out-of-the-box compatibility with HTTP clients, API gateways, OpenAPI codegen, and middleware that expects standard auth headers developers.holded.com β†—
API access is gated to paid plans only (NOT available on the free Plus trial), and v2's gating tier has not been publicly clarified - integrators building free-tier-friendly workflows are blocked help.holded.com β†—
Rate limits are documented as 'depending on the subscribed plan' with no visible usage counter in the account dashboard, no published per-tier numbers, and no rate-limit response headers (X-RateLimit-Limit, X-RateLimit-Remaining, Retry-After) - integrators must guess the throttle, back off blindly on HTTP 429, and have no way to forecast capacity help.holded.com β†—
Custom roles cannot generate or view API keys - a Spanish asesoria managing dozens of client accounts via custom-role staff cannot delegate API-key management without granting full owner/admin rights help.holded.com β†—
The v1 to v2 API migration is in progress with v2 only in 'preview' (June 2026 GA target) - integrators face a forced re-platforming with no published deprecation timeline for v1, creating multi-year integration maintenance burden holded.com β†—
No native OAuth 2.0 flow - API-key-as-Bearer authentication means third-party integrators cannot do standard end-user-consent flows and must instead ask each Holded customer to manually generate and paste an API key, which is a known conversion-killer for SaaS integrations developers.holded.com β†—
Custom fields and the Spanish-localization-specific schema (Plan General Contable account codes, Modelo report mappings, SII / Verifactu metadata) are not consistently documented in the API reference, requiring integrators to reverse-engineer the field layer per customer database rollout.com β†—
The v1 API documentation is described by community integration guides as shallow and incomplete - many endpoints exist in the OpenAPI spec but lack worked examples, leaving integrators to test against live customer accounts apitracker.io β†—
MCP server is advertised as 'upcoming' but not yet shipped, meaning AI-assistant integrations (Claude, ChatGPT, Cursor) cannot natively reason over a customer's Holded data without an intermediate scraping layer holded.com β†—
Bank account synchronization is widely cited as unreliable, with users reporting bank feeds broken for three months or more despite repeated support tickets trustpilot.com β†—
Customer support quality has degraded post-Visma acquisition - replies described as taking a week or never arriving, account managers not responding, heavy reliance on chatbots before reaching a human trustpilot.com β†—
Recurring-payment and direct-debit (domiciliacion) features have bugs that can impact annual accounting integrity capterra.com β†—
Platform performance has deteriorated - users report slow searches, long wait times between screens, and degraded responsiveness recently capterra.com β†—
SII (real-time VAT reporting) is not supported in the Canary Islands, blocking adoption by Canarian businesses subject to IGIC instead of IVA capterra.com β†—
Not suitable for companies with turnover above EUR 6M - reviewers explicitly note growing businesses must migrate off Holded to Sage 50 / Sage 200 / SAP B1 / Business Central capterra.com β†—
Pricing is considered expensive relative to competitors for the feature breadth offered, with users on lower tiers locked out of meaningful functionality (only 1 bank connection on Plus, no priority support below Advanced) trustpilot.com β†—
Mobile app needs significant improvement - users report missing functionality compared to web app and frequent sync issues capterra.com β†—
Currency conversion and multi-currency handling has bugs, particularly around historical FX rates and invoice translation capterra.com β†—
Returns/refunds frequently do not register correctly against original invoices, requiring manual journal-entry workarounds capterra.com β†—
Feature requests and product improvements take a long time to ship, with the post-acquisition product roadmap perceived as slow compared to the pre-Visma startup pace g2.com β†—
Pricing structure can be limiting for larger teams - per-user economics become punitive above 7 users + accountant (the Advanced tier cap) g2.com β†—