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, which is acquired using Basic Authentication.
Step 1: Generate API Token
Use the following endpoint:
GET /api/v2/token
Requires Basic Authentication
Returns a JWT token
Optional Header:
X-Proxy: Allows acting on behalf of another user (if permitted)
Response Example:
eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9...
👉 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: Marketplace-Specific Tokens (if required)
For marketplace related API calls retrieve an access token.
Amazon Selling Partner API (SP-API) Access Token
GET /api/az/access-token?marketplace=US
Response:
{
"access_token": "string",
"expires_in": 3600
}
Walmart API Access Token
POST /api/wm/v3/token
Response:
{
"access_token": "string",
"token_type": "string",
"expires_in": 0,
"refresh_token": "string"
}
MCP Server
The ScanPower MCP server is available at https://mcp.scanpower.com
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
When connecting to the server use the URL above and your ScanPower email as your OAuth Client ID.
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.
Event-driven notifications via Webhooks
To receive API notifications via webhooks, please refer to the Webhook Documentation: