> ## 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 Activity Types

> List the valid Reo.dev activity sources (GitHub, docs, website, product, Slack, LinkedIn) and the activity types allowed for each.

List the valid Reo.dev activity sources (GitHub, docs, website, product, Slack, LinkedIn) and the activity types allowed for each.

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

## 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_activity_types',
  {},
);

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

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline run reo_get_activity_types --input '{}'
```

## 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": [
      {
        "activity_source": "GITHUB",
        "label": "example",
        "activity_types": [
          {}
        ]
      }
    ],
    "request_id": "request_123"
  }
}
```

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

## Input reference

### Overview Master API to refer `activity_type` and `activity_source`. Returns every valid activity source and the activity types allowed for each, for use as filters in **Get Account Activities** and **Get Developer Activities**. ### Path Parameters None. ### Errors | Code | When it happens | Response body | |---|---|---| | 400 | `X-API-KEY` header missing or empty | `{"error":"Missing API Key"}` | | 403 | Invalid API key, or a write API key used on this host | `{"error":"Invalid API Key."}` | ### 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 | | See the live schema below for the complete notes.

This action requires no input fields.

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

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "### Overview Master API to refer `activity_type` and `activity_source`. Returns every valid activity source and the activity types allowed for each, for use as filters in **Get Account Activities** and **Get Developer Activities**. ### Path Parameters None. ### Errors | Code | When it happens | Response body | |---|---|---| | 400 | `X-API-KEY` header missing or empty | `{\"error\":\"Missing API Key\"}` | | 403 | Invalid API key, or a write API key used on this host | `{\"error\":\"Invalid API Key.\"}` | ### 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 - The sample shows one source. The live response returns an entry for each source above, each with its own `activity_types`. - This endpoint returns `request_id` in the body as well as in the `X-Request-Id` header. - Error messages in Get Account Activities and Get Developer Activities refer to `GET /v1/activity-types`. Use `/activities/types`.",
    "properties": {},
    "required": [],
    "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[].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[].label` | `string` | No | — | Human-readable label for the source or activity type. |
| `result.data.data[].activity_types` | `array` | No | — | Activity types valid for this source. |
| `result.data.data[].activity_types[].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_types[].label` | `string` | No | — | Human-readable label for the source or activity type. |
| `result.data.request_id` | `string` | No | — | Request ID. Also returned in the `X-Request-Id` response header. |
| `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": {
                "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"
                  ]
                },
                "label": {
                  "type": "string",
                  "description": "Human-readable label for the source or activity type."
                },
                "activity_types": {
                  "type": "array",
                  "description": "Activity types valid for this source.",
                  "items": {
                    "type": "object",
                    "properties": {
                      "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"
                      },
                      "label": {
                        "type": "string",
                        "description": "Human-readable label for the source or activity type."
                      }
                    },
                    "additionalProperties": false
                  }
                }
              },
              "additionalProperties": false
            }
          },
          "request_id": {
            "type": "string",
            "description": "Request ID. Also returned in the `X-Request-Id` response header."
          }
        },
        "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.