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

# LinkedIn

> LinkedIn Scenario seeding parameters, nested fields, and examples

Use `linkedin` in `twins` and put this configuration under `seed_config.linkedin`.

LinkedIn professional network twin with members, profile search/typeahead, first-degree connections, OAuth/OIDC tokens, UGC posts, and feed assets.

## Example seed

This is the complete Scenario request body for [creating a Scenario](https://docs.argalabs.com/api-reference/post-create-a-scenario.md). You can also import it with `arga test-runner scenarios import --file scenario.json`.

```json theme={null}
{
  "name": "LinkedIn eval fixture",
  "twins": [
    "linkedin"
  ],
  "seed_config": {
    "linkedin": {
      "members": [
        {
          "name": "Ada Lovelace",
          "headline": "Founder at Analytical Engines",
          "email": "ada@example.com",
          "vanity_name": "ada-lovelace",
          "connections": [
            "grace@example.com"
          ]
        }
      ],
      "posts": [
        {
          "author_email": "ada@example.com",
          "text": "Hiring platform engineers for a developer tooling team.",
          "article_url": "https://example.com/careers",
          "title": "Engineering roles",
          "description": "Seeded LinkedIn post link preview"
        }
      ]
    }
  }
}
```

## Parameters

The following fields belong directly inside `seed_config.linkedin`. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.

| Parameter | Type | Description |
| - | - | - |
| `members` | `object[]` | Members fixtures in provider-native format. |
| `posts` | `object[]` | Posts fixtures in provider-native format. |

## Resource fields

These tables describe the record shapes used by the example. Keep native field names and casing. Map keys such as property names, IDs, and metadata keys are supplied by your fixture.

### `members[]`

| Parameter | Type | Description |
| - | - | - |
| `name` | `string` | Human-readable name. |
| `headline` | `string` | Headline. |
| `email` | `string` | Main account email address. |
| `vanity_name` | `string` | Vanity name. |
| `connections` | `string[]` | Connections fixtures in provider-native format. |

### `posts[]`

| Parameter | Type | Description |
| - | - | - |
| `author_email` | `string` | Author email. |
| `text` | `string` | Text content. |
| `article_url` | `string` | Article url. |
| `title` | `string` | Human-readable name. |
| `description` | `string` | Description. |

See [Scenario seeding](https://docs.argalabs.com/twins/seeding.md) for saving, provisioning, and resetting fixtures.


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