integrating-with-wms

To integrate with a WMS API, you call /api/v1 endpoints for containers, orders, inventory, items, audits, and ASNs using camelCase payloads. This approach dynamically fetches the current API surface from the source repository to align with evolving schemas.

Dynamic API discovery is the process of reading endpoint routing and schemas directly from source repositories. It ensures your WMS integration adapts to evolving API surfaces by fetching the current structure of core entities like containers, orders, and ASNs.

You map WMS API endpoints by reading routing configurations from the source repository to link core entities like containers, orders, items, inventories, audits, and ASNs to their respective schemas and response models.

Yes, you need to use camelCase payloads when calling /api/v1 WMS endpoints. Adhering to camelCase conventions and the /api/v1 base path ensures your backend integration correctly handles common response models for containers and inventory.

Yes, you can validate your WMS API integration by dynamically fetching the current API surface from the source repository. This allows you to plan and verify that your calls to containers, orders, and ASNs endpoints match the latest schemas.

A limitation of source repo API discovery is that it requires backend source repository access to fetch current WMS endpoint routing and schemas. If the repository is unavailable, you cannot dynamically validate the /api/v1 integration structure.