Invoice extraction, reconciliation proposals, quotes, project hours and lead triage connected to Holded after validating endpoints, permissions, data and limits in your account and plan.
Amura Software provides integration services independently. Naming brands or products on this page does not imply affiliation, an official partnership or endorsement by their providers.
When invoicing, expenses, projects and CRM live in Holded, a parallel tool can duplicate contacts, consume the API quota or separate a decision from its accounting record. We design the flow around the resources and permissions the API actually exposes in the customer account.
Before building, we confirm the API version, plan, token permissions, required endpoints and remaining monthly usage. Sensitive writes begin as reviewable drafts or proposals; they are automated only after agreeing thresholds, human approvals and tests with authorised tenant data.
Figures, timings and accuracy levels on these cards are illustrative operating targets. We validate them with your data during the pilot; they are not achieved client results.
The flow extracts headers, lines, taxes and withholding from a PDF, email or image, then checks the contact and required fields before preparing a purchase record. Automatic creation is enabled only if the pilot meets agreed thresholds; uncertain cases remain in review with the reason.
Matches movements to documents using amount, date, counterparty and reference. The public API documents read and reconciliation operations, but we verify availability and permissions in your account; by default, the result remains a proposal for the accountant.
Reads products, price lists and contact data available through validated endpoints and prepares a traceable quote. The sales team checks product, price, tax and terms before approving or sending it.
Collects hours and notes from authorised sources and proposes their assignment to the right project and task. We validate time-tracking endpoints, permissions and the tenant's approval cycle before enabling any write.
Classifies inbound items by intent and priority and proposes an owner and next action. Fields, permissions, enrichment sources and data-protection rules are validated with the customer before an opportunity is created or updated.
The customer creates an API Token in Developers and selects the permissions it needs. Each v2 call sends it as Authorization: Bearer. Because a token should not be treated like an ordinary user's permission, we apply least privilege, encrypted storage, separation by account and a rehearsed rotation before retiring the previous credential.
We map only resources and actions present in the official reference, then use controlled reads to verify required fields, states and permissions for your API version. An additional field or external reference is used only if the endpoint supports it and its behaviour has been tested in that account.
The current public table lists monthly quotas of Plus 500, Basic 2,000, Standard 7,500, Advanced 30,000 and Premium 100,000 with possible billed overage; per-minute limits also vary by plan. We confirm the plan and remaining usage in Developers > API Usage, monitor quota headers and, on a 429, honour Retry-After with backoff and jitter.
Official documentation publishes signed webhooks, but we do not assume identical availability or coverage across every account or API version. We query the tenant's event types; where present, we verify the HMAC signature, acknowledge quickly and deduplicate on x-holded-webhook-id. Otherwise we use bounded, cached polling.
The API is not presented as an exactly-once transport, and the documentation does not promise a dedicated sandbox. We start with the interactive documentation or Postman, then use an authorised test account or controlled records. We persist an operation key and outcome, re-read after ambiguous responses and promote only after replay, failure and human-review tests pass.
Documentation checked on 9 August 2026. Features, permissions and limits can change; before implementation, we compare them with the API version, plan and configuration available in your account.
Modular open-source ERP, AI agents and workflows on top of sales, inventory and project modules.
View integration →Reference ERP for mid-market distribution and manufacturing, document extraction and ops orchestration.
View integration →Mid-market CRM with broad APIs, a natural fit for sales agents and lead enrichment.
View integration →Current Holded help states that the API is available on paid or trial accounts and not on Free. Before estimating the work, we check Developers access, the active plan, API version, token permissions and required endpoints in your account.
Holded publishes per-minute limits and monthly plan quotas: currently 500 calls on Plus, 2,000 on Basic, 7,500 on Standard, 30,000 on Advanced and 100,000 with possible billed overage on Premium. Because terms can change, we validate the plan, remaining usage and any overage rule in your tenant before sizing the flow.
The v2 reference documents reading and reconciling bank movements, but we first verify those endpoints and permissions in your account. The flow proposes matches with its evidence and retains human approval until the customer accepts the rules, thresholds and exception handling.
Holded associates each account and its limits with a fiscal entity. We treat every account as an independent tenant with separate token, configuration, queue, log and idempotency state. Before a write, we verify the expected account identifier and record the destination in the audit log.
We design for privacy from the start, human control, traceability, usage limits, permissioning and documentation. For sensitive processes, we help assess risk and applicable obligations under GDPR and the EU AI Act.
Every engagement is led personally by one of the partners. If there's a fit, you get a personal first read of your case within one business day, not a canned demo.
