The eBound integration API is used for connectivity between Orchid eBound™ and ERP or POS solutions. The full integration guide can be downloaded below.
The guide covers:
API overview
- Architecture and integrations
- Interactive API documents and payloads
- In-scope transactions — acquisitions, dispositions, manufacturing and adjustments
- Approved ATF firearm types, and a note on FFL numbers
- The API endpoint, for 4473 and core transactions
- Frequency of data transmission
- Active error detection — synchronous feedback
- Passive error detection — the API Error Log
Endpoint review
- Endpoint #1 — 4473 transactions
- Endpoint #2 — core transactions
- Synchronous API overview: method, format, transaction values and headers
Body content
Sample payloads and required fields, lengths and formats for each transaction:
- Serialize
- Receive
- FFL Transfer
- Exempt Transfer
- Assemble
- Disassemble
- Destroy
Related documentation
Orchid eBound API - Responses — every response the Transaction API can return, including the pre-flight errors that reject a batch and the per-transaction messages that explain why a single transaction was rejected.