Start with five real rows.

Download collection Download environment template

1. Import both files into a current Postman desktop app. The environment starts with an empty key and ALLOW_LIVE_REQUESTS=false. No request runs on import.
2. Create an account, finish setup and copy your saved key from API keys. Set PRIZEPICKS_API_KEY only in your private local environment; do not publish an environment containing a real key.
3. Set TASK_CONTEXT to a short, non-sensitive description of your current task. It is sent as X-User-Request and retained for 35 days. Leave out private prompts and personal information.
4. Review a single request, set ALLOW_LIVE_REQUESTS=true, then press Send. Start with coverage and the credit policy. Set the flag back to false when finished.
5. For result records, supply RESULTS_DATE, a US Eastern game date. For a historical board, supply AS_OF, an explicit recorded timestamp with timezone. Both start empty and their requests stay skipped until configured.

The collection contains GET requests for coverage, multi-league projections, priced comparisons, results, historical boards and credit costs. Data requests use limit=5. There is no automatic pagination, polling, retry loop, purchase or checkout action. Redirect following is disabled. Use a current Postman runtime that supports pm.execution.skipRequest(); review imported scripts before running them.

Live reads may consume your account allowance. Five rows are a small response, not a promise that every endpoint costs the same. Inspect X-Usage-Unit, X-Credits-Cost and X-Credits-Remaining, and use the credit calculator. A plan gate or empty result stays visible.

Download the source bundle · Python quickstart · Node.js quickstart · Jupyter notebook

Maintained by PP API Inc. and published on our own domain. The bundle includes a README and MIT license for example code, with no credentials or saved notebook output. Data access remains subject to the service terms. Quickstarts default to five rows and one request; without a key they explicitly use fictional demo records.

Each client has its own request budget and access requirements; review its guide before scheduling it. Preserve source timestamps, grading status, tier, period and unknown values. Older game logs are not proof that PrizePicks offered a historical line.

The hosted endpoint uses Streamable HTTP in its stateless JSON form. Public search and fetch are available without a key; authenticated data tools use the same account-issued bearer key as REST. Data tool calls take a short non-sensitive user_request argument describing the current task.

Use the setup instructions for Claude, Gemini, Lovable or ChatGPT. Client capabilities differ; use REST from your application backend and keep keys out of browser bundles. A registry listing is not required to connect to the endpoint.

The dated coverage report links its JSON evidence and query methodology. It separates recorded line history from box-score history and distinguishes full coverage from a partial recovered snapshot.

For provider evaluation, read the Parlay API comparison alongside the current endpoint reference. This is an independent data service, not an official PrizePicks API.