> ## 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 Developer Activities

> Get one developer's activity timeline in Reo.dev (GitHub stars, forks and PRs, docs and website visits, product usage), optionally filtered by source and type.

Get one developer's activity timeline in Reo.dev (GitHub stars, forks and PRs, docs and website visits, product usage), optionally filtered by source and type.

> [!NOTE]
>
> Tool ID: `reo_get_developer_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_developer_activities',
  {
    "developer_id": "123e4567-e89b-42d3-a456-426614174000"
  },
);

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

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline run reo_get_developer_activities --input '{
  "developer_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": [
      {
        "page": "example",
        "account_name": "Example",
        "activity_type": "example"
      }
    ],
    "has_more": true
  }
}
```

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

## Input reference

### Overview Returns all activities performed by a specific developer. Supports filtering by activity type and activity source. ### Path Parameters | Name | Type | Required | Description | |---|---|---|---| | `developer_id` | string (UUID) | Yes | Developer ID (`id` from the developer APIs, or `developer_id` from Get Account Activities) | ### 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` See the live schema below for the complete notes.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.developer_id` | `string` | Yes | — | Developer ID (`id` from the developer APIs, or `developer_id` from Get Account Activities). 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 performed by a specific developer. Supports filtering by activity type and activity source. ### Path Parameters | Name | Type | Required | Description | |---|---|---|---| | `developer_id` | string (UUID) | Yes | Developer ID (`id` from the developer APIs, or `developer_id` from Get Account Activities) | ### 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/developer/ /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 · Developer ID doesn't exist | Bad key: `{\"error\":\"Invalid API Key.\"}` · Unknown developer: `{\"error\":\"Invalid Developer 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. - Error messages point to `GET /v1/activity-types`. The live endpoint is `GET https://integration.reo.dev/activities/types`. - Response envelope is `data` and `has_more`. There is no `page_no`, `page_size` or `total_pages`. - Fields differ from Get Account Activities: there's no `actor`, `developer_id`, `developer_linkedin` or `count`, and there are `account_name`, `source_type` and `source_url`. - Several fields can be `null` (`account_name`, `copied_text`, `developer_designation`, `country`, `source_type`). Handle nulls on every field. - `activity_date` is `YYYY-MM-DD`.",
    "properties": {
      "developer_id": {
        "type": "string",
        "description": "Developer ID (`id` from the developer APIs, or `developer_id` from Get Account Activities).",
        "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": [
      "developer_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[].page` | `string` | No | — | Page, repository or resource the activity happened on. |
| `result.data.data[].account_name` | `string \| null` | No | — | Account the activity is attributed to. Can be `null`. |
| `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 \| null` | No | — | Job title of the developer. Can be `null`. |
| `result.data.data[].country` | `string \| null` | No | — | Country. Can be `null`. |
| `result.data.data[].activity_date` | `string` | No | — | Date of the activity, `YYYY-MM-DD`. |
| `result.data.data[].source_type` | `string \| null` | No | — | Type of the source. Can be `null`. |
| `result.data.data[].activity_info` | `string` | No | — | URL or detail with more information about the activity. |
| `result.data.data[].source_url` | `string` | No | — | URL of the source. |
| `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": {
                "page": {
                  "type": "string",
                  "description": "Page, repository or resource the activity happened on."
                },
                "account_name": {
                  "type": [
                    "string",
                    "null"
                  ],
                  "description": "Account the activity is attributed to. Can be `null`."
                },
                "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",
                    "null"
                  ],
                  "description": "Job title of the developer. Can be `null`."
                },
                "country": {
                  "type": [
                    "string",
                    "null"
                  ],
                  "description": "Country. Can be `null`."
                },
                "activity_date": {
                  "type": "string",
                  "description": "Date of the activity, `YYYY-MM-DD`."
                },
                "source_type": {
                  "type": [
                    "string",
                    "null"
                  ],
                  "description": "Type of the source. Can be `null`."
                },
                "activity_info": {
                  "type": "string",
                  "description": "URL or detail with more information about the activity."
                },
                "source_url": {
                  "type": "string",
                  "description": "URL of the source."
                }
              },
              "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.