RASL | Statuses

Statuses are commonly used to track customer lifecycle stages, lead progression, engagement states, or internal workflow classifications.

This module helps organize contacts and enables structured segmentation across messaging and automation workflows.

Overview

A status represents the current state or classification of a contact.

Common examples include:

New Lead

Interested

Active Customer

Pending Follow-up

Converted

VIP Customer

Inactive

Blocked

Statuses improve operational visibility and simplify customer management processes.

Available Endpoints

GET /statuses

List Statuses
Retrieve a paginated list of all statuses.

POST /statuses

Create Status
Create a new custom status.

GET /statuses/{id}

Get Status
Retrieve detailed information for a specific status.

PATCH /statuses/{id}

Update Status
Update status properties such as name, color, or description.

DELETE /statuses/{id}

Delete Status
Permanently delete a status from your tenant.

Deleting a status does not delete associated contacts.

Common Behavior

Contacts can be assigned statuses for segmentation and workflow management.

Statuses are commonly used in CRM processes, automation rules, and reporting.

Deleting a status removes the classification only and does not affect contact records.

Statuses can be updated dynamically throughout the customer lifecycle.

Required Scopes

Depending on the operation, your API token must include:

statuses:read

statuses:write

statuses:delete

Ensure the correct scopes are assigned when creating your V2 API token.

Use Cases

Lead pipeline tracking

Customer lifecycle management

CRM workflow organization

Automation triggers

Sales follow-up management

Customer segmentation and reporting

The Statuses module enables structured customer state management within RASL and improves operational organization across messaging and automation systems.

The Statuses API allows you to define and manage custom contact statuses within your RASL tenant

Overview#

Available Endpoints#

GET /statuses#

POST /statuses#

GET /statuses/{id}#

PATCH /statuses/{id}#

DELETE /statuses/{id}#

Common Behavior#

Required Scopes#

Use Cases#