Deepcrawl
Activity Logs

List Logs

Paginated activity log history with filters for path, status, and dates.

List historic Deepcrawl requests with filters for time range, endpoint, success status, and pagination. This endpoint is optimised for quick scans—it returns metadata about each run without replaying the stored response payloads.

listLogs does not return original response bodies. To inspect the original payload for a given log, call getOneLog or exportResponse.

Endpoint

  • POST https://api.deepcrawl.dev/logs
  • Body accepts JSON options; authentication uses bearer tokens.

Request Options – ListLogsOptions

Prop

Type

Any missing fields are normalized via resolveListLogsOptions, so you can send an empty body to receive the latest logs.

Example Request

curl "https://api.deepcrawl.dev/logs" \
  -H "Authorization: Bearer $DEEPCRAWL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "path": "read-readUrl",
    "success": true,
    "startDate": "2025-01-01T00:00:00.000Z",
    "limit": 10
  }'

TypeScript SDK

import { DeepcrawlApp } from 'deepcrawl';

const dc = new DeepcrawlApp({ apiKey: process.env.DEEPCRAWL_API_KEY! });
const params: ListLogsOptions = {
  path: 'links-extractLinks',
  startDate: '2025-01-01T00:00:00.000Z',
  endDate: '2025-01-31T23:59:59.999Z',
  limit: 25
};
const { logs, meta }: ListLogsResponse = await dc.listLogs(params);

if (meta.hasMore) {
  console.log(`Next page offset: ${meta.nextOffset}`);
}

Response – ListLogsResponse

Prop

Type

{
  "logs": [
    {
      "id": "log_123",
      "path": "links-extractLinks",
      "success": true,
      "requestOptions": {
        "url": "https://example.com",
        "tree": true
      },
      "requestTimestamp": "2025-01-12T12:45:33.000Z"
    }
  ],
  "meta": {
    "limit": 10,
    "offset": 0,
    "hasMore": true,
    "nextOffset": 10,
    "orderBy": "requestTimestamp",
    "orderDir": "desc",
    "startDate": "2025-01-01T00:00:00.000Z",
    "endDate": "2025-01-31T23:59:59.999Z"
  }
}

Tips

  • When paginating, pass offset: meta.nextOffset from the previous response.
  • Combine path and success filters to isolate failing requests.
  • Use the dashboard query builder for previews, then copy the generated query into automation.