# Activities API & Webhooks

## Overview

<code class="expression">space.vars.activities</code> can be managed programmatically through the <code class="expression">space.vars.Kizen\_company\_name</code> API and webhooks, enabling external systems and internal <code class="expression">space.vars.automations</code> to schedule, retrieve, and respond to <code class="expression">space.vars.activity</code> state changes in near real time.

Each subpage focuses on a specific use case, such as scheduling <code class="expression">space.vars.activities</code>, retrieving logged <code class="expression">space.vars.activity</code> details, or triggering external workflows when <code class="expression">space.vars.activities</code> are created or completed.

### How Activities Are Exposed Programmatically

<code class="expression">space.vars.activities</code> are available through APIs and webhooks in ways that align with their lifecycle:

* Scheduled <code class="expression">space.vars.activities</code> support planning and coordination use cases
* Logged <code class="expression">space.vars.activities</code> provide a durable record of completed interactions
* Lifecycle events emit webhook notifications that can drive downstream workflows

All API and webhook behavior respects <code class="expression">space.vars.activity</code> Objects, permissions, and record associations, ensuring consistent behavior across UI, <code class="expression">space.vars.automations</code>, and external integrations.

### When to Use APIs vs Webhooks

In general:

* Use APIs when you need to create or access <code class="expression">space.vars.activity</code> data on demand
* Use webhooks when you need to react automatically to <code class="expression">space.vars.activity</code> lifecycle events

Many integrations use both together, using APIs for data access and webhooks for event-driven workflows.

***

## API Topics in this Section

* [Scheduling Activities](/docs/concepts/activities/activities-api-and-webhooks/schedule-activities-api.md)
* [Viewing Logged Activity Details](/docs/concepts/activities/activities-api-and-webhooks/view-logged-activity-details-api.md)
* [Listing Scheduled Activities](/docs/concepts/activities/activities-api-and-webhooks/list-scheduled-activities-api.md)
* [Retrieving Scheduled Activity Details by ID](/docs/concepts/activities/activities-api-and-webhooks/retrieve-scheduled-activity-details-by-id-api.md)
* [Triggering External Workflows with Activity Webhooks](/docs/concepts/activities/activities-api-and-webhooks/triggering-external-activity-workflows-with-webhooks.md)

***

## What’s Next

Review the individual topics in this section to learn how to work with specific <code class="expression">space.vars.activity</code> endpoints, and webhook events. Each page includes an endpoint or event details, examples, and usage considerations.

<details>

<summary>Related Topics</summary>

* [Activities](/docs/concepts/activities.md)
* [Activities Core Concepts](/docs/concepts/activities/activities-core-concepts.md)
* [Activities Data Model](/docs/concepts/activities/activities-data-model.md)
* [Activity Permissions](/docs/concepts/activities/activity-permissions.md)
* [Advanced Activity Rules](/docs/concepts/activities/advanced-activity-rules.md)

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.kizen.com/docs/concepts/activities/activities-api-and-webhooks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.