##  [nShift Go Documentation (2026)](/nominees/2026/nshift-go-documentation) 

 ![Screenshot of nShift Go Documentation's Home page header](/sites/default/files/styles/nominees_image/public/2026-10/Screenshot%202026-10-28%20at%2010.45.57.png?itok=siEICYV0)

 

 

Owner

nShift



 

 

 [ Visit the portal ](https://docs.nshiftgo.com) 

 

 

## NOMINEE OVERVIEW

nShift Go is the shipping API nShift built for platform builders and marketplaces: one API for carrier selection, shipment booking, labels, pickup points and tracking, embedded under the platform's brand, with access to 200+ carriers, and with potential expansion into nShift's complete network of 1,000+ carriers in 190+ countries. The nShift Go Documentation is its developer portal, written for developers and for the AI agents they work with. The guides take a new integrator from sign-up to a first booked shipment through a chain of "Next step" pointers, with flow diagrams for authorization, account setup, configuration and billing. The reference is generated from the OpenAPI 3.1 specification the API publishes, and each of its 119 operations has a summary and a description. Every page is also served as plain text, the portal publishes an llms.txt index, and the API itself serves an llms.txt and a single-file llms-full.txt reference, so an AI agent can load the whole API in one pass.

## NOMINATION RATIONALE

### 1) BEST API PRODUCT MICROPORTAL INSIDE A DEVELOPER PORTAL

**Why is this category a strong match?**

nShift publishes seven APIs at [nShift APIs](https://nshift.com/apis), each documented alongside the product it belongs to. nShift Go is built for a different reader profile: platform builders and marketplaces that embed shipping under their brand, often on behalf of many merchants, and pay per use. A team like that has to understand Go's usage-based billing, its affiliate route and its two-level token model before it builds anything, so Go has a dedicated portal with its navigation, onboarding, billing page, authentication guide and reference in one place. nShift's main API overview and the Go product page both link into it, and a platform team can learn what Go does, what it costs to run and how to integrate it without switching sites.

  
**In what ways does your portal shine in this category?**

- **Concepts before endpoints.** A Key concepts page defines the shipping vocabulary, from Account and Carrier Definition to Shipment Channel and PUDO point, so a platform team without logistics experience can follow the reference.
- **One page of conventions.** The REST guidelines page sets out how the API behaves throughout: RFC 7807 error responses with field-level violations, cursor-based pagination, naming conventions and JSON schema validation.
- **Billing explained where it applies.** Usage-based billing has a page with a flow diagram, and Report endpoints at company and account level show consumption and cost as they accrue.
- **Scope kept to the product.** Sign-up, billing, the Company and Account token levels and all 119 operations belong to Go, so everything an integrator reads in the portal applies to the product they are integrating.

### 2) BEST REIMAGINED ONBOARDING EXPERIENCE IN A DEVELOPER PORTAL

**Why is this category a strong match?**

A platform team that is new to shipping meets an unfamiliar vocabulary, and its first test booking could reach a real carrier. The Go portal answers both before the first line of code. The guides read end to end, from sign-up to a first booked shipment, and every carrier connection starts in a staging mode by default, inside the same API, so a team can build and test its whole booking flow with no live carrier communication, then switch the connection to production. The portal also treats the developer's AI coding assistant as a reader in its own right: the journey is published in forms an AI client can load directly, so a developer can hand the portal to an assistant and both work from the same material.

  
**In what ways does your portal shine in this category?**

- **A guided path.** The core guides end with a "Next step" pointer, chaining sign-up, authentication, account management and configuration to the first shipment booking.
- **Flow diagrams first.** Diagrams show how authorization, account setup, configuration and billing fit together before the reader meets an endpoint.
- **Credentials explained once.** The Company token for setup and the Account token for daily operations are introduced with a step-by-step flow and a full table of access scopes.
- **Room to make mistakes.** Carrier Definitions start in STAGING, a mock-event call tests webhooks before real traffic, and error responses identify the field and the problem ("Missing Shipment Channel configuration") instead of returning a bare status code.
- **An AI client as a first-class reader.** Plain-text pages, an llms.txt index and a single-file llms-full.txt reference let an agent load the API in one pass.



 

 

2026