> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Laposta

The Laposta connector lets your AI agent act in each user's Laposta account. Each user connects their own Laposta API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 46 tools.

**Authentication:** API Key
**Categories:** Marketing
**Tools:** 46: 19 read, 20 write, 7 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=LAPOSTA)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Laposta connection

   In **AgentKit > Connections**, create a Laposta connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'laposta_automation_get',
  toolInput: {
    automation_id: '<automation_id>',
  },
  connector: 'laposta',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="laposta_automation_get",
    tool_input={
        "automation_id": "<automation_id>",
    },
    connection_name="laposta",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `laposta_automation_get`

Get Automation · Read-only

Get one Laposta automation.
Returns the automation object with automation_id, name, status, started count and dates.
Use laposta_automations_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `automation_id` (`string`, required): ID of the automation. Find it with laposta_automations_list. Example: pdq4k7wqcm.

Example input: `{"automation_id":"<automation_id>"}`

### `laposta_automations_list`

List Automations · Read-only

List the automations in the Laposta account, optionally only active or inactive ones. Deleted automations are left out.
Returns data[] of automation objects with automation_id, name, status and started count.
Use laposta_automation_get for one automation.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `status` (`string`, optional): Only automations with this status: active or inactive. Leave empty for all. One of: `active`, `inactive`.

Example input: `{}`

### `laposta_campaign_content_get`

Get Campaign Content · Read-only

Get the HTML content of a Laposta campaign. Works only for campaigns filled with HTML or an import URL, not drag-and-drop campaigns.
Returns the campaign_id, plain html and import_url.
Use laposta_campaign_content_update to change it.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `campaign_id` (`string`, required): ID of the campaign. Find it with laposta_campaigns_list. Example: njhgaf61ye.

Example input: `{"campaign_id":"<campaign_id>"}`

### `laposta_campaign_get`

Get Campaign · Read-only

Get one Laposta campaign.
Returns the campaign object: name, subject, previewtext, from, reply_to, list_ids, delivery times, web version URL and screenshots.
Use laposta_campaigns_list to find the campaign_id.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `campaign_id` (`string`, required): ID of the campaign. Find it with laposta_campaigns_list. Example: njhgaf61ye.

Example input: `{"campaign_id":"<campaign_id>"}`

### `laposta_campaign_history_get`

Get Campaign History · Read-only

Get the event history of a Laposta campaign: sends, opens, clicks, bounces, unsubscribes and complaints per subscriber.
Returns data[] of events with type, event_date, member and details, plus pagination with has_more and next_cursor.
Use laposta_report_get for totals only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `campaign_id` (`string`, required): ID of the campaign. Find it with laposta_campaigns_list. Example: njhgaf61ye.
- `cursor` (`string`, optional): pagination.next_cursor from the previous page, sent back unchanged. Keep the same filters when paging.
- `event_date_from` (`string`, optional): Only events from this date and time, inclusive. Regular format YYYY-MM-DD HH:MM:SS (account timezone) or ISO 8601. Example: 2026-04-01 00:00:00.
- `event_date_to` (`string`, optional): Only events before this date and time, exclusive. Regular format YYYY-MM-DD HH:MM:SS (account timezone) or ISO 8601. Example: 2026-05-01 00:00:00.
- `limit` (`integer`, optional): Maximum events per page, 1-1000 (Laposta default 100). Example: 100.
- `order` (`string`, optional): Sort direction, desc (default) or asc. One of: `desc`, `asc`.
- `order_by` (`string`, optional): Field to sort by. Only event_date is supported. One of: `event_date`.

Example input: `{"campaign_id":"<campaign_id>"}`

### `laposta_campaigns_list`

List Campaigns · Read-only

List the campaigns in the Laposta account, optionally only drafts or only sent ones.
Returns data[] of campaign objects with campaign_id, name, subject, from, list_ids and delivery times.
Use laposta_campaign_get for one campaign and laposta_report_get for its results.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `status` (`string`, optional): Only draft campaigns (not sent yet, including scheduled) or sent ones (sending or sent). Leave empty for all. One of: `draft`, `sent`.

Example input: `{}`

### `laposta_field_get`

Get Field · Read-only

Get one field of a Laposta list.
Returns the field object: field_id, name, tag, custom_name, datatype, defaultvalue, options and options_full, required, in_form and in_list.
Use laposta_fields_list to find the field_id.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `field_id` (`string`, required): ID of the field. Example: gt2Em8vJwi.
- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.

Example input: `{"field_id":"<field_id>","list_id":"<list_id>"}`

### `laposta_fields_list`

List Fields · Read-only

List all fields of a Laposta list, including the built-in email field and the labels field if the list uses labels.
Returns data[] of field objects with field_id, name, custom_name, datatype, options, required, in_form and in_list.
Use the custom_name values as keys in custom_fields when adding or updating subscribers.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.

Example input: `{"list_id":"<list_id>"}`

### `laposta_list_get`

Get List · Read-only

Get one Laposta mailing list by ID.
Returns the list object: list_id, name, state, locked, remarks, notification emails and member counts.
Use laposta_lists_list to find the ID first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.

Example input: `{"list_id":"<list_id>"}`

### `laposta_lists_list`

List Lists · Read-only

List all mailing lists in the Laposta account.
Returns data[] of list objects with list_id, name, state, locked, remarks and member counts (active, unsubscribed, cleaned).
Use laposta_lists_list to find a list_id. Use laposta_list_get for one list.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `laposta_member_get`

Get Subscriber · Read-only

Get one subscriber of a Laposta list by member ID or email address.
Returns the member object: member_id, email, state, signup and confirm dates, ip, source_url and custom_fields.
Use laposta_members_list to search a list.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `member_id` (`string`, required): Member ID or the subscriber's email address. Write a + in an email address as %2B. Example: Du83Hyjhj8.

Example input: `{"list_id":"<list_id>","member_id":"<member_id>"}`

### `laposta_member_history_get`

Get Subscriber History · Read-only

Get the event history of a Laposta subscriber: subscriptions, sends, opens, clicks, bounces and automation steps.
Returns data[] of events with type, event_date, campaign and details, plus pagination with has_more and next_cursor.
Use laposta_campaign_history_get for all events of one campaign.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `member_id` (`string`, required): Member ID or the subscriber's email address. Example: Du83Hyjhj8.
- `campaign_id` (`string`, optional): Only events of this campaign. Leave empty for the full history. Example: njhgaf61ye.
- `cursor` (`string`, optional): pagination.next_cursor from the previous page, sent back unchanged. Keep the same filters when paging.
- `event_date_from` (`string`, optional): Only events from this date and time, inclusive. Regular format YYYY-MM-DD HH:MM:SS (account timezone) or ISO 8601. Example: 2026-04-01 00:00:00.
- `event_date_to` (`string`, optional): Only events before this date and time, exclusive. Regular format YYYY-MM-DD HH:MM:SS (account timezone) or ISO 8601. Example: 2026-05-01 00:00:00.
- `limit` (`integer`, optional): Maximum events per page, 1-1000 (Laposta default 100). Example: 100.
- `order` (`string`, optional): Sort direction, desc (default) or asc. One of: `desc`, `asc`.
- `order_by` (`string`, optional): Field to sort by. Only event_date is supported. One of: `event_date`.

Example input: `{"list_id":"<list_id>","member_id":"<member_id>"}`

### `laposta_members_list`

List Subscribers · Read-only

List subscribers of a Laposta list, optionally by state, label or search term, in pages when limit or cursor is sent.
Returns data[] of member objects (member_id, email, state, signup_date, custom_fields) and, when paged, a pagination object with next_cursor.
Use laposta_member_get for one subscriber by ID or email.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `cursor` (`string`, optional): pagination.next_cursor from the previous page, sent back unchanged with the same other filters.
- `label` (`string`, optional): Only subscribers carrying this label, by exact name. One label per request. Example: Customer.
- `limit` (`integer`, optional): Subscribers per page, up to 1000 (default 100). Sending limit or cursor switches to paged results; without either the whole list comes back at once. Example: 100.
- `order` (`string`, optional): Sort direction for order_by: asc (default) or desc. One of: `asc`, `desc`.
- `order_by` (`string`, optional): Sort by email, signup_date or a text field's tag without braces; comma-separate several. Example: lastname,firstname.
- `search` (`string`, optional): Only subscribers whose email or text, numeric or select field values contain this text (case-insensitive, up to 255 characters). Example: example.net.
- `state` (`string`, optional): Only subscribers with this status: active, unsubscribed or cleaned. One of: `active`, `unsubscribed`, `cleaned`.

Example input: `{"list_id":"<list_id>"}`

### `laposta_report_get`

Get Campaign Report · Read-only

Get the results of one Laposta campaign.
Returns sent, accepted, opened, clicked, webversion, cleaned, complained, hardbounced and unsubscribed counts, unique counts and ratios.
Use laposta_campaign_history_get for per-subscriber events.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `campaign_id` (`string`, required): ID of the campaign. Find it with laposta_campaigns_list. Example: njhgaf61ye.

Example input: `{"campaign_id":"<campaign_id>"}`

### `laposta_reports_list`

List Campaign Reports · Read-only

Get the results of all campaigns in the Laposta account.
Returns data[] of report objects per campaign with sent, accepted, opened, clicked, bounced, unsubscribed and complained counts and ratios.
Use laposta_report_get for one campaign.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `laposta_segment_get`

Get Segment · Read-only

Get one segment of a Laposta list.
Returns the segment object with segment_id, name and its definition (a JSON string).
Copy a definition built in the app to create similar segments with laposta_segment_create.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `segment_id` (`string`, required): ID of the segment. Example: pDrp5KOD0z.

Example input: `{"list_id":"<list_id>","segment_id":"<segment_id>"}`

### `laposta_segments_list`

List Segments · Read-only

List all segments of a Laposta list.
Returns data[] of segment objects with segment_id, name and definition.
Use laposta_segment_get for one segment.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.

Example input: `{"list_id":"<list_id>"}`

### `laposta_webhook_get`

Get Webhook · Read-only

Get one webhook of a Laposta list.
Returns the webhook object: webhook_id, event, url, blocked, state and secret for verifying X-Laposta-Signature.
Use laposta_webhooks_list to find the webhook_id.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `webhook_id` (`string`, required): ID of the webhook. Example: cW5ls8IVJl.

Example input: `{"list_id":"<list_id>","webhook_id":"<webhook_id>"}`

### `laposta_webhooks_list`

List Webhooks · Read-only

List the webhooks of a Laposta list.
Returns data[] of webhook objects with webhook_id, event, url, blocked, state and signing secret.
Use laposta_webhook_get for one webhook.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.

Example input: `{"list_id":"<list_id>"}`

### `laposta_automation_refresh`

Activate Automation Changes · Write

Activate the changes made to an active Laposta automation since it was last activated, like the Activate changes button in the app.
Returns the automation object; on a failed check the previous version keeps running and the error lists each problem.
Use laposta_automation_start for an inactive automation.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `automation_id` (`string`, required): ID of the automation. Find it with laposta_automations_list. Example: pdq4k7wqcm.

Example input: `{"automation_id":"<automation_id>"}`

### `laposta_automation_start`

Start Automation · Write

Activate an inactive Laposta automation, like the Activate button in the app. It is checked first and stays inactive if something is wrong.
Returns the automation object, or an error whose details list each problem.
Use laposta_automation_refresh to activate changes to an automation that is already active.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `automation_id` (`string`, required): ID of the automation. Find it with laposta_automations_list. Example: pdq4k7wqcm.

Example input: `{"automation_id":"<automation_id>"}`

### `laposta_automation_stop`

Stop Automation · Write

Pause an active Laposta automation, like the Pause button in the app. Members stay where they are and continue when it is started again.
Returns the automation object.
Use laposta_automation_start to resume.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `automation_id` (`string`, required): ID of the automation. Find it with laposta_automations_list. Example: pdq4k7wqcm.

Example input: `{"automation_id":"<automation_id>"}`

### `laposta_campaign_content_update`

Set Campaign Content · Write

Fill a Laposta campaign with HTML, or import the HTML from a URL. If both are given, html is used.
Returns the content with a report of import problems such as no_unsubscribe, css or images.
Run this after laposta_campaign_create and before sending; Laposta adds an unsubscribe link if the HTML has none.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `campaign_id` (`string`, required): ID of the campaign. Find it with laposta_campaigns_list. Example: njhgaf61ye.
- `html` (`string`, optional): Full HTML of the email. Required unless import_url is given. Example: <html><body><h1>News</h1></body></html>.
- `import_url` (`string`, optional): URL Laposta imports the HTML from. Required unless html is given. Example: https://example.net/newsletter.
- `inline_css` (`boolean`, optional): Move CSS inline into the HTML elements. true or false.

Example input: `{"campaign_id":"<campaign_id>"}`

### `laposta_campaign_create`

Create Campaign · Write

Create a regular email campaign in Laposta with its sender, subject and recipient lists.
Returns the new campaign object with its campaign_id.
Next fill it with laposta_campaign_content_update, then send it with laposta_campaign_send or laposta_campaign_schedule.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `from_email` (`string`, required): Sender email address. It must be a sender address approved in the Laposta app. Example: max@example.net.
- `from_name` (`string`, required): Sender name, up to 255 characters. Example: Max de Vries.
- `list_ids` (`array`, required): Recipients: IDs of lists, and of segments if needed. Example: ["nnhnkrytua", "srbhotdwob"].
- `name` (`string`, required): Internal campaign name, up to 255 characters. Example: Test via API.
- `subject` (`string`, required): Email subject line, up to 255 characters. Example: Hello from us.
- `type` (`string`, required): Campaign type. Only regular is supported. One of: `regular`.
- `previewtext` (`string`, optional): Preview text shown after the subject in many inboxes, up to 120 characters. Example: Our news of this month.
- `reply_to` (`string`, optional): Email address that receives replies. Example: reply@example.net.
- `stats_ga` (`boolean`, optional): Link Google Analytics to the campaign's links. true or false.

Example input: `{"from_email":"<from_email>","from_name":"<from_name>","list_ids":["nnhnkrytua","srbhotdwob"],"name":"<name>","subject":"<subject>","type":"regular"}`

### `laposta_campaign_schedule`

Schedule Campaign · Write

Schedule a Laposta campaign for a later date and time.
Returns the campaign object with delivery_requested set.
Use laposta_campaign_send to send right away.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `campaign_id` (`string`, required): ID of the campaign. Find it with laposta_campaigns_list. Example: njhgaf61ye.
- `delivery_requested` (`string`, required): When to send. Regular format YYYY-MM-DD HH:MM:SS (account timezone) or ISO 8601. Example: 2026-12-01 09:00:00.

Example input: `{"campaign_id":"<campaign_id>","delivery_requested":"<delivery_requested>"}`

### `laposta_campaign_send`

Send Campaign · Write

Send a Laposta campaign right away to its lists. A campaign sent before is sent again only to subscribers added since the last send.
Returns the campaign object.
Use laposta_campaign_schedule to send later and laposta_campaign_testmail to test first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `campaign_id` (`string`, required): ID of the campaign. Find it with laposta_campaigns_list. Example: njhgaf61ye.

Example input: `{"campaign_id":"<campaign_id>"}`

### `laposta_campaign_testmail`

Send Campaign Test · Write

Send a test email of an unsent Laposta campaign that already has content.
Returns the campaign object.
Use before laposta_campaign_send to check the email.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `campaign_id` (`string`, required): ID of the campaign. Find it with laposta_campaigns_list. Example: njhgaf61ye.
- `email` (`string`, required): Address to send the test to. Example: test@example.net.

Example input: `{"campaign_id":"<campaign_id>","email":"<email>"}`

### `laposta_campaign_update`

Update Campaign · Write

Change the name, subject, sender, reply-to address or recipients of a Laposta campaign. Only the fields you send change.
Returns the updated campaign object.
Use laposta_campaign_content_update to change the email body.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `campaign_id` (`string`, required): ID of the campaign. Find it with laposta_campaigns_list. Example: njhgaf61ye.
- `from_email` (`string`, optional): Sender email address. It must be a sender address approved in the Laposta app. Example: max@example.net.
- `from_name` (`string`, optional): Sender name, up to 255 characters. Example: Max de Vries.
- `list_ids` (`array`, optional): Recipients: IDs of lists, and of segments if needed. Example: ["nnhnkrytua", "srbhotdwob"].
- `name` (`string`, optional): Internal campaign name, up to 255 characters. Example: Test via API.
- `previewtext` (`string`, optional): Preview text shown after the subject in many inboxes, up to 120 characters. Example: Our news of this month.
- `reply_to` (`string`, optional): Email address that receives replies. Example: reply@example.net.
- `stats_ga` (`boolean`, optional): Link Google Analytics to the campaign's links. true or false.
- `subject` (`string`, optional): Email subject line, up to 255 characters. Example: Hello from us.

Example input: `{"campaign_id":"<campaign_id>"}`

### `laposta_field_create`

Create Field · Write

Add an extra subscriber field to a Laposta list.
Returns the new field object, with its custom_name for use in custom_fields.
The labels field cannot be created through the API.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `datatype` (`string`, required): Data type: text, numeric, date, select_single or select_multiple. One of: `text`, `numeric`, `date`, `select_single`, `select_multiple`.
- `in_form` (`boolean`, required): Whether the field appears in the subscription form. true or false.
- `in_list` (`boolean`, required): Whether the field is shown in Laposta's subscriber overview. true or false.
- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `name` (`string`, required): Display name of the field. Example: Color.
- `required` (`boolean`, required): Whether subscribers must fill in this field. true or false.
- `datatype_display` (`string`, optional): Display style: select or radio for select_single; input (one line, up to 255 characters) or textarea (up to 10,000 characters) for text. One of: `select`, `radio`, `input`, `textarea`.
- `defaultvalue` (`string`, optional): Default value used when the field is left empty. Example: Green.
- `options` (`array`, optional): Selectable options; required for select_single and select_multiple. Example: ["Red", "Green", "Blue"].

Example input: `{"datatype":"text","in_form":true,"in_list":true,"list_id":"<list_id>","name":"<name>","required":true}`

### `laposta_field_update`

Update Field · Write

Change a field of a Laposta list. Only the parts you send change; changing the datatype erases the field's data.
Returns the updated field object.
To change select options send options_full with every option to keep; the labels field cannot be changed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `field_id` (`string`, required): ID of the field to change. Example: hsJ5zbDfzJ.
- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `datatype` (`string`, optional): New data type. Changing it removes all data stored in the field. One of: `text`, `numeric`, `date`, `select_single`, `select_multiple`.
- `datatype_display` (`string`, optional): Display style: select or radio for select_single; input (one line, up to 255 characters) or textarea (up to 10,000 characters) for text. One of: `select`, `radio`, `input`, `textarea`.
- `defaultvalue` (`string`, optional): Default value used when the field is left empty. Example: Green.
- `in_form` (`boolean`, optional): Whether the field appears in the subscription form. true or false.
- `in_list` (`boolean`, optional): Whether the field is shown in Laposta's subscriber overview. true or false.
- `name` (`string`, optional): New display name. Example: Favourite color.
- `options_full` (`object`, optional): Complete set of options for a select field as a map of option ID to label. Keep an existing numeric ID to keep or rename that option, use a non-numeric key such as new-0 to add one, and leave an ID out to delete it. Example: {"1": "Red", "2": "Lime Green", "new-0": "Orange"}.
- `required` (`boolean`, optional): Whether subscribers must fill in this field. true or false.

Example input: `{"field_id":"<field_id>","list_id":"<list_id>"}`

### `laposta_list_create`

Create List · Write

Create a new Laposta mailing list.
Returns the new list object with its list_id.
Add extra subscriber fields afterwards with laposta_field_create.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Name of the list. Example: Testlist.
- `locked` (`boolean`, optional): Lock the list so users of the Laposta app cannot change it. true or false.
- `remarks` (`string`, optional): Free-text remarks about the list. Example: A list for testing purposes.
- `subscribe_notification_email` (`string`, optional): Email address that gets a notification on each new subscription. Example: subscription@example.net.
- `unsubscribe_notification_email` (`string`, optional): Email address that gets a notification on each unsubscription. Example: unsubscription@example.net.

Example input: `{"name":"<name>"}`

### `laposta_list_members_sync`

Bulk Sync List Members · Write

Add, update and optionally unsubscribe many subscribers of a Laposta list in one request (paid accounts only).
Returns a report that sorts each submitted member into added, edited, skipped and errors.
Use laposta_member_create or laposta_member_update for a single subscriber. Including unsubscribe_excluded unsubscribes every member not in the request.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `actions` (`array`, required): What the sync may do: add (new members), update (existing members) and/or unsubscribe_excluded (unsubscribe every active member NOT in members; only send this with the complete member list). Example: ["add", "update"].
- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `members` (`array`, required): Member objects, 1 to 500,000. Each needs an email or a member_id (the ID or email of an existing member, with email then giving a new address), and may carry custom_fields (keyed by custom_name), source_url and state. Example: [{"email": "maartje@example.net", "custom_fields": {"name": "Maartje"}}].

Example input: `{"actions":["add","update"],"list_id":"<list_id>","members":[{"email":"maartje@example.net","custom_fields":{"name":"Maartje"}}]}`

### `laposta_list_update`

Update List · Write

Change the name, lock, remarks or notification addresses of a Laposta list. Only the fields you send change.
Returns the updated list object.
Use laposta_list_get to read the current values.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `locked` (`boolean`, optional): Lock the list so users of the Laposta app cannot change it. true or false.
- `name` (`string`, optional): New name for the list. Example: Customers.
- `remarks` (`string`, optional): Free-text remarks about the list. Example: A list for testing purposes.
- `subscribe_notification_email` (`string`, optional): Email address that gets a notification on each new subscription. Example: subscription@example.net.
- `unsubscribe_notification_email` (`string`, optional): Email address that gets a notification on each unsubscription. Example: unsubscription@example.net.

Example input: `{"list_id":"<list_id>"}`

### `laposta_member_create`

Add Subscriber · Write

Add a subscriber to a Laposta list. On a double opt-in list a confirmation email is sent unless options.ignore_doubleoptin is true.
Returns the new member object with its member_id.
Set options.upsert to update an existing subscriber instead of getting an error; use laposta_list_members_sync for many at once.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, required): Email address of the subscriber. Example: maartje@example.net.
- `ip` (`string`, required): IP address the subscriber signed up from. Use your server's IP for API imports. Example: 198.51.100.0.
- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `custom_fields` (`object`, optional): Values for the list's extra fields, keyed by each field's custom_name (see laposta_fields_list). Multi-select fields and labels take an array of existing option or label names. Example: {"name": "Maartje de Vries", "children": 2, "prefs": ["optionA", "optionB"]}.
- `options` (`object`, optional): Extra instructions, each true or false: upsert (update the subscriber if the email is already on the list, which also reactivates an unsubscribed one), suppress_reactivation (with upsert, keep unsubscribed subscribers unsubscribed), suppress_email_notification, ignore_doubleoptin (activate right away with no confirmation email) and spam_check (treat as a public form submission). Example: {"upsert": true, "ignore_doubleoptin": true}.
- `source_url` (`string`, optional): URL the subscriber signed up from. Example: https://example.com/signup.
- `user_agent` (`string`, optional): The subscriber's browser User-Agent, used only by the spam check. Example: Mozilla/5.0.

Example input: `{"email":"<email>","ip":"<ip>","list_id":"<list_id>"}`

### `laposta_member_update`

Update Subscriber · Write

Change a Laposta subscriber's email, state or custom fields. Only the fields you send change.
Returns the updated member object.
Set state to unsubscribed to unsubscribe; labels in custom_fields replace the subscriber's current labels.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `member_id` (`string`, required): Member ID or the subscriber's current email address. Example: 9978ydioiZ.
- `custom_fields` (`object`, optional): Values for the list's extra fields, keyed by each field's custom_name (see laposta_fields_list). Multi-select fields and labels take an array of existing option or label names. Example: {"name": "Maartje de Vries", "children": 2, "prefs": ["optionA", "optionB"]}.
- `email` (`string`, optional): New email address. Example: maartje.new@example.net.
- `state` (`string`, optional): New status: active or unsubscribed. One of: `active`, `unsubscribed`.

Example input: `{"list_id":"<list_id>","member_id":"<member_id>"}`

### `laposta_segment_create`

Create Segment · Write

Create a segment of a Laposta list from a definition.
Returns the new segment object with its segment_id.
Build the segment in the Laposta app first and copy its definition from laposta_segment_get; definitions are hard to write by hand.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `definition` (`string`, required): Segment definition as Laposta stores it, a string in JSON format; copy it from laposta_segment_get. Example: {"postcode"} = '1234AB'.
- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `name` (`string`, required): Name of the segment. Example: Contacts with postal code 1234AB.

Example input: `{"definition":"<definition>","list_id":"<list_id>","name":"<name>"}`

### `laposta_segment_update`

Update Segment · Write

Change the name or definition of a Laposta segment. Only the fields you send change.
Returns the updated segment object.
Use laposta_segment_get to read the current definition.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `segment_id` (`string`, required): ID of the segment to change. Example: pDrp5KOD0z.
- `definition` (`string`, optional): New segment definition, a string in JSON format as returned by laposta_segment_get.
- `name` (`string`, optional): New name of the segment. Example: Contacts in Amsterdam.

Example input: `{"list_id":"<list_id>","segment_id":"<segment_id>"}`

### `laposta_webhook_create`

Create Webhook · Write

Register a webhook that Laposta POSTs to when subscribers of a list are added, changed or deactivated.
Returns the new webhook object with its webhook_id and signing secret.
Webhooks are not called for changes made through the API unless enabled in the account.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `blocked` (`boolean`, required): Create the webhook paused (true) or active (false).
- `event` (`string`, required): When to call the webhook: subscribed, modified or deactivated. One of: `subscribed`, `modified`, `deactivated`.
- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `url` (`string`, required): URL Laposta POSTs the events to. Example: https://example.com/webhook.

Example input: `{"blocked":true,"event":"subscribed","list_id":"<list_id>","url":"<url>"}`

### `laposta_webhook_update`

Update Webhook · Write

Change the event, URL or blocked status of a Laposta webhook. Only the fields you send change.
Returns the updated webhook object.
Set blocked to true to pause a webhook without deleting it.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `webhook_id` (`string`, required): ID of the webhook to change. Example: JH_y9dEsfH.
- `blocked` (`boolean`, optional): true pauses the webhook, false resumes it.
- `event` (`string`, optional): When to call the webhook: subscribed, modified or deactivated. One of: `subscribed`, `modified`, `deactivated`.
- `url` (`string`, optional): New URL for the webhook. Example: https://example.com/dir/webhook.

Example input: `{"list_id":"<list_id>","webhook_id":"<webhook_id>"}`

### `laposta_campaign_delete`

Delete Campaign · Destructive

Delete a Laposta campaign. Unsent campaigns are deleted at once; sent ones can be restored in the app for 180 days.
Returns the campaign object with state deleted.
Use laposta_campaigns_list to find the campaign_id.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `campaign_id` (`string`, required): ID of the campaign to delete. Example: az0ndh7akc.

Example input: `{"campaign_id":"<campaign_id>"}`

### `laposta_field_delete`

Delete Field · Destructive

Permanently delete a field from a Laposta list, with its data.
Returns the field object with state deleted.
The labels field cannot be deleted through the API.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `field_id` (`string`, required): ID of the field to delete. Example: lxwc8OyD3a.
- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.

Example input: `{"field_id":"<field_id>","list_id":"<list_id>"}`

### `laposta_list_delete`

Delete List · Destructive

Permanently delete a Laposta list and its subscribers.
Returns the list object with state deleted.
Use laposta_list_members_purge to empty a list but keep it.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.

Example input: `{"list_id":"<list_id>"}`

### `laposta_list_members_purge`

Purge List Members · Destructive

Permanently remove all active subscribers from a Laposta list, keeping the list itself.
Returns the list object.
Use laposta_list_delete to remove the list too.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.

Example input: `{"list_id":"<list_id>"}`

### `laposta_member_delete`

Delete Subscriber · Destructive

Permanently delete a subscriber from a Laposta list.
Returns the member object with state deleted.
Use laposta_member_update with state unsubscribed to unsubscribe instead.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `member_id` (`string`, required): Member ID or the subscriber's email address. Example: 9978ydioiZ.

Example input: `{"list_id":"<list_id>","member_id":"<member_id>"}`

### `laposta_segment_delete`

Delete Segment · Destructive

Permanently delete a segment of a Laposta list. Subscribers are not affected.
Returns the deleted segment object.
Use laposta_segments_list to find the segment_id.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `segment_id` (`string`, required): ID of the segment to delete. Example: pDrp5KOD0z.

Example input: `{"list_id":"<list_id>","segment_id":"<segment_id>"}`

### `laposta_webhook_delete`

Delete Webhook · Destructive

Permanently delete a webhook of a Laposta list. Calls already queued are still delivered.
Returns the webhook object with state deleted.
Use laposta_webhook_update with blocked true to pause instead.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the Laposta list. Find it with laposta_lists_list or in the app under Subscribers > the list > Attributes list. Example: BaImMu3JZA.
- `webhook_id` (`string`, required): ID of the webhook to delete. Example: 8HdlEGtlml.

Example input: `{"list_id":"<list_id>","webhook_id":"<webhook_id>"}`

## Related

Other Marketing connectors ([all 190](/agentkit/connectors/?category=marketing)):

- [HubSpot](/agentkit/connectors/hubspot/): Scalekit connector, OAuth, 457 tools
- [Mailchimp](/agentkit/connectors/mailchimp/): Scalekit connector, OAuth, 73 tools
- [Twitter / X](/agentkit/connectors/twitteroauth/): Scalekit connector, OAuth, 92 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
