DrillPlan's Activity Log Download API allows external applications to export activity logs from a data partition as a JSON file. The endpoint returns activity logs across all projects in the current data partition, including data-partition-scoped logs.

curl -X GET '{baseURL}activity-log/v1/download?before={before}&after={after}&page=1' \
-H 'accept: application/json' \
-H 'slb-partition-id: {SlbPartitionId}' \
-H 'appkey: {appKey}' \
-H 'Authorization: Bearer {token}'

Authentication

This endpoint requires a service token obtained via the Client Credentials Flow (CCG). User tokens from Authorization Code Flow are not accepted and will receive a 401 Unauthorized response.

See How to access DrillPlan APIs for prerequisites (AppKey, Client_Id, Secret, slb-partition-id, and token generation).

The upper bound of the activity time range (inclusive). Activity logs with activity_time before or at this timestamp are included.

This parameter is required. Requests without before will receive a 400 Bad Request response.

The lower bound of the activity time range (inclusive). Activity logs with activity_time after or at this timestamp are included.

This parameter is required. Requests without after will receive a 400 Bad Request response.

Date range limit

The difference between before and after must not exceed 90 days. Requests exceeding this limit will receive a 400 Bad Request response with the message: Date range between before and after must not exceed 90 days.

Timestamps should be provided in ISO 8601 format (for example, 2026-07-09T00:00:00.0000000Z).

1-based page number (optional). Each page returns up to 100 activity log records. The page size is fixed and cannot be changed via query parameters.

When page is omitted, the first 100 matching records are returned. Use page=2, page=3, and so on to retrieve additional records within the same time range.

A successful request returns HTTP 200 OK with a JSON object containing the activity log records and pagination metadata:

• Content-Type: application/json

Results are sorted in descending order of activity time (most recent first).

Each element in the items array has the following properties:

Each item in the activities array has the following properties:

{
  "items": [
    {
      "id": "abc123",
      "owner": {
        "full_name": "Jane Doe",
        "image_url": "https://example.com/avatar.jpg",
        "alias": "jdoe"
      },
      "activities": [
        {
          "type": "Update",
          "entity_id": "plan-001",
          "entity_name": "Well Plan A",
          "activity_time": "2026-07-08T14:30:00.0000000Z",
          "comments": "",
          "project_id": "project-001",
          "activity_entity_type": "plan",
          "is_customer_data": false,
          "changed_property_names": ["name"],
          "extension_propertys_dic": {},
          "parent": {
            "id": "project-001",
            "entity_type": "project",
            "name": "Exploration Project",
            "parent": null
          },
          "old_name": null,
          "changed_properties": []
        }
      ],
      "plan_name": "Well Plan A",
      "project_name": "Exploration Project"
    }
  ],
  "page": 1,
  "page_size": 100,
  "has_more": false
}

To download all activity logs within a time range:

1. Call GET /v1/download?before={before}&after={after}&page=1.
2. Read activity logs from the items array in the response.
3. If has_more is true, call again with page=2, then page=3, and so on.
4. Stop when has_more is false.