flexport-common-errors
Diagnose and fix common Flexport API errors including HTTP status codes, webhook failures, and data validation issues. Trigger: "flexport error", "fix flexport", "flexport not working", "debug flexport API".
- License 许可
- MIT
- 最近更新
- 2026-07-13
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- flexport-common-errors
- tags
- [ "saas", "logistics", "flexport" ]
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Diagnose and fix common Flexport API errors including HTTP status codes, webhook failures, and data validation issues. Trigger: "flexport error", "fix flexport", "flexport not working", "debug flexport API".
- allowed-tools
- Read, Grep, Bash(curl:*)
- compatible-with
- claude-code
03 SKILL.md 正文
Flexport Common Errors
Overview
Quick reference for the most common Flexport API v2 errors. The API returns standard HTTP codes with JSON error bodies containing code, message, and sometimes details fields.
Error Reference
401 Unauthorized — Invalid or Missing API Key
{ "error": { "code": "UNAUTHORIZED", "message": "Invalid API key" } }
Causes: Missing Authorization header, expired JWT token, revoked API key.
Fix:
# Verify key is set
echo $FLEXPORT_API_KEY | head -c 10
# Test with cURL
curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $FLEXPORT_API_KEY" \
-H "Flexport-Version: 2" \
https://api.flexport.com/shipments?per=1
403 Forbidden — Insufficient Permissions
Causes: API key lacks required scope, IP whitelist blocking, sandbox key used on production.
Fix: Check key permissions in Flexport Portal > Settings > Developer. Ensure key scope includes the endpoint you are calling.
404 Not Found — Resource Does Not Exist
{ "error": { "code": "NOT_FOUND", "message": "Shipment shp_xxx not found" } }
Causes: Wrong ID format, resource deleted, using test ID in production.
Fix: List resources first to get valid IDs:
curl -s -H "Authorization: Bearer $FLEXPORT_API_KEY" \
-H "Flexport-Version: 2" \
https://api.flexport.com/shipments?per=1 | jq '.data.records[0].id'
422 Unprocessable Entity — Validation Failed
{ "error": { "code": "VALIDATION_ERROR", "message": "Invalid port code", "details": [...] } }
Common validation failures:
| Field | Issue | Fix |
|---|---|---|
origin_port.code |
Not a valid UN/LOCODE | Use CNSHA, USLAX, DEHAM format |
hs_code |
Wrong format | Use 6-10 digit codes like 8479.89 |
cargo_ready_date |
In the past | Use future ISO date |
freight_type |
Unsupported value | Use ocean, air, or trucking |
incoterm |
Invalid | Use FOB, CIF, EXW, DDP |
429 Too Many Requests — Rate Limited
{ "error": { "code": "RATE_LIMITED", "message": "Rate limit exceeded" } }
Fix: Check response headers and back off:
function handleRateLimit(res: Response): number {
const retryAfter = res.headers.get('Retry-After');
const remaining = res.headers.get('X-RateLimit-Remaining');
console.log(`Rate limited. Remaining: ${remaining}. Retry after: ${retryAfter}s`);
return parseInt(retryAfter || '60') * 1000;
}
500/502/503 — Server Errors
Causes: Flexport internal issue, maintenance window, upstream provider failure.
Fix:
# Check Flexport status page
curl -s https://status.flexport.com/api/v2/status.json | jq '.status'
Retry with exponential backoff for transient 5xx errors. See flexport-rate-limits.
Diagnostic Script
#!/bin/bash
echo "=== Flexport Diagnostics ==="
echo "API Key set: ${FLEXPORT_API_KEY:+YES}"
echo "Key prefix: ${FLEXPORT_API_KEY:0:8}..."
echo -n "API status: "
curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $FLEXPORT_API_KEY" \
-H "Flexport-Version: 2" \
https://api.flexport.com/shipments?per=1
echo ""
echo -n "Status page: "
curl -s https://status.flexport.com/api/v2/status.json | jq -r '.status.description'
Escalation Path
- Run diagnostic script above
- Collect request ID from response headers (
X-Request-Id) - Check Flexport Status
- Contact Flexport support with request ID and error details
Resources
Next Steps
For comprehensive debugging, see flexport-debug-bundle.
04 同仓库更多 Skills
zustand-store-creator
Create zustand store creator operations. Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like "zustand store creator", "zustand creator", "zustand".
zero-trust-config-helper
Configure with zero trust config helper operations. Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like "zero trust config helper", "zero helper", "zero".
zapier-integration-helper
Assist with zapier integration helper operations. Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like "zapier integration helper", "zapier helper", "zapier".
yaml-config-validator
Validate yaml config validator operations. Auto-activating skill for DevOps Basics. Triggers on: yaml config validator, yaml config validator Part of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like "yaml config validator", "yaml validator", "yaml".
xvary-stock-research
Thesis-driven equity analysis from public SEC EDGAR and market data; /analyze, /score, /compare workflows with bundled Python tools (Claude Code, Cursor, Codex).
xss-vulnerability-scanner
Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals. Triggers on: xss vulnerability scanner, xss vulnerability scanner Part of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like "xss vulnerability scanner", "xss scanner", "xss".