> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Reo.dev: Reo Get Account Activities

> Get an account's developer activity timeline in Reo.dev (GitHub, docs, website, product usage), optionally filtered by source and type.

Get an account's developer activity timeline in Reo.dev (GitHub, docs, website, product usage), optionally filtered by source and type.

> [!NOTE]
>
> Tool ID: `reo_get_account_activities`

## Run this action

Use the TypeScript SDK for one call. Use `ctx.tools.execute(...)` inside a Play for durable calls, scheduled calls, or CSV processing.

```ts theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'reo_get_account_activities',
  {
    "account_id": "123e4567-e89b-42d3-a456-426614174000"
  },
);

console.log(result.toolResponse.raw);
```

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline run reo_get_account_activities --input '{
  "account_id": "123e4567-e89b-42d3-a456-426614174000"
}'
```

## Example response

The SDK returns this shape at `result.toolResponse.raw`. The example values illustrate the response.

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "data": {
    "data": [
      {
        "actor": "example",
        "page": "example",
        "activity_type": "example"
      }
    ],
    "has_more": true
  }
}
```

Use `deepline describe reo_get_account_activities --json` for the latest machine-readable contract.

## Input reference

### Overview Returns all activities recorded for a given account, including which developer performed each activity. Supports filtering by activity type and activity source. ### Path Parameters | Name | Type | Required | Description | |---|---|---|---| | `account_id` | string (UUID) | Yes | Account ID (`id` from the account APIs) | ### Filters (Query Parameters) Narrow the activities returned by source, or by source and type together. | Name | Type | Required | Description | |---|---|---|---| | `activity_source` | string | No. Required when `activity_type` is set | Filter by activity source | | `activity_type` | string | No | Filter by activity type. Must be valid for the `activity_source` sent | **How the filters work** - Filter by source only: `?activity_source=GITHUB` returns every GitHub activity. - Filter by source and type: `?activity_source=GITHUB&activity_type=STAR` returns only See the live schema below for the complete notes.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.account_id` | `string` | Yes | — | Account ID (`id` from the account APIs). Format: `uuid`. |
| `payload.activity_source` | `"GITHUB" \| "DOCUMENT" \| "WEBSITE" \| "PRODUCT_JS" \| "CODE_INTERACTIONS" \| "SLACK" \| "LINKEDIN" \| "PRODUCT_API"` | No | — | Filter by activity source. Required: No. Required when `activity_type` is set. Allowed: `GITHUB`, `DOCUMENT`, `WEBSITE`, `PRODUCT_JS`, `CODE_INTERACTIONS`, `SLACK`, `LINKEDIN`, `PRODUCT_API`. |
| `payload.activity_type` | `string` | No | — | Filter by activity type. Must be valid for the `activity_source` sent. |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ````json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "### Overview Returns all activities recorded for a given account, including which developer performed each activity. Supports filtering by activity type and activity source. ### Path Parameters | Name | Type | Required | Description | |---|---|---|---| | `account_id` | string (UUID) | Yes | Account ID (`id` from the account APIs) | ### Filters (Query Parameters) Narrow the activities returned by source, or by source and type together. | Name | Type | Required | Description | |---|---|---|---| | `activity_source` | string | No. Required when `activity_type` is set | Filter by activity source | | `activity_type` | string | No | Filter by activity type. Must be valid for the `activity_source` sent | **How the filters work** - Filter by source only: `?activity_source=GITHUB` returns every GitHub activity. - Filter by source and type: `?activity_source=GITHUB&activity_type=STAR` returns only GitHub stars. - `activity_type` can't be sent on its own. It must come with `activity_source`, and it must be valid for that source, or the call returns `400`. - Valid `activity_source` values: `GITHUB`, `DOCUMENT`, `WEBSITE`, `PRODUCT_JS`, `CODE_INTERACTIONS`, `SLACK`, `LINKEDIN`, `PRODUCT_API`. - For the `activity_type` values allowed under each source, call **Get Activity Types** (`GET https://integration.reo.dev/activities/types`). - No filters returns all activities. ``` GET https://integration.reo.dev/account/ /activities?activity_source=GITHUB&activity_type=PULL_REQUEST ``` ### Errors | Code | When it happens | Response body | |---|---|---| | 400 | `X-API-KEY` header missing or empty · `activity_type` sent without `activity_source` · Unknown `activity_source` · `activity_type` not valid for the `activity_source` sent | Missing key: `{\"error\":\"Missing API Key\"}` · Type without source: `{\"error\":\"activity_source is required when activity_type is set; see GET /v1/activity-types for valid pairs\"}` · Unknown source: `{\"error\":\"unknown activity_source \\\"FOOBAR\\\"; see GET /v1/activity-types for valid values\"}` · Invalid pair: `{\"error\":\"activity_type \\\"PAGE_VISIT\\\" is not valid for activity_source \\\"GITHUB\\\"; see GET /v1/activity-types for valid pairs\"}` | | 403 | Invalid API key, or a write API key used on this host · Account ID doesn't exist | Bad key: `{\"error\":\"Invalid API Key.\"}` · Unknown account: `{\"error\":\"Invalid Account Id.\"}` | ### ENUMs | Field | Value | Meaning | |---|---|---| | activity_source | `GITHUB` | GitHub | | activity_source | `DOCUMENT` | Documentation | | activity_source | `WEBSITE` | Website | | activity_source | `PRODUCT_JS` | Product (JS tracking) | | activity_source | `CODE_INTERACTIONS` | Code interactions | | activity_source | `SLACK` | Slack | | activity_source | `LINKEDIN` | LinkedIn | | activity_source | `PRODUCT_API` | Product API (usage sent through the Add Telemetry Data and Add Custom Product Data APIs) | | activity_type (GITHUB) | `FORK` | Forked repository | | activity_type (GITHUB) | `STAR` | Starred repository | | activity_type (GITHUB) | `COMMENT` | Commented | | activity_type (GITHUB) | `ISSUE_CREATION` | Created an issue | | activity_type (GITHUB) | `PULL_REQUEST` | Opened a pull request | | activity_type (GITHUB) | `WATCH` | Watched repository | ### Things to Note - Valid `activity_type` values depend on the `activity_source`. Call **Get Activity Types** for the full list of valid pairs. - Response envelope is `data` and `has_more`. There is no `page_no`, `page_size` or `total_pages`. - `has_more: true` means more activities exist beyond this response. - `developer_id` is the ID of the developer who did the activity. Use it with Get Developer Activities. - `copied_text` is `null` unless the activity copied text. `activity_date` is `YYYY-MM-DD`. `count` is the number of times the activity happened.",
    "properties": {
      "account_id": {
        "type": "string",
        "description": "Account ID (`id` from the account APIs).",
        "format": "uuid"
      },
      "activity_source": {
        "type": "string",
        "description": "Filter by activity source. Required: No. Required when `activity_type` is set.",
        "enum": [
          "GITHUB",
          "DOCUMENT",
          "WEBSITE",
          "PRODUCT_JS",
          "CODE_INTERACTIONS",
          "SLACK",
          "LINKEDIN",
          "PRODUCT_API"
        ]
      },
      "activity_type": {
        "type": "string",
        "description": "Filter by activity type. Must be valid for the `activity_source` sent."
      }
    },
    "required": [
      "account_id"
    ],
    "additionalProperties": false
  }
  ````
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | Provider response payload. |
| `result.data.data` | `array` | No | — | Result records. |
| `result.data.data[].actor` | `string` | No | — | Name of the developer who did the activity. |
| `result.data.data[].page` | `string` | No | — | Page or repository the activity happened on. |
| `result.data.data[].activity_type` | `string` | No | — | Type of activity. See ENUMs and Get Activity Types. - `FORK` (GITHUB): Forked repository - `STAR` (GITHUB): Starred repository - `COMMENT` (GITHUB): Commented - `ISSUE_CREATION` (GITHUB): Created an issue - `PULL_REQUEST` (GITHUB): Opened a pull request - `WATCH` (GITHUB): Watched repository |
| `result.data.data[].activity_source` | `"GITHUB" \| "DOCUMENT" \| "WEBSITE" \| "PRODUCT_JS" \| "CODE_INTERACTIONS" \| "SLACK" \| "LINKEDIN" \| "PRODUCT_API"` | No | — | Channel the activity came from. See ENUMs. - `GITHUB`: GitHub - `DOCUMENT`: Documentation - `WEBSITE`: Website - `PRODUCT_JS`: Product (JS tracking) - `CODE_INTERACTIONS`: Code interactions - `SLACK`: Slack - `LINKEDIN`: LinkedIn - `PRODUCT_API`: Product API (usage sent through the Add Telemetry Data and Add Custom Product Data APIs) Allowed: `GITHUB`, `DOCUMENT`, `WEBSITE`, `PRODUCT_JS`, `CODE_INTERACTIONS`, `SLACK`, `LINKEDIN`, `PRODUCT_API`. |
| `result.data.data[].copied_text` | `string \| null` | No | — | Text copied by the user. `null` unless the activity copied text. |
| `result.data.data[].developer_designation` | `string` | No | — | Job title of the developer. Can be `null`. |
| `result.data.data[].country` | `string` | No | — | Country of the developer. |
| `result.data.data[].activity_date` | `string` | No | — | Date of the activity, `YYYY-MM-DD`. |
| `result.data.data[].developer_linkedin` | `string` | No | — | LinkedIn profile URL. Empty string when unknown. |
| `result.data.data[].activity_info` | `string` | No | — | URL or detail with more information about the activity. |
| `result.data.data[].developer_id` | `string` | No | — | ID of the developer who did the activity. Use with Get Developer Activities. |
| `result.data.data[].count` | `integer` | No | — | Number of times the activity happened. |
| `result.data.has_more` | `boolean` | No | — | `true` when more activities exist beyond this response. |
| `result.meta` | `object` | No | — | Additional response metadata (status, paging). |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "Provider response payload.",
        "properties": {
          "data": {
            "type": "array",
            "description": "Result records.",
            "items": {
              "type": "object",
              "properties": {
                "actor": {
                  "type": "string",
                  "description": "Name of the developer who did the activity."
                },
                "page": {
                  "type": "string",
                  "description": "Page or repository the activity happened on."
                },
                "activity_type": {
                  "type": "string",
                  "description": "Type of activity. See ENUMs and Get Activity Types. - `FORK` (GITHUB): Forked repository - `STAR` (GITHUB): Starred repository - `COMMENT` (GITHUB): Commented - `ISSUE_CREATION` (GITHUB): Created an issue - `PULL_REQUEST` (GITHUB): Opened a pull request - `WATCH` (GITHUB): Watched repository"
                },
                "activity_source": {
                  "type": "string",
                  "description": "Channel the activity came from. See ENUMs. - `GITHUB`: GitHub - `DOCUMENT`: Documentation - `WEBSITE`: Website - `PRODUCT_JS`: Product (JS tracking) - `CODE_INTERACTIONS`: Code interactions - `SLACK`: Slack - `LINKEDIN`: LinkedIn - `PRODUCT_API`: Product API (usage sent through the Add Telemetry Data and Add Custom Product Data APIs)",
                  "enum": [
                    "GITHUB",
                    "DOCUMENT",
                    "WEBSITE",
                    "PRODUCT_JS",
                    "CODE_INTERACTIONS",
                    "SLACK",
                    "LINKEDIN",
                    "PRODUCT_API"
                  ]
                },
                "copied_text": {
                  "type": [
                    "string",
                    "null"
                  ],
                  "description": "Text copied by the user. `null` unless the activity copied text."
                },
                "developer_designation": {
                  "type": "string",
                  "description": "Job title of the developer. Can be `null`."
                },
                "country": {
                  "type": "string",
                  "description": "Country of the developer."
                },
                "activity_date": {
                  "type": "string",
                  "description": "Date of the activity, `YYYY-MM-DD`."
                },
                "developer_linkedin": {
                  "type": "string",
                  "description": "LinkedIn profile URL. Empty string when unknown."
                },
                "activity_info": {
                  "type": "string",
                  "description": "URL or detail with more information about the activity."
                },
                "developer_id": {
                  "type": "string",
                  "description": "ID of the developer who did the activity. Use with Get Developer Activities."
                },
                "count": {
                  "type": "integer",
                  "description": "Number of times the activity happened."
                }
              },
              "additionalProperties": false
            }
          },
          "has_more": {
            "type": "boolean",
            "description": "`true` when more activities exist beyond this response."
          }
        },
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Deepline cost

* Pricing model: `fixed` (per call).
* Estimated Deepline credits: `0` per pricing unit.
* Provider-native pricing may still exist outside Deepline credit billing.

## Related documentation

* [Connect integrations](https://deepline.com/docs/integrations.md)
* [SDK V2 quickstart](https://deepline.com/docs/sdk-v2/quickstart.md)
* [SDK reference](https://deepline.com/docs/sdk-v2/sdk-reference.md)
* [Run tools across a CSV](https://deepline.com/docs/sdk-v2/batch-csv.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.