List Saved Dorks

Retrieve your saved dorks with any custom notes and tags you've added.

User-Scoped Endpoint

This endpoint returns saved dorks for the user associated with the API key. Each API key is linked to a specific user account.

Request

bash

# Basic request
curl -X GET "https://dorklist.com/api/v1/saved" \
  -H "Authorization: Bearer dk_your_api_key_here"
# With pagination
curl -X GET "https://dorklist.com/api/v1/saved?page=1&limit=50" \
  -H "Authorization: Bearer dk_your_api_key_here"

Query Parameters

Parameter	Type	Default	Description
page	integer	1	Page number for pagination
limit	integer	20	Number of results per page (max: 100)

Response

Saved Dork Object

Field	Type	Description
id	string (UUID)	Saved dork entry ID
dork_id	string (UUID)	Reference to the original dork
dork	object	Full dork object (title, query, etc.)
notes	string \| null	User's personal notes for this dork
custom_tags	string[] \| null	User-defined tags for organization
saved_at	string (ISO 8601)	When the dork was saved

Example Response

json

{
  "success": true,
  "data": {
    "saved_dorks": [
      {
        "id": "770e8400-e29b-41d4-a716-446655440001",
        "dork_id": "660e8400-e29b-41d4-a716-446655440001",
        "dork": {
          "id": "660e8400-e29b-41d4-a716-446655440001",
          "title": "SQL Error Messages",
          "query": "site:example.com intext:\"sql syntax\" | intext:\"mysql_fetch\"",
          "description": "Find pages exposing SQL error messages",
          "category": {
            "name": "Vulnerability Scanning",
            "icon": "shield-alert"
          },
          "is_pro": false,
          "slug": "sql-error-messages"
        },
        "notes": "Used this for the acme.com pentest - found 3 vulnerable endpoints",
        "custom_tags": ["pentest", "acme", "sql"],
        "saved_at": "2024-02-15T09:20:00.000Z"
      },
      {
        "id": "770e8400-e29b-41d4-a716-446655440002",
        "dork_id": "660e8400-e29b-41d4-a716-446655440002",
        "dork": {
          "id": "660e8400-e29b-41d4-a716-446655440002",
          "title": "Exposed Config Files",
          "query": "site:example.com ext:env | ext:config | ext:ini",
          "description": "Search for exposed configuration files",
          "category": {
            "name": "Files & Exposures",
            "icon": "file-warning"
          },
          "is_pro": false,
          "slug": "exposed-config-files"
        },
        "notes": null,
        "custom_tags": ["recon", "config"],
        "saved_at": "2024-02-10T14:30:00.000Z"
      }
    ]
  },
  "pagination": {
    "page": 1,
    "limit": 20,
    "total": 12,
    "hasMore": false
  }
}

Empty State

If you haven't saved any dorks yet, the response will have an empty array:

json

{
  "success": true,
  "data": {
    "saved_dorks": []
  },
  "pagination": {
    "page": 1,
    "limit": 20,
    "total": 0,
    "hasMore": false
  }
}

Common Use Cases

•Syncing saved dorks to your own tool or database
•Building a custom interface for your saved dorks
•Automating dork execution from your saved collection
•Backing up your saved dorks and notes

Next Steps

Error Codes →

Handle errors properly in your integration

Response Format →

Understand the standard response structure