ShippyPro vs TrackingMore

ShippyPro 64

OpenAPI 3.1 files for v1 (55 operations, 119 schemas) and v2 (17 operations), loaded by the reference at api.shippypro.com/docs (25). api.shippypro.com/llms.txt returns 404, the main site's robots.txt disallows /llms.txt so it was not requested, and no Markdown docs were found (0). v1 descriptions state purpose, how to test and known traps, such as GetTracking not being meant for bulk use (14 of 20). Required fields are marked, but the v1 file has 14 enums in all, LabelURL is a string or an array, delivery_days a number or a string, and carrier options are free name and value pairs (9 of 15). 812 examples in the v1 file. v1 error responses are one line per status code with no body schema, and v2 documents RFC 9457 problem types (10 of 15). Versions are in the path, v1 and v2. No changelog was found (6 of 15).

TrackingMore 31

No OpenAPI or similar file was found in the docs, the SDK repositories or a search, and the reference at trackingmore.com/docs renders by script so its schemas were not read (0 of 25). No llms.txt or Markdown docs (0). The official SDK READMEs give one line per call, and the support centre explains when to pair create with get or a webhook and that the create response carries the result (8 of 20). Field names and the required tracking_number and courier_code appear in the SDK examples, with no types, enums or constraints readable (5 of 15). Examples in seven SDK languages and a table of HTTP and meta codes with messages (12 of 15). v4 in the path with v2 and v3 still served, and the support centre says there is no changelog for switching versions. No dated API changelog was found (6 of 15). 0 + 0 + 8 + 5 + 12 + 6 = 31.

ShippyPro 51

API keys are created in the panel, several per account, in three types (Full Access, Maps, PII Excluded), and v2 answers 401 for a revoked key. No expiry or rotation was found. The help centre still describes Basic auth with the key as username (22 of 30). The Maps and PII Excluded types narrow a key, but there is no read-only key and no confirmation step for label creation or voiding. The Generic carrier allows tests without a real shipment (8 of 20). Tracking messages and marketplace order text come from third parties, and no guidance on untrusted content was found. Requests are screened for script-like strings (3 of 15). The panel has API logs with requests and responses, an API error history and webhook logs (10 of 15). The site footer states ISO 27001 and SOC 2 Type II, with no certificate, report or trust page found. security.txt was not requested because robots.txt disallows the path. No bug bounty or disclosure policy was found (8 of 20).

TrackingMore 31

One API key in the Tracking-Api-Key header, shown once, at most four per account, deleted in the web app. No scopes or expiry (20 of 30). No read-only key or least-privilege mode, and delete is one call (4 of 20). Tracking checkpoints are carrier text returned to the model, and no guidance was found (3 of 15). A webhook notification log exists in the web app; no log of API calls or key use was found (4 of 15). No security.txt (404), no security page on trackingmore.com, no certification, bug bounty or disclosure policy found. The CWILL privacy policy points to a trust site that was not read (0 of 20). 20 + 4 + 3 + 4 + 0 = 31.

ShippyPro 5

No x402, MPP or L402 (0). The self-serve plans have public monthly prices, but the pricing page marks them UI only and lists API access under Enterprise at a custom price through sales (0). The terms describe a 14-day, 30-order trial with no card. The help centre says APIs are activated by sales on an Enterprise plan, so we could not establish that a trial account can call the API, and give part credit (5 of 20). A person signs up in a browser and sales activates the API (0).

TrackingMore 23

Read with the hosted rubric. No x402, MPP or L402 (0). The API page gives a from price of $0.03 a tracked order and three unlabelled figures, and the pricing page's plan prices render by script, so per-unit pricing is partly public (8 of 20). A Free plan and a 14-day trial are offered, and whether a card is asked for was not established (15 of 20). A person signs up in a browser and generates the key there (0). 0 + 8 + 15 + 0 = 23.

ShippyPro 46

Scored on the REST API. v1 report calls take date ranges and switches such as IncludeItems, with no field selection, and v2 lists take pageSize up to 100 (12 of 25). v1 lists have date filters and no pagination. v2 has cursor pagination and filters by carrier and country (10 of 20). v1 mixes HTTP status codes with 200 responses carrying Status 2, though ErrorType and ErrorSuggestion name a cause and a fix. v2 errors are application/problem+json with field pointers (12 of 20). No idempotency key on Ship, Edit or VoidShipments. v2 accepts Idempotency-Key on POST and DELETE and answers 409 on a mismatched replay (7 of 20). Ship has eight required parameters and needs a CarrierID from the panel or GetCarriers. No official SDK was found on the pages read, though the API page's FAQ mentions SDKs (5 of 15).

TrackingMore 54

trackings/get filters by tracking numbers, courier and created date range, and batch create takes 40 at once. No field selection was found, and the unread reference may document more (10 of 25). Date and courier filters exist; pagination parameters were not found in what was read (8 of 20). Every response carries an HTTP code and a meta code with a message, such as 4121 for an undetected courier and 4190 for a reached quota (14 of 20). No idempotency key. A repeated create is rejected with 4101, so the write is safe to retry, and delete and retrack take ids (10 of 20). Create needs only tracking_number and courier_code, detect is free, and official SDKs cover seven languages (12 of 15). 10 + 8 + 14 + 10 + 12 = 54.

ShippyPro 25

No API changelog or dated release notes were found. Both OpenAPI files were last modified on 8 October 2026 per their HTTP headers, and the v2 file reads as recent work, so we give half for recency on that metadata alone (15 of 30). No dated entries in the last 90 days (0). Closed service with no changelog. Support runs through tickets, email and chat, the SLA sets response times, and the status page is updated daily (7 of 15). No official SDK or MCP registry entry was found (0). The contract is current OpenAPI 3.1 with examples (3 of 10).

TrackingMore 19

Read as a closed service. No dated API change was found. The SDKs were last pushed between February and December 2024, the support articles are dated 2023 and 2024, and the reference is undated (0 of 30). No releases or dated entries in the last 90 days were found (0). Support by email and chat with a help centre; GitHub issues were not read (6 of 15). Seven official SDKs exist but none has changed since December 2024 (10 of 15). The Node SDK has tests and no CI workflow (3 of 10). 0 + 0 + 6 + 10 + 3 = 19.

ShippyPro 70

Read with the hosted lines and scored on the v1 REST API, where rates, labels and tracking live. Statuspage at status.shippypro.com with a component for ShippyPro API & Webhooks and one per carrier (20). From 11 July to 8 October 2026 no entry names the API. A platform login problem ran for 3 hours 6 minutes on 18 September, marked critical, SMS one-time codes went unsent from 29 August to 3 September and from 19 September to 5 October, and one carrier's label creation was marked critical on most days, some for several days (Asendia from 20 to 31 August). We read that as one major, as for other listings in this category (10 of 30). 20 requests every 10 seconds (15). v1 documents the 429 and nothing more, and Ship takes no idempotency key. The help centre suggests spreading calls over several IP addresses. v2 documents Retry-After, rate-limit headers and Idempotency-Key, but covers no shipping call (5 of 15). The SLA commits to 99.5 per cent a month with service credits (10). GA (10).

TrackingMore 65

Read with the hosted lines and scored on the REST API v4 at api.trackingmore.com. status.trackingmore.com is a hosted status page with uptime and a status update history (20). Its figures and history render by script, so the 90 days could not be read; the static text says there were no updates in the last 7 days (5). Rate limits are published per endpoint, 3 requests a second on trackings/create and 10 a second elsewhere, per account (15). The support centre says a 429 means the application should stop and wait 120 seconds, and a repeated create answers meta code 4101 rather than creating a duplicate. No Retry-After and no idempotency key (10 of 15). No SLA document was found. The Enterprise plan lists 99.99 per cent API uptime as a feature and the API page claims 99.9 per cent uptime, which is marketing rather than a published SLA (5 of 10). v4 is the current version and not marked beta (10). 20 + 5 + 15 + 10 + 5 + 10 = 65.