OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
Shipments return structured shipping records.
ShipStation V2 shipment listing ↗
List Shipments · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
Paged requests require partitioning when page × page_size would exceed 10,000.
ShipStation V2 shipment listing ↗
Pagination Limits · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
Created/modified windows and shipment status/tag filters are documented; batch filters override others.
ShipStation V2 shipment listing ↗
Query Parameters · Checked 2026-10-16
Access cost barrier -
-
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges.
ShipStation V2 shipment listing ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
A customer V2 key is documented; broad chosen-third-party eligibility and distribution terms were not established.
ShipStation product-specific authentication and sandbox ↗
Platform API keys versus standalone API keys · Checked 2026-10-16
Downstream permission -
-
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
The reviewed technical documentation does not establish contractual permission for the declared downstream processing.
ShipStation V2 shipment listing ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
POST creates shipments and PUT updates a shipment by ID.
ShipStation V2 shipment operation reference ↗
Create shipments; Update a shipment · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
The guide describes building shipping capabilities into customer applications/services.
ShipStation V2 product model and finite label retention ↗
Shipping API Features · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
modified_at_start/end and ordering support bounded changed-record polls.
ShipStation V2 shipment listing ↗
Query Parameters · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
Default 200/minute, 429 and Retry-After recovery are published; carriers have separate limits.
ShipStation V2 usage limits ↗
Rate Limit; Handling Limits Gracefully · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
Modified-time filters identify shipment changes; cancelled state is not proof of all hard deletes.
ShipStation V2 shipment listing ↗
Query Parameters · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
Overlapping modified-time queries recover current records within filtered selections; no retained event checkpoint established.
ShipStation V2 shipment listing ↗
Query Parameters; Pagination Limits · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
Authorized shipment JSON supplies an external record copy.
ShipStation V2 shipment listing ↗
Example Request & Response · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
No retrieval window or export charge at cancellation is established by these technical sources.
ShipStation V2 shipment listing ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
Portable shipment records; full sales orders and indefinitely retained label documents are not established.
ShipStation V2 product model and finite label retention ↗
Common Terminology · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
V2 is documented for application/service shipping integrations.
ShipStation V2 product model and finite label retention ↗
Getting Started; Shipping API Features · Checked 2026-10-16
Rights to custom logic -
-
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
Rights to native workflow artifacts and independent execution are not established.
ShipStation V2 shipment listing ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Platform customers generate a V2 API key in account settings, with one active V2 key at a time. Standalone API customers use a separate account/key route; platform accounts have no sandbox.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
GET /v2/shipments uses page/page_size and created/modified date windows. Filtering by batch_id overrides several other filters, so it cannot be treated as an additive delta constraint.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| ShipStation platform customer V2 API key | API key | Customer | No | customer settings v2 api key; one active key; platform production only, no sandbox | 2026-10-16 |
| Standalone ShipStation API product key | API key | Customer | No | standalone api account formerly shipengine; separate plans and test sandbox keys | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Fixed API charges and the lowest fully entitled platform package were not established. The current guide publishes 200 requests/minute and Retry-After; carrier/provider throttles are separate.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
POST /v2/shipments creates shipment records; PUT /v2/shipments/{shipment_id} updates them. external_shipment_id need not be unique and is not an idempotency key; label purchases and carrier notifications have separate side effects.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
modified_at_start/end supports overlapping polls with bounded pages. Cancelled shipment state is visible, but hard-delete capture and retained event replay remain unresolved.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. Modified-time filters identify shipment changes; cancelled state is not proof of all hard deletes. | ShipStation V2 shipment listing ↗Query ParametersChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. Overlapping modified-time queries recover current records within filtered selections; no retained event checkpoint established. | ShipStation V2 shipment listing ↗Query Parameters; Pagination LimitsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Shipment JSON supports a portable scoped record copy. Original sales orders are not fully represented, and label documents have finite retention, requiring their own prompt archival path.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customer apps can implement external shipping rules. Native automation artifact rights and independent execution are not established (production API calls can incur real shipping costs).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. Shipments return structured shipping records. | ShipStation V2 shipment listing ↗List ShipmentsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. Paged requests require partitioning when page × page_size would exceed 10,000. | ShipStation V2 shipment listing ↗Pagination LimitsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. Created/modified windows and shipment status/tag filters are documented; batch filters override others. | ShipStation V2 shipment listing ↗Query ParametersChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. A customer V2 key is documented; broad chosen-third-party eligibility and distribution terms were not established. | ShipStation product-specific authentication and sandbox ↗Platform API keys versus standalone API keysChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges. | ShipStation V2 shipment listing ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. The reviewed technical documentation does not establish contractual permission for the declared downstream processing. | ShipStation V2 shipment listing ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. POST creates shipments and PUT updates a shipment by ID. | ShipStation V2 shipment operation reference ↗Create shipments; Update a shipmentChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. The guide describes building shipping capabilities into customer applications/services. | ShipStation V2 product model and finite label retention ↗Shipping API FeaturesChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. modified_at_start/end and ordering support bounded changed-record polls. | ShipStation V2 shipment listing ↗Query ParametersChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. Default 200/minute, 429 and Retry-After recovery are published; carriers have separate limits. | ShipStation V2 usage limits ↗Rate Limit; Handling Limits GracefullyChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. Authorized shipment JSON supplies an external record copy. | ShipStation V2 shipment listing ↗Example Request & ResponseChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. No retrieval window or export charge at cancellation is established by these technical sources. | ShipStation V2 shipment listing ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. V2 is documented for application/service shipping integrations. | ShipStation V2 product model and finite label retention ↗Getting Started; Shipping API FeaturesChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. Rights to native workflow artifacts and independent execution are not established. | ShipStation V2 shipment listing ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. Portable shipment records; full sales orders and indefinitely retained label documents are not established. | ShipStation V2 product model and finite label retention ↗Common TerminologyChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Lowest-plan API entitlement and fixed access fees
- Complete attachments/history and deletion recovery
- Native workflow rights and cancellation retrieval
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.