Skip to main content
GET
Search specs
Pass the required query parameter as a regular expression. Search applies to the original input text, not the generated specification body.
Use --data-urlencode or your HTTP library’s query encoder so regex characters reach the API intact. Escape regex metacharacters when you intend a literal search. The specs, total, and hasMore envelope uses the same summary format and pagination as list specifications. Use spec status for full bodies.

Errors

Each status has an example body in the response examples. See errors and retries.

Authorizations

Authorization
string
header
required

Your pre.dev workspace API key (pdk_...) from Integrations, Built-in tab: https://pre.dev/projects/integrations?tab=built-in

Query Parameters

query
string
required

Case-insensitive regular expression matched against spec input. Invalid syntax returns 500.

Minimum string length: 1
limit
integer
default:20
Required range: 1 <= x <= 100
skip
integer
default:0
Required range: x >= 0
endpoint
enum<string>
Available options:
fast_spec,
deep_spec
status
enum<string>
Available options:
pending,
processing,
completed,
failed

Response

Paginated spec summaries.

specs
object[]
required
total
integer
required
Required range: x >= 0
hasMore
boolean
required