Integrations
STRYKE and JobBOSS²
JobBOSS² has a public API, and STRYKE uses it with your shop's own keys. A customer PO becomes an Order in JobBOSS² with the Jobs it cuts; a vendor invoice is checked against the JobBOSS² PO and receiver, then goes to your books.
How the connection works
By ECI's public API, signed in with your keys, never a shared account of ours.
- OAuth 2.0 client credentials against the ECI host you pick from a fixed list; a typed address could send your keys anywhere
- Nothing is saved until JobBOSS² accepts the keys, names your company and lets STRYKE read its customers
- Before each Order is written, STRYKE asks JobBOSS² whether that customer PO number is already on one
- One JobBOSS² company connects to one STRYKE shop
What a PO becomes in JobBOSS²
An Order, entered the way your order desk enters it.
- An Order with the customer PO number, lines, quantity, unit price and due date, read back so STRYKE knows its number
- Processing the Order cuts one Job per line, named the way JobBOSS² names them
- A change order that adds a line is added to the open Order; a change to a line already there is held, because the public API cannot change or cancel one
- A PO from a customer JobBOSS² does not have yet is held with a note to add the customer there; the public API has no customer create
- A vendor invoice is matched to the JobBOSS² PO and receiver and entered as a Bill in your books
What to have ready
Four things from JobBOSS²'s API portal, entered once in Settings › Connections.
- The ECI host your company is on, picked from the list
- The client id and client secret
- The API key, which JobBOSS² needs on every call
- Your company code
Read the vendor's own pages
ECI 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.
