Overview
This article provides an summary of the different ways to integrate your business with the ScanPower platform. ScanPower provides a public API and AI tool integration via our MCP Server. Whether you are integrating an ERP, OMS, or WMS, ScanPower offers easy access to your Amazon FBA and Walmart WFS shipments and related objects. Most of the application functionality is available through the API.
Please Note: The ScanPower API is available to users with Enterprise Pro, 3PL Enterprise, and Enterprise Multi-store plans.
API Documentation
Authentication
All ScanPower API requests require a Bearer token. In v3, the ScanPower token is the only token you need. Amazon and Walmart marketplace tokens are handled by ScanPower behind the scenes, so there are no separate marketplace token calls.
Step 1: Generate an Access Token
Use the following endpoint:
GET /api/v3/auth
Requires Basic Authentication (your ScanPower username and password)
Returns an access token and its expiration
Optional Header:
X-Proxy: A client user ID. Generates a token that can be used to make calls on behalf of that user (if permitted)
Response Example:
{
"access_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9...",
"token_type": "bearer",
"expires_in": 0,
"scope": "string",
"state": "string"
}👉 This token must be included in all subsequent API requests.
Step 2: Use Bearer Token in subsequent calls
Include the token in headers:
Authorization: Bearer <your_token>
Step 3: Get a Refresh Token (optional)
For long-running integrations, request a refresh token so you can get new access tokens without sending your ScanPower login each time. The v3 API implements a subset of OAuth 2.0 for this.
Call the endpoint below using Basic Authentication (the same login as Step 1):
POST /api/v3/auth
Content-Type: application/json
{
"grant_type": "client_credentials"
}
The response includes an access_token and a refresh_token. Store the refresh token securely.
Step 4: Use the Refresh Token to Get a New Access Token
When your access token expires, exchange the refresh token for a new access token:
POST /api/v3/auth
Content-Type: application/json
{
"grant_type": "refresh_token",
"refresh_token": "<your_refresh_token>"
}
See the Auth section of the API documentation for full details.
MCP Server
The ScanPower MCP server is available at https://mcp3.scanpower.com/mcp
The MCP server works with popular LLMs such as Claude Code, Claude Desktop, Visual Code Studio, and Github Copilot. Use it to explore the ScanPower API and build tools and artifacts conversationally.
Connecting to the MCP Server
Add https://mcp3.scanpower.com/mcp as a remote MCP server (custom connector) in your client, then sign in with your ScanPower credentials when prompted.
To see some examples workflows and use cases, prompt the client:
ScanPower MCP get resources
Response
There are 4 resources available. Let me fetch all of them:
Used ScanPower MCP integration
Here's a summary of all 4 resources available from the ScanPower MCP:
1. pack-first-flow (docs://pack-first-flow)
A 13-step reference guide for the Pack First FBA inbound workflow — used for SPD/LTL shipments where items are prepped and boxed before Amazon destinations are known. Key stages: Create Plan → Label → Box → Set Packing → Placement → Delivery Window → Transportation → Tracking → BOL.
2. pack-later-flow (docs://pack-later-flow)
A 14-step reference guide for the Pack Later FBA inbound workflow — used for LTL pallet shipments where box contents are declared after destinations are known. Same general structure as pack-first but with placement happening before boxing. Also includes a cancel_inbound_plan step.
3. print-item-label (docs://print-item-label)
Reference doc for the print_item_labels tool — covers all parameters for items (title, FNSKU, condition, quantity, expiration, lot code) and opts (printer, label size, what to print on the label). Response is a base64-encoded PDF.
4. scanpower-openapi-spec (docs://scanpower-openapi-spec)
The full ScanPower OpenAPI spec — too large to display inline (stored separately). Contains the complete API surface definition for the ScanPower platform.
The agent can expand on any of resources and walk you through the various printing and packing flows.
Using the ScanPower MCP, acting as a prep center:
Call get_proxy_users (proxy: "proxy") and list my clients in a table:
client name, email, and proxy user ID.
For each client, one at a time:
a. Call get_api_token with that client's proxy_user_id to switch into their account.
b. Call get_shipment_history with aggregate=false and interval="90 days" to get one row per FBA shipment.
c. Record each shipment's shipment_confirmation_id (FBA...), shipment name,
destination FC, status, shipping mode, and created/ship date.
When all clients are done, call get_api_token with no proxy_user_id to switch back to my own account.
Show one combined table: Client | Shipment confirmation ID | Name | Destination FC | Status | Mode | Date. Sort by client, newest first. Also list any client whose token or shipment call failed, with the error.
Event-driven notifications via Webhooks
To receive API notifications via webhooks, please refer to the Webhook Documentation: