List Specs
API Reference
List Specs
List all specs with pagination and filtering. Perfect for displaying user spec history, recent specs, or filtered views.
GET
List Specs
Documentation Index
Fetch the complete documentation index at: https://docs.pre.dev/llms.txt
Use this file to discover all available pages before exploring further.
GET /list-specs
List all specifications with support for pagination and filtering by status or endpoint type.Overview
- Cost: Free (no credits required)
- Use Cases: Display spec history, build dashboards, monitor spec status
- Response Time: Instant
- Returns: Paginated array of specs with metadata
Endpoint
Headers
Query Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
limit | integer | ❌ | 20 | Results per page (1-100) |
skip | integer | ❌ | 0 | Number of records to skip for pagination |
endpoint | string | ❌ | - | Filter by endpoint: fast_spec or deep_spec |
status | string | ❌ | - | Filter by status: pending, processing, completed, or failed |
Parameter Details
limit- Minimum: 1
- Maximum: 100
- Default: 20
- Controls how many specs are returned per request
- Minimum: 0
- Used for pagination (e.g., skip=20 for page 2 with limit=20)
fast_spec- Only show Fast Spec generationsdeep_spec- Only show Deep Spec generations
pending- Queued but not startedprocessing- Currently generatingcompleted- Successfully finishedfailed- Generation failed
Response
Success Response
Response Fields
| Field | Type | Description |
|---|---|---|
specs | array | Array of spec objects (see Spec Object below) |
total | integer | Total number of specs matching the filters |
hasMore | boolean | Whether more pages are available |
Spec Object Fields
| Field | Type | Always Present | Description |
|---|---|---|---|
_id | string | ✅ | Unique spec identifier |
created | string | ✅ | ISO 8601 timestamp of creation |
endpoint | string | ✅ | "fast_spec" or "deep_spec" |
input | string | ✅ | Original input text |
status | string | ✅ | Current status |
success | boolean | ✅ | Whether generation succeeded |
uploadedFileShortUrl | string | ❌ | URL if file was uploaded |
uploadedFileName | string | ❌ | Name of uploaded file |
humanSpecUrl | string | ❌ | Human-readable spec URL (when completed) |
totalHumanHours | number | ❌ | Estimated total hours for a human to implement the spec (when completed) |
codingAgentSpecUrl | string | ❌ | Coding agent spec URL (when completed) |
executionTime | number | ❌ | Processing time in ms (when completed) |
predevUrl | string | ❌ | pre.dev project URL (when completed) |
errorMessage | string | ❌ | Error details (when failed) |
progress | string | ❌ | Status message (when processing) |
Code Examples
cURL Examples
Get first 20 specs:JavaScript/Node.js
TypeScript
Python
Common Use Cases
1. Display Recent Specs Dashboard
2. Monitor Failed Specs
3. Export Completed Specs
4. Build Pagination Component
Best Practices
Pagination
- Use reasonable page sizes (20-50 specs)
- Cache results when appropriate
- Show loading states while fetching
Filtering
- Combine filters to reduce result sets
- Use
status=completedfor user-facing spec lists - Use
status=failedfor debugging/monitoring
Performance
- Don’t fetch all specs at once if you have many
- Use pagination for large datasets
- Consider implementing infinite scroll with
skipparameter
Error Handling
- Always check response status codes
- Handle empty result sets gracefully
- Show appropriate messages when no specs match filters
Next: Find Specs (Search)
Search specs using regex patterns for advanced filtering.
Authorizations
API key for authentication. Get your API key from https://pre.dev/projects/playground (Solo) or https://pre.dev/enterprise/dashboard?page=api (Enterprise). Use format: Bearer YOUR_API_KEY
Query Parameters
Number of results per page (1-100)
Required range:
1 <= x <= 100Example:
20
Number of records to skip for pagination
Required range:
x >= 0Example:
0
Filter by endpoint type
Available options:
fast_spec, deep_spec Example:
"fast_spec"
Filter by processing status
Available options:
pending, processing, completed, failed Example:
"completed"

