VenturusEAM connects to virtually any ERP
If your ERP has a SQL database or an API, VenturusEAM connects to it: vendors, items, GL accounts and open purchase orders come in, and journals, asset changes and maintenance cost go back to your books. Around that connection sit a REST API, signed webhooks and inbound events, each logged and retried until it lands.
14 capabilities on this page’s part of the platform
Administration / Webhooks
Webhook deliveries
Subscription · ERP finance feed
- Sent today
- 1,284
- Pending
- 3
- Failed
- 1
- Event types
- 12
| Event | Record | Attempt | Result | Time |
|---|---|---|---|---|
| workorder.closed | WO-24817 | 1 | 200 OK | 14:52 |
| item.issued | 7014 bearing kit | 1 | 200 OK | 14:48 |
| depreciation.posted | Plant 1 · Sep | 1 | 200 OK | 14:30 |
| invoice.approved | INV-88213 | 3 | Retry at 15:15 | 14:15 |
| asset.improved | PR-02 | 1 | 200 OK | 13:57 |
Retry scheduled
- The receiving system answered 503 twice. The next attempt runs at 15:15 on the backoff schedule.
- The payload is signed with HMAC-SHA256 and is identical on every attempt.
Popular ERP systems VenturusEAM connects to
These are the systems we meet most often in plants. Each keeps its records in a database VenturusEAM can read from and write to, so the connection is built on your data model, not on a file drop. If your system is not on the wall, ask; the connection is built the same way.
Microsoft SQL Server
Microsoft SQL Server
Microsoft SQL Server
Microsoft SQL Server or SAP HANA
Microsoft SQL Server
Microsoft SQL Server
Microsoft SQL Server- JobBOSS²Microsoft SQL Server
- E2Shop SystemMicrosoft SQL Server
Microsoft SQL Server
SQL mirror of its database
PostgreSQL
Product names and logos belong to their owners. Cloud systems such as NetSuite and Plex connect through their APIs.
A REST API for assets, records and sensor readings
Other systems can list, read, create, update and retire assets, pull a record with its linked source records, and post sensor readings in batches. Every call carries an API key that an administrator issues, can set to expire and can revoke, and each key is limited to its company.
Asset REST API
Lets other systems list, read, create, update and retire assets over a documented REST API.
API keys by company
Lets an administrator issue and revoke API keys, each tied to your account and optionally to one company.
Sensor reading API
Takes sensor readings from gateways and historians, flags readings outside their limits, and keeps the latest value per asset.
Record detail feed
Returns a record and its linked source records as JSON, for side panels and connected tools.
Signed webhooks when something happens
Subscribe a system to the events it cares about, such as a work order closed, a part issued or a purchase order approved. Each message is signed, written in the same transaction as the change so none are lost, and retried on a backoff schedule with every attempt logged.
Outbound webhooks
Sends a signed message to your other systems when something happens, such as an asset created or a work order closed.
Webhook event catalog
Publishes the list of events the product sends and the exact fields in each, generated from the code so it stays current.
Event outbox with automatic retry
Retries failed deliveries on a backoff schedule and lets an administrator retry or replay any event.
Webhook delivery log
Shows every delivery attempt for each subscription, with the exact payload sent.
Finance events your ledger can act on
Depreciation posted, assets improved or disposed of, and vendor invoices approved, paid or voided all go out as signed events. Your finance system hears about the change when it happens, not at the next export.
Disposal and reversal events
Signed webhooks tell your other systems when an asset is disposed of or returned to service.
Depreciation and improvement events
Signed webhooks fire when depreciation posts, when missed depreciation is caught up, and when an asset is improved.
Invoice approval and payment events
Signed webhooks fire when a vendor invoice is approved, paid or voided, and when a payment is voided.
Inbound events from the systems around you
Other systems can send signed updates, such as an asset change or a work order status, to their own endpoint. Each message is checked, applied once even if it arrives twice, and kept in a log where an administrator can retry or replay it, with value maps that translate the other system’s codes to your records.
Inbound webhooks
Accepts signed updates from other systems, such as an asset change or a work order status, and applies each only once.
Inbound event log with retry and replay
Lists every inbound event with its result and lets an administrator retry or replay it.
Value mapping for connected systems
Maps another system's IDs and codes to your records so inbound updates land on the right asset.
Connecting VenturusEAM to your ERP
Your ERP connects through the same three paths. It reads and writes assets over the REST API, hears about work orders, receipts, invoices and depreciation through signed webhooks, and sends its own changes back as inbound events, so each system keeps the records it owns.
Asset REST API
Lets other systems list, read, create, update and retire assets over a documented REST API.
Webhook event catalog
Publishes the list of events the product sends and the exact fields in each, generated from the code so it stays current.
Inbound webhooks
Accepts signed updates from other systems, such as an asset change or a work order status, and applies each only once.
Value mapping for connected systems
Maps another system's IDs and codes to your records so inbound updates land on the right asset.
Related
Common questions
Which ERP systems does VenturusEAM work with?
Virtually any. If your ERP has a SQL database or an API, VenturusEAM reads from it and writes to it, including Epicor Kinetic, Infor CloudSuite Industrial, Microsoft Dynamics 365 Business Central, SAP Business One, Sage, Acumatica, Global Shop Solutions and Odoo. Cloud systems such as NetSuite and Plex connect through their APIs.
How do we know a webhook really came from VenturusEAM?
Every message is signed with HMAC-SHA256 over a timestamp and the payload, using a secret for that subscription. Your system checks the signature before trusting the message, and an administrator can rotate the secret at any time.
What happens if our system is down when an event is sent?
The event waits in an outbox and is retried up to eight times, from one minute out to sixteen hours. An administrator can see every attempt, open the exact payload and retry or replay an event by hand.
Which events can we subscribe to?
About 30 event types, including asset created, improved and disposed, depreciation posted, PM generated, work order created and closed, item issued and received, purchase order approved and received, and invoice approved and paid. The catalog lists the fields in each one.
Can an API key see every company?
Only if an administrator who sees every company issues it that way. A key is normally tied to one company, only its hash is stored, and it can carry an expiry date.
The plant never stops. Neither does the record.
Bring an asset list and a month of work orders. We will load them and walk through your own plant in VenturusEAM, from the purchase order to the depreciation run.