bullpen polymarket clob price-history¶
Last updated: May 29, 2026
Get price history for a token ID (unauthenticated)
Usage¶
Live Help¶
Get price history for a token ID (unauthenticated)
Usage: bullpen polymarket clob price-history [OPTIONS] <TOKEN_ID>
Arguments:
<TOKEN_ID>
Token ID (condition token; decimal or 0x hex)
Options:
--interval <INTERVAL>
Time interval: 1m, 1h, 6h, 1d, 1w, max
Possible values:
- 1m: 1 minute window (fine-grained data points)
- 1h: 1 hour window (5-minute data points)
- 6h: 6 hour window (30-minute data points)
- 1d: 1 day window (60-minute data points)
- 1w: 1 week window (720-minute data points)
- max: Maximum available history
[default: 1d]
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--env <ENV>
Target environment to connect to (overrides config.toml)
[env: BULLPEN_ENV=]
[possible values: staging, production]
--fidelity <FIDELITY>
Number of data points to return (optional fidelity override)
--config <CONFIG>
Path to a custom config.toml file (overrides $BULLPEN_CONFIG and the default location).
Explicit --config and BULLPEN_CONFIG paths fail closed: if the file is missing, the CLI exits validation instead of silently loading defaults. Credentials still resolve via BULLPEN_HOME, so set BULLPEN_HOME too when isolating a session.
--read-only
Enable read-only mode: blocks all mutating commands
--non-interactive
Suppress interactive prompts; does NOT imply --yes for money-moving commands
[env: BULLPEN_NON_INTERACTIVE=]
-h, --help
Print help (see a summary with '-h')
EXAMPLES:
bullpen polymarket clob price-history --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen polymarket clob price-history [OPTIONS] <TOKEN_ID>
bullpen polymarket clob price-history --help
bullpen polymarket clob price-history --output json
JSON Output¶
Contract: JSON Output Contract.
This command supports --output json, but this generated reference page intentionally does not include a synthetic success schema or example.
Use the live command in your target environment to inspect command-specific success fields. Error output follows the shared JSON output contract linked above.
Schema version: 1 when a command emits schema_version; otherwise treat the current command shape as contract version 1.
Stability¶
Patch releases may add nullable or optional fields. Minor releases may add required fields or increment schema_version. Major releases may remove or rename fields.