Built for Developers, Architects & Integrators

vpn_keyHow do I authenticate with the eveXso API?

Authentication uses a simple API key approach - just include your key in the x-api-key header of every request. This is faster and easier than OAuth flows while remaining secure.

Best Practice: Request separate API keys for your Production and Beta environments. This allows you to test integrations safely without affecting live data, revoke keys independently if needed, and track API usage by environment.

Getting Started: Contact the eveXso team to receive your API keys and endpoint details. Our Quick Start Guide and API Playground provide complete implementation examples once you're set up.

scienceIs there a test environment available for API development?

Yes. eveXso provides a dedicated Beta environment for testing and development, completely separate from Production.

Why this matters: Testing in Beta before switching to Production is strongly recommended. It helps you avoid disruptions to live operations, validate data mappings, and catch edge cases before they affect real orders.

scheduleHow long does it take to build an eveXso integration?

Most developers make their first successful API call within 30 minutes. A basic integration covering products, orders, and inventory typically takes 1-2 weeks for a solo developer.

• Day 1: Authentication and master data (products, customers)
• Week 1: Orders flowing to warehouse, basic polling
• Week 2: Fulfillment data syncing back, testing edge cases
• Week 3+: Advanced features (ASN, reconciliation, SSCC labels)

Real Examples: Self-integrated platforms like AS400 (D'Orsogna) and Business Central (MM Plastics) were completed in days and generate near-zero support tickets.

inventory_2How do I sync products and inventory with eveXso?

The inventory API uses an "upsert" operation - it automatically creates new records if they don't exist or updates existing ones if they do. This makes synchronization simple and reliable.

What you can sync: Product master data (SKU, description, dimensions, weight), tracking types (serial/batch/date), packaging units (inner, case, pallet), and warehouse-specific settings. Each aspect is managed through dedicated API endpoints detailed in our Quick Start Guide.

sync_altHow does order data flow between my ERP and eveXso?

eveXso uses a push-pull hybrid model:

• PUSH →Send orders to eveXso when they're created in your ERP (push model)
• ← PULLPoll the update endpoints every 60-120 seconds to get fulfillment data back (pull model)

What comes back: Fulfilled orders (with serial/batch numbers), received POs, inventory adjustments, and pack movements - everything your ERP needs to stay synchronized.

editCan I update an order after it has been sent to eveXso?

Yes. The import action is idempotent - you can resend order data and the system will detect changes (e.g., new lines added, quantity changes) and apply them automatically.

When updates work: Orders can be modified up until they've been picked or dispatched. Once an order is in progress, the system protects warehouse staff from mid-pick changes that could cause confusion.

qr_code_scannerHow do I handle serial number or batch tracked items?

eveXso supports three tracking modes for inventory items:

• Serial - Unique serial numbers (one-to-one tracking)
• Batch - Batch/lot numbers (one-to-many tracking)
• Date - Batch + expiry date tracking (for food, pharma)

When processing orders or receipts for tracked items, the API requires valid serial/batch numbers and date codes. This ensures complete traceability throughout the warehouse - crucial for warranties, recalls, and regulatory compliance.

verifiedDoes eveXso support retailer compliance like SSCC labeling?

Yes. eveXso natively generates GS1-compliant SSCC labels and Advanced Shipping Notices (ASNs) for major retailers worldwide. This is built-in, not an add-on.

What's included:

• Automatic SSCC generation for pallets and cartons
• GS1-128 label printing with all required data elements
• EDI/XML ASNs in retailer-specific formats
• MLOR (Minimum Life on Receipt) contract enforcement
• Batch and expiry date validation before dispatch

The API also supports the Contracts API to enforce minimum shelf-life requirements automatically, preventing shipments that don't meet retailer standards from leaving the warehouse.

compareHow do I ensure my ERP inventory matches the WMS?

eveXso provides a dedicated Reconciliation API that runs an 8-step comparison workflow:

1. Captures a snapshot of both systems at the same moment
2. Accounts for "in-flight" transactions (picks in progress, receiving)
3. Identifies true variances (excludes temporary differences)
4. Calculates adjustment quantities needed to balance
5. Can auto-generate adjustment transactions (with approval)

Time Savings: Manual reconciliation typically takes 2-4 hours per week. The Reconciliation API completes the entire process in under 60 seconds and provides a detailed variance report showing exactly what changed and why.