An open REST API, real-time webhooks and ready-made integrations for payments, shops and business systems — so IDup fits the stack you already run instead of forcing you to replace it.
All-in-one platforms usually make an implicit demand: give up everything else. That is rarely realistic. There is a shop system that works, a payment provider that is already integrated, a tool a team depends on, and a process built around something specific.
IDup is designed to be the centre of that stack rather than a replacement for it. Because accounting, CRM, projects, support, documents and messaging already share one database, most of the integrations businesses normally build simply do not need to exist — and the ones that remain are genuine connections to the outside world.
Those run on an open REST API and webhooks. Push data in, pull data out, trigger workflows on real business events, and connect ready-made integrations for payments, shops and business systems — with tokens, permissions and an audit trail so a connection is not a hole in your security model.
All in IDup — one login, no silos.
Read and write customers, invoices, projects, documents and bookings programmatically, with clear, consistent endpoints — so anything you can do in the interface can be automated.
Business events pushed to your systems the moment they happen: an invoice paid, a lead created, a project completed, a document uploaded — no polling, no delay, no scheduled sync job.
Payments, shop systems and common business tools connect without development, so the most frequent connections are a configuration step rather than a project.
Scoped tokens, granular permissions, rate limiting and a complete audit trail, so an integration has exactly the access it needs and every call it makes is traceable.
Most integration work in a small business is not connecting to the outside world. It is connecting internal tools to each other: the CRM to the invoicing system, the invoicing system to accounting, the project tool to the timesheet, the helpdesk to the customer list.
Every one of those connections costs money to build, breaks when either side changes, and requires somebody to notice when it silently stops working.
In IDup those systems are one system, so those integrations do not exist. What remains is the small number of genuinely external connections — your shop, your payment provider, a specific tool you rely on — and those are exactly what the API and webhooks are for.
Scoped credentials with exactly the permissions the integration requires — nothing more.
Ready-made connectors for payments and shops, or your own endpoint for anything else.
Events flow in real time in both directions, with every call logged and traceable.
An integration is a permanent door into your business data, and in many companies it is the least governed one. A key generated once, shared in a chat, with full permissions, still working three years and two employees later.
IDup treats API access with the same permission model as human access. Tokens are scoped to what an integration actually needs, they can be rotated or revoked in one action, and every call appears in the audit trail alongside manual actions.
That is what makes an open API acceptable in a system holding financial and personal data: the openness is real, and so is the control over it.
One login, ein Preis – keine versteckten Zusatzkosten.
Read and write the core objects — customers, leads, estimates, invoices, payments, projects, tasks, documents and bookings — so anything you do in the interface can be driven programmatically.
You register an endpoint and select the events you care about. IDup pushes them in real time as they happen, so your systems react immediately instead of polling on a schedule.
Payments, shop systems and common business tools connect without development. Where a native connector does not exist, a webhook and an API key are usually a short job rather than a project.
Yes. Tokens are scoped and revocable, permissions are granular, requests are rate-limited and every call is recorded in the same audit trail as manual actions.
The API is versioned and backwards compatible within a version, so platform updates do not silently break a working connection.
Minutes. Create a scoped key, make your first call or point a webhook at your endpoint — there is nothing to install and no approval process to wait for.
Copyright © 2025 - IDup. All rights Reserved.
