Get Started with Forge
IMPORTANT: Forge is currently in beta and available to select customers. To check eligibility or join the waitlist, contact EasyPost Sales.
This guide outlines essential steps for setting up Forge, including prerequisites, implementation options, and account onboarding.
Before integrating Forge, complete the following steps:
- Account Registration: Contact the EasyPost Sales Team to complete account registration.
- Carrier Account Registration: Upon signing up with Forge, EasyPost-Powered Carrier Accounts are available and can be enabled directly from the Dashboard. For additional carriers, the Bring Your Own Account (BYOA) option allows direct carrier integration.
- Software Requirements: Download an EasyPost Client Library or utilize the REST API with cURL.
- Documentation Review: Review the following EasyPost resources:
- EasyPost Objects to understand the API structure, which is critical for constructing requests and interpreting responses.
- EasyPost API offerings to determine the shipping features to integrate, including shipping label generation, parcel insurance, tracking, scheduled pick-ups, and address verification. Additional tools such as report generation and the Shipping UI Tutorial are also available.
Forge offers two implementation options, allowing platforms to control how postage, fees, and carrier charges are managed. Each implementation type determines the sub account structure and onboarding process.
The Decentralized option is recommended for platforms that require customers to pay for their own labels and services directly through EasyPost,
reducing financial risk and operational overhead. This implementation uses ReferralCustomer
users, which have unique onboarding requirements
detailed in the Decentralized Quick Start Guide.
The Centralized option allows platforms to retain full control over end-user payments by routing all shipping activity through platform-owned carrier accounts and billing. This option enables pricing adjustment for postage and fees but requires platforms to assume responsibility for negative balance liabilities. This implementation uses Child User Sub Accounts, with onboarding requirements detailed in the Centralized Quick Start Guide.
Please visit the Help Center for more information.