Integrations
STRYKE and Epicor Kinetic
Epicor Kinetic serves its REST API from each installation, so STRYKE builds the connection from your instance's own documentation and your keys, and tests it before anything is written. It is not a ready-made connector today; your plan says which door yours takes.
How the connection works
Tell us your ERP: STRYKE reads your Kinetic API's documentation and builds the connection from it.
- You point STRYKE at the REST help your instance serves, a PDF of it, or pasted text
- STRYKE builds the connection from it and your keys, then tests it by reading only
- Nothing is written until that test passes
- Where the API is closed to you, STRYKE writes an import file for each entry, or its desktop runner keys the entry into Kinetic's screens
What a PO becomes in Epicor Kinetic
A sales order, with the checks every STRYKE entry gets.
- A sales order with the customer PO number, lines, quantity, price and need-by date
- Every line matched to your part number and checked against your quote before it is written
- Through an import file or the runner, STRYKE cannot ask the ERP whether a PO is already in, so that check waits for a person's one click
- Vendor invoices go to your books as Bills
What to have ready
What your Kinetic administrator already has.
- The address your Kinetic REST API answers at
- Its documentation: the help page your instance serves, a PDF, or pasted text
- The keys the documentation names: an API key, a client id and secret, or a user
- Without an API: your import map, or one shop PC signed into Kinetic for the runner
Read the vendor's own pages
Epicor publishes these; they are its pages, not ours.
Starting at $500 a month*
Every document, every system you connect. No seats, no per-system fees, month to month. *Plans scale with your document volume. How pricing works.
