17TRACK Parcel Tracking

Track parcels using the 17TRACK Tracking API v2.2. Stores everything in a local SQLite database — no external dependencies beyond Python 3 stdlib.

Requirements

• - TRACK17_TOKEN — your 17TRACK API token (sent as the 17token header). Configure it in ~/.clawdbot/clawdbot.json:

CODEBLOCK0

Or export TRACK17_TOKEN in your shell.

Data Storage

Data lives under <workspace>/packages/track17/ where <workspace> is auto-detected from the skill installation path (parent of the skills/ directory). Override with TRACK17_DATA_DIR or TRACK17_WORKSPACE_DIR.

Quick Start

CODEBLOCK1

If carrier auto-detection fails, specify one: INLINECODE9

Common Commands

Webhooks (optional)

17TRACK can push updates instead of polling. Prefer polling (sync) for simplicity — webhooks are only needed if you want real-time updates.

CODEBLOCK2

Set TRACK17_WEBHOOK_SECRET to verify webhook signatures.

Daily Reports with Auto-Cleanup

The scripts/track17-daily-report.py script syncs all packages, auto-removes delivered ones, and prints a formatted status report to stdout. It uses the same path resolution and env vars as the main script — no hardcoded paths or external config files.

CODEBLOCK3

Agent Guidance

• - Prefer sync (polling) over webhooks unless the user explicitly wants push updates — it's simpler and doesn't require a server.
• After adding a package, run status to confirm the carrier was detected and tracking data is available.
• When summarizing, prioritize actionable items: delivered/out-for-delivery, exceptions, customs holds, carrier handoffs.
• Delivered packages are automatically cleaned up by the daily report. For ad-hoc checks, use sync then list.
• Never echo TRACK17_TOKEN or TRACK17_WEBHOOK_SECRET — these are secrets.