Shipping
Connect ShipStation
Your application calls one EchoRelay URL. When ShipStation changes its API, you update the mapping, not your application.
How ShipStation signs requests
An API key in the API-Key header on every call.
Can you connect it today?
Yes. Add an API-key-in-a-header credential with the header name API-Key.
A sample mapping
Your application sends the first request below. The mapping turns it into the body of POST /v2/rates, shown second.
Your request
{
"shipmentId": "se-123",
"carriers": [
"se-123890"
]
}
What ShipStation receives
{
"shipment_id": "se-123",
"rate_options": {
"carrier_ids": [
"se-123890"
]
}
}
The mapping
{
"$schema": "https://schemas.echorelay.dev/transform/mapping/v1.json",
"root": {
"type": "object",
"id": "root",
"properties": {
"shipment_id": {
"type": "field",
"id": "shipment",
"path": "shipmentId"
},
"rate_options": {
"type": "object",
"id": "rate-options",
"properties": {
"carrier_ids": {
"type": "field",
"id": "carriers",
"path": "carriers"
}
}
}
}
}
}
The grammar, the answer mapping and the dry run are in the mapping docs.
What you bring
This is not a ready-made connector. You bring a sample request or ShipStation’s OpenAPI document, you or your agent write the mapping, and we run the integration you define.
ShipStation facts on this page were read 2026-10-29 from ShipStation API authentication. Another service? Check it here.
Connect everything. Deploy nothing.
No credit card required.