Easyship is automatable through its API

Easyship is automatable today through its public REST API. The authentication reference says every request sends Authorization Bearer and an API access token created in the dashboard under APIs & Webhooks. Production tokens start with prod_ and sandbox tokens start with sand_. The token's scopes decide which endpoints answer. The reference lists shipments, rates, labels, pickups, addresses, tracking, billing, and insurance. The webhooks guide says Easyship POSTs shipment, label, tracking, batch, and credit events to an HTTPS endpoint that must return 2XX. The signature header is X-EASYSHIP-SIGNATURE, a JWT checked with a webh_ secret. Failed deliveries retry 30 times, one minute apart, and then the webhook is deactivated. The plans page says the Free plan includes no Advanced API calls and bills those calls as you go, while Plus and higher plans include a quota and charge overage after that. Easyship also documents an official MCP server at https://mcp.easyship.com/mcp. The guide lists 25 tools on API version 2024-09 for rates, shipments, labels, pickups, address validation, billing, and analytics. Remote clients send the same bearer token. A missing scope returns 403 for that tool. The easyship/easyship-mcp-plugin README says label actions spend real credits and that MCP actions have no separate test environment. ChatGPT can connect by signing in with an Easyship account. Connector catalogs for Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API and the MCP server each score 7. The API is the best path because it includes sandbox tokens and webhooks, and the MCP server is a proxy over a subset of the same API.

Best path today: api · Overall automatability: 7/10