Skip to main content
GET /search looks for one piece of text everywhere in your store and returns the matches grouped by type. It is the search behind ⌘K (Ctrl+K on Windows and Linux) in the dashboard, so an integration or an AI agent finds a record the same way you do. Base URL https://api.pocketsflow.com, API key in the Authorization header, like every other endpoint. Available on every plan.

What it matches

Matching ignores case. Text is matched literally: a.b+c finds the email a.b+c@example.com and nothing else. Each group lists up to limit hits, an id match first, then newest first. hasMore: true means more records match: use the list endpoints (GET /orders, GET /customers, …) with their filters to page through them.

The hit

Test mode

A pk_test_ key searches your test data, a pk_live_ key your live data. testMode in the answer says which.

Team members

In the dashboard a team member searches the store they work on, and only gets the types of the areas their teams have: Orders, customers and refunds gives orders, customers and subscriptions; Products and store design gives products; Discounts, upsells and affiliates gives discounts. Owners and admins get everything.

Limits

120 searches per minute per account, on top of the general 600 requests per minute. Past it the API answers 429 with code: "RATE_LIMITED".

MCP

AI agents connected through the MCP server call the same search as the search_store tool.