Skip to main content
Use API keys when your app, backend job, or research pipeline wants a traditional bearer token instead of wallet-based x402 or MPP payments. An API key authorizes stock-pick reads with Authorization: Bearer pk_drip_.... With a PRO or EXPERT subscription, in-window reads are free and uncharged. Without a plan, the same route falls through to pay-per-use and spends your account credits — see Quickstart: x402 and MPP for the wallet-payment path.
1

Create an API key

Sign in to Drip, then create a key from the API keys. Copy the key when it is shown; raw keys are not displayed again.Add or start a subscription from the Billing.
2

Preview the day for free

The quote route needs no auth. Use it to see whether a day has picks before you request it.
3

Read the picks

One UTC day, with your key. PRO readers get the live 7-day window, EXPERT readers get full history.
4

Page back through a range

EXPERT plan. limitDays bounds each page and cursor continues older. Always pass the previous response’s pagination.nextCursor unchanged.

Request examples

More picks in one call

Pass a range instead of a day. limitDays (1-30) sets how many days come back per page and limit sets rows per day, so limitDays=30&limit=500 returns a month of picks in one request.
When more days remain, pagination.nextCursor holds the oldest day returned — pass it as cursor to continue older. Historical subscription reads include prices (entry, current, direction-adjusted returnPct, currency).

Example response

A day in the life of the feed: several sources calling the same names, one with prices attached, one without an attributed post.
A successful query can return picks: [] — an empty day is not an error. asset and assetId are null until the ticker is resolved; use asset.kind for identity, and Company Lookup when you need to resolve one yourself.

Common responses

Keep API keys server-side. Do not ship pk_drip_... keys in browser code, public repositories, or agent traces.