Skip to main content

Multi Organizations

The Organizations feature allows you to manage multiple clients, businesses, or projects within a single LoopMessage account while keeping their messaging resources and API configurations separate.

Each organization has its own unique API Key, Webhook URL, and assigned Sender Names, allowing you to create independent messaging environments without registering multiple LoopMessage accounts.

This feature is particularly useful for agencies, SaaS platforms, white-label providers, and businesses that need to manage messaging for multiple customers or projects.

1. What is an Organization?

An Organization is a separate workspace within your LoopMessage account.

Each organization can have its own:

  • API Key: Unique credentials for accessing the LoopMessage API.
  • Webhook URL: A separate endpoint for receiving incoming messages, delivery statuses, and other events.
  • Webhook Authorization Header: An optional custom value for authenticating webhook requests.
  • Sender Names: Dedicated phone numbers or email-based sender names assigned to that organization.
  • Messaging History: Message and conversation records associated with the organization.
  • Organization Settings: Configuration options for supported features, such as Data Retention and Deferred Messages.

This structure allows you to keep messaging activity and integrations organized without mixing resources belonging to different clients or business projects.

For example, you can use one organization for your primary business, another for a separate product, and additional organizations for each customer you manage.

2. Default Organization: Your Master Organization

When you create a LoopMessage account, a Default organization is automatically created.

This is the first organization in your account, and it acts as your Master Organization.

Unlike additional organizations, the Default organization cannot be deleted.

What makes the Default organization special?

The Default organization has administrative privileges that allow you to manage other organizations within your account through the API.

Using the Default organization’s API Key, you can:

  • Retrieve a list of all organizations in your account.
  • Create new organizations.
  • Retrieve information about other organizations.
  • Update organization settings.
  • Delete eligible organizations.

These administrative operations are available through the Organizations API.

How is the Default API Key different?

There is an important distinction between API keys belonging to the Default organization and those belonging to additional organizations.

Default Organization API Key (Master Key)

This key provides account-level administrative capabilities through the supported Organizations API endpoints.

It can be used to create, update, and manage other organizations.

Regular Organization API Key

An API Key belonging to any additional organization is scoped to that specific organization.

For example, when using Organization A’s API Key, you cannot retrieve or manage Organization B’s resources through organization-scoped operations.

This separation allows your applications to use different credentials for each customer or project.

Security recommendation: Treat your Default organization’s API Key as a highly privileged credential. Never expose it in frontend applications or share it with customers. Use separate organization-specific API keys for individual integrations.

3. Separate Sender Names for Each Organization

One of the primary benefits of Organizations is the ability to assign sender names to specific organizations.

Each organization can have its own set of phone numbers or email-based sender names.

For example, imagine you operate an agency serving three clients.

Your account might look like this:

Default Organization (Master)

  • Manages organizations through the API.
  • Controls administrative operations.

Organization A — Client A

  • Phone Number A1
  • Phone Number A2
  • API Key A
  • Webhook URL A

Organization B — Client B

  • Phone Number B1
  • API Key B
  • Webhook URL B

Organization C — Client C

  • Phone Number C1
  • Phone Number C2
  • API Key C
  • Webhook URL C

Each organization has its own assigned sender names.

When sending messages through Organization A’s API Key, your application works with the sender names assigned to Organization A.

This helps prevent accidentally sending messages from another customer’s phone numbers.

Can I move a Sender Name between organizations?

Yes. You can reassign an existing sender name to another organization.

This can be useful if you are reorganizing your projects or transferring messaging resources between customers.

The LoopMessage API supports changing a sender’s organization by updating its organization_id.

Learn more in the Manage Sender Name API.

4. Separate API Keys and Webhook URLs

Every organization has its own API credentials and webhook configuration.

This makes it possible to connect different organizations to completely different applications or backend systems.

Separate API Keys

For example, suppose you manage two applications:

  • Application A uses Organization A’s API Key.
  • Application B uses Organization B’s API Key.

Each application communicates with LoopMessage using its own credentials.

This helps keep messaging operations separated and reduces the need to share the same API credentials across unrelated systems.

You can find the API Key for a specific organization by opening the LoopMessage Dashboard, selecting the organization, and navigating to:

API → Settings

Learn more in the API Credentials documentation.

Separate Webhook URLs

You can configure a different Webhook URL for every organization.

For example:

Organization A

https://client-a.example.com/webhooks/loopmessage

Organization B

https://client-b.example.com/webhooks/loopmessage

When an incoming message or another supported event occurs, LoopMessage sends the webhook notification to the endpoint configured for the corresponding organization.

This makes it possible to process events independently.

You can also configure a custom authorization header value for each organization to help your backend authenticate incoming webhook requests.

Learn more in the Webhooks documentation.

5. How to Create and Configure Organizations

You can manage organizations through the LoopMessage Dashboard or programmatically using the Organizations API.

Step 1: Open the LoopMessage Dashboard

Sign in to your LoopMessage account.

Your Default organization will already be available.

Open the organization management interface to create or manage additional organizations.

Step 2: Create a new Organization

Create an organization for your client, business, or project.

Depending on the interface, you may need to provide information such as:

  • Organization Name
  • Website
  • Support URL
  • Country

Give your organization a recognizable name so you can easily identify it in the Dashboard.

Step 3: Configure the API and Webhooks

Select your newly created organization.

Navigate to API → Settings to access its API credentials and configure the webhook integration.

Each organization uses its own unique API Key.

If you’re connecting the organization to a separate backend or CRM, configure the corresponding Webhook URL.

Step 4: Assign Sender Names

Assign one or more sender names to the organization.

You can order new sender names or reassign existing ones, depending on your requirements.

Once assigned, those sender names become part of that organization’s messaging resources.

Step 5: Start using the Organization

Your organization is ready to be integrated with your application.

Use its unique API Key when sending requests and its configured Webhook URL to receive events.

You can switch between organizations in the Dashboard to manage each environment separately.

6. Manage Organizations through the API

If you operate a SaaS platform, CRM, or reseller service, you may prefer to create and manage organizations automatically.

LoopMessage provides an Organizations API that supports:

  • Creating organizations.
  • Listing all organizations.
  • Retrieving organization details.
  • Updating organization information.
  • Configuring webhook settings.
  • Deleting eligible organizations.

For example, when a new customer registers on your SaaS platform, your backend can automatically create a corresponding LoopMessage organization.

A typical onboarding workflow might look like this:

  1. Your customer registers on your platform.
  2. Your backend creates a new organization using the Default organization’s API Key.
  3. LoopMessage returns the new organization’s ID and API credentials.
  4. Your backend securely stores the organization information.
  5. Your backend provisions or assigns sender names to the organization.
  6. Your customer’s application starts communicating through its organization-specific API Key.

This makes it possible to automate customer onboarding without manually configuring every organization in the Dashboard.

Important: Creating organizations through the API requires active paid services and is not supported in the Sandbox environment.

7. Common Use Cases

Agencies managing multiple clients

If you’re an agency providing messaging services to multiple businesses, you can create a separate organization for each client.

Each client receives its own messaging resources, API credentials, and webhook configuration.

This makes it easier to manage customers independently without creating a separate LoopMessage account for each one.

White-label and Reseller Platforms

Organizations are especially useful for building white-label messaging platforms.

Your application can create and manage organizations through the API while providing customers with your own branded interface.

You can manage customer onboarding, provisioning, and messaging integrations programmatically.

Learn more about the White-Label & Resellers use case.

SaaS and CRM Platforms

If your software serves multiple businesses, you can create a separate LoopMessage organization for each customer.

Your application can associate each customer account with its own LoopMessage organization and API credentials.

This helps keep customer messaging resources separated while allowing your backend to manage the integration centrally.

Multiple Brands or Projects

Organizations can also be useful when you operate multiple brands or products.

For example, you might use:

  • Organization A for your e-commerce store.
  • Organization B for your customer support service.
  • Organization C for your marketing platform.

Each project can have its own sender names, webhook integrations, and organization-specific configuration.

8. Organization-Specific Feature Settings

Some LoopMessage features are configured independently for each organization.

For example:

Data Retention

You can configure how long LoopMessage retains supported message, webhook, and API request history for each organization.

This is useful when different clients have different data-retention requirements.

Learn more about Data Retention.

Deferred Messages

You can independently enable Deferred Messages and configure custom sending schedules for each organization.

For example, one organization may permit deferred sending during business hours, while another may use a different schedule.

Learn more about Deferred Messages.

S3 Bucket Integration

Organizations can also have separate attachment storage configurations.

For example, different clients can connect their own S3-compatible storage destinations for supported inbound message attachments.

Learn more about the S3 Bucket Integration.

9. Important Considerations

Default Organization

The Default organization is created automatically and cannot be deleted. Its API Key has additional administrative privileges.

Separate Credentials

Every organization has a unique API Key. Keep these credentials secure and use the appropriate key for each integration.

Sender Assignment

Sender names belong to their assigned organization. If necessary, you can move an existing sender name to another organization using the supported API.

Organization Deletion

Additional organizations can be deleted, but they must not have any active sender names assigned to them.

Sandbox Limitations

The Sandbox environment is available only for the Default organization. Some organization-management operations require active paid services.

Access and Billing

Organizations provide separation for messaging resources and API configurations. They do not automatically create independent LoopMessage accounts, separate customer logins, or individual billing relationships.

If you’re building a multi-tenant or white-label platform, your own application should implement the appropriate customer authentication, permissions, and billing logic.

Getting Started

If you manage more than one business, customer, or project, we recommend creating a separate organization for each environment that requires independent messaging resources.

Your Default organization serves as the central administrative organization, while additional organizations provide separate API credentials, webhook configurations, and assigned sender names.

This makes it easier to build scalable integrations, manage multiple customers, and keep your messaging infrastructure organized within a single LoopMessage account.

One account. Multiple organizations. Separate messaging environments.