Integrations
Integrations connect AVERASE to the systems your ITAD operation already runs. Today that means RazorERP: connect it once under settings, then push assets and erasure results to it directly from the Inventory and Wipes grids.
The Integrations page lives in the settings section's Developer group and is admin-only — members who open it see "Ask an account admin to connect RazorERP."
RazorERP
The card is described as: "Push erasure results to RazorERP asset records." A badge shows its state — Connected or Not connected.
Connecting
The connect form takes four fields:
- Name
API token- Type
- password
- Description
Your RazorERP API token, stored encrypted. Hint: "Generate one in RazorERP under your user profile → Razor API → Generate new."
- Name
API base URL- Type
- url
- Description
Defaults to
https://apiprod.razorerp.com. Must be https.
- Name
Lot auto-name- Type
- string
- Description
Required by Razor when creating assets.
- Name
Asset workflow step- Type
- string
- Description
Defaults to "Data Collection".
The token is verified before anything is saved. Submitting the form makes a live call to RazorERP (GET /api/v1/Lookup/data-erasure-methods against your base URL); only a token that answers is persisted. The outcome is one of two flashes:
- Success: "RazorERP connected — token verified."
- Failure: "Token failed verification against RazorERP — nothing saved. Check the token and base URL."
A failed verification leaves the integration exactly as it was — no partial state, no stored-but-broken credentials.
Disconnecting
Disconnecting removes the stored credentials and flashes "RazorERP disconnected." The Push menu in the grids stops offering RazorERP until it's reconnected.
Pushing records from the grids
Once connected, RazorERP appears in the Push menu of the Inventory and Wipes grids. The Push button is icon-only until you select rows, then it reads the selection back to you — "3 Assets", "1 Wipe".
The flow:
- Select rows in the grid, then open Push and choose the integration. Pushing with nothing selected flashes: "Select at least one row to push."
- Pick a lot. The dialog live-fetches your Razor lots and lets you choose where newly created assets land. The dialog explains the semantics: "Records already in Razor are updated in place — the lot only applies to newly created assets."
- Push. Up to 200 records per push, of one record type at a time — assets from Inventory, wipe results from Wipes. A successful submit flashes "Pushing N records to the integration…" and the deliveries proceed in the background.
If the chosen integration isn't connected (for example, it was disconnected after the page loaded), the push is refused with: "That integration isn't connected. Set it up under Integrations first."
The delivery log
The Integrations page keeps a log of the last 25 deliveries, so you can see what actually reached RazorERP:
| Column | Contents |
|---|---|
| Record | The pushed record's label, plus its external uid once RazorERP has assigned one |
| Integration | Which integration received it |
| Status | queued (yellow) → delivered (green) or failed (red); the row shows created/updated timestamps, and a failed row shows its last error |
| Pushed by | The user who started the push |
| When | When the delivery was created |
A queued delivery is waiting on the background worker; delivered means RazorERP accepted the record; failed shows the last error so you can fix the cause (usually the token or base URL) and push again.
Prefer webhooks for everything else
RazorERP is a first-party, push-button integration. For any other system, use webhooks — the generic alternative that delivers signed wipe, asset, and certificate events to any https endpoint you control, the moment they happen, with retries and a delivery ledger of their own.