Shipping IO

How to integrate Shipping IO with Webflow

Shipping IO provides no public API documentation. The integration depends entirely on obtaining private API access.

The only available method is Custom API integration using serverless middleware to connect Webflow's e-commerce webhooks with Shipping IO's API. This requires mid-to-senior developers.

Custom API integration

Contact Shipping IO to request private API documentation before development. Once done, confirm the following:

• API endpoint URLs
• Authentication methods
• Webhook support
• Rate limits and usage restrictions
• Customer references with similar Webflow implementations

Custom API integration offers maximum control but requires significant resources.

Webflow API configuration

Configure the ecommerce_new_order webhook to send order data to your serverless endpoint at checkout. This webhook delivers shipping addresses, line items, and customer information without polling.

Authenticate using Site Tokens for single-site integrations, OAuth 2.0 for multi-site applications, or Workspace Tokens for workspace-level access and store credentials in environment variables. Make sure that you use Webflow's v2 API for all implementations. See the v1 deprecation notice for migration details.

Key Webflow endpoints include the following:

• GET /v2/sites/:site_id/orders/:order_id — retrieve order details
• PATCH /v2/sites/:site_id/orders/:order_id/fulfill — update fulfillment status
• Write tracking data: shippingProvider, shippingTracking, shippingTrackingURL

Serverless deployment

Deploy middleware on platforms that Webflow developers commonly use. These include the following:

• Vercel Functions offers single-command deployment with GitHub integration
• Netlify Functions provides a straightforward setup with 125,000 free invocations monthly
• Cloudflare Workers provides edge computing for global applications.

Implementation pattern

Structure code in three layers:

• Layer 1 (Webhook receiver) validates webhook signatures using HMAC SHA256, extracts order data, and triggers async processing.
• Layer 2 (Shipping API integration) calls shipping provider endpoints for rates or labels. Store API credentials separately in environment variables. Implement retry logic with exponential backoff to meet Webflow's 60–120 requests per minute limit.
• Layer 3 (Webflow update) writes tracking information back via the Fulfill Order API, maintaining platform synchronization.

What you can build

You can build the following with Shipping IO once integrated with Webflow. However, the integrations require API documentation from Shipping IO.

• Automated order fulfillment workflow: Serverless middleware receives Webflow orders via webhooks, sends data to Shipping IO for label generation, and writes tracking numbers back automatically.
• Real-time shipping rate calculator: Display carrier rates at checkout based on destination and cart weight. Call Shipping IO's rate API from serverless functions, and inject rates via a custom code embed.
• Custom shipping rules engine: Apply policies such as free-shipping thresholds, dimensional-weight calculations, and handling fees.
• Multi-carrier tracking consolidation dashboard: Build a custom Webflow CMS page that aggregates shipment status across all carriers using Shipping IO's unified tracking API.