API Reference

Introduction

eHub is built to help systems optimize order fulfillment with powerful API functionality. Key features include checking shipping rates, purchasing labels, generating manifests, and consolidating orders from multiple ecommerce platforms.

API Overview

The eHub API follows REST principles, making it accessible and easy to use through standard HTTP methods. This guide will walk you through available endpoints, request and response formats, and best practices to help you get the most out of the API.

Supported Request Body Content Types

The eHub API supports multiple content types for request bodies, ensuring flexibility and compatibility with different data formats. Ensure the Content-Type header in your requests matches the format of your request body.

• Accepted Content Types:
  • application/json
  • application/xml
  • application/x-www-form-urlencoded

Depending on the endpoint, the required content type may vary. Check the corresponding endpoint documentation for correct usage.

Rate Limiting and Throttling

The eHub API is optimized to handle high volumes of requests with minimal rate limiting or throttling.

While no strict caps are enforced, for optimal performance, it's recommended to limit parallel requests to a maximum of 10 per API token. Following this guideline helps ensure efficient operation and system reliability.

By following these guidelines, you can ensure the best performance and reliability when using the eHub API.