Skip to content
SENDLY by ACTIOSENDLY by ACTIO
Blog
News8 min·

SMS API: multiple tokens and sender names on one account

With SENDLY, you can use multiple SMS API tokens and multiple SMS sender names within a single account. A separate token authenticates each integration, while the sender name, or Sender ID, determines the name recipients see on a message. This setup suits agencies, software development companies and businesses running several applications or brands while keeping a shared budget and centralized billing. These new capabilities are complemented by 2FA for dashboard sign-in and a pay-as-you-go model – no subscription, with 100 free SMS to get started.

Multiple SMS API tokens – a separate key for each integration

An API token is a confidential access key that an application uses to authenticate requests to an SMS gateway. SENDLY SMS API uses Bearer Token authentication. You do not need to use the same key across all your projects.

Within a single SENDLY account, you can generate an unlimited number of independent API tokens and assign them specifically to:

  • Different projects or applications – each integration has its own key.
  • Different clients – agencies and software development companies can use a separate token for each client without creating separate accounts.
  • Different environments – production, staging and testing environments run on independent keys.
  • Different departments – marketing, sales and customer support each send SMS through their own token while sharing a budget and centralized billing.

You can deactivate or regenerate any token at any time, or monitor its activity. Multiple tokens give you full control and operational separation without multiplying accounts and invoices.

This means replacing the key for one integration does not require distributing a new token to every other application. Never publish tokens in a repository, browser-side code or screenshots.

Example: two brands and several applications on one account

A hypothetical agency manages communications for two stores and its own CRM. It can organize each integration with a separate token while keeping one account and shared billing.

IntegrationAPI tokenSMS sender name
Store A – productionSeparate token for store AStoreA
Store A – stagingSeparate token for the testing environmentStoreA
Store B – productionSeparate token for store BStoreB
Agency CRMSeparate CRM tokenAgency

This is a fictional organizational example, not a description of an actual client. The table contains token labels, not real access keys. All sender names require approval. When an integration is retired, you deactivate its token while the other projects continue using their own keys.

SMS sender name, header and Sender ID – what do they mean?

SMS sender name, sender header and Sender ID are terms for the identifier displayed in a message’s sender field. Instead of a number, recipients can see a recognizable company, brand or project name, such as SENDLY, MyStore or Reception24.

This alphanumeric sender identifier builds recipients’ trust, increases brand recognition and makes communication more effective. SENDLY lets you assign multiple approved SMS sender names and numeric identifiers to one account.

ScenarioBenefit
Agency serving multiple clientsEach client has its own sender name – all messages are sent from one place.
Company with multiple brandsA separate Sender ID for each brand without separate accounts.
Notifications and marketingDifferent sender names for transactional and promotional SMS.
Regulations requiring a numberIdentification by number instead of an alphanumeric name.

For more on the identifier itself and the uses of company names, see our guide to SMS sender names.

How do you configure an SMS sender name and API token in the SENDLY dashboard?

You can manage tokens, sender names and gateway settings yourself in the customer dashboard, without contacting support. To add an SMS sender name:

  1. Sign in to your account in the SENDLY dashboard.
  2. Go to SMS Gateway in the main menu.
  3. Select Service list and click Add service.
  4. Enter your chosen alphanumeric name.
  5. Wait for verification and approval by telecommunications operators.
  6. Once approved, the name is available in the from field whenever you send an SMS through the API.

The from parameter in a SENDLY API request takes exactly the value previously approved in the dashboard. This ensures your messages meet operators’ requirements and recipients see a recognizable sender.

Generating and managing API tokens works in a similar way – the entire process takes just a few clicks in the same menu. If you are connecting an application for the first time, start with your first SMS through the API and the SMS API documentation.

2FA in the SENDLY dashboard – how do you protect account sign-in?

Two-factor authentication, or 2FA, adds a second verification factor to sign-in. An SMS gateway account gives access to message history, API keys and your budget, so a password should not be the only layer of protection.

SENDLY has introduced two-factor authentication in the dashboard. Once enabled, every sign-in requires a second verification factor in addition to the usual password. This keeps unauthorized users locked out even if sign-in credentials are leaked.

  1. Go to your account settings in the dashboard.
  2. Find Security and select Two-factor authentication.
  3. Set up your preferred verification method by following the instructions in the dashboard.
  4. Confirm activation – your account is now protected by two independent security layers.

2FA is built directly into the dashboard, with no need for external tools or contact with support. This is particularly important for agencies, software development companies and teams managing SMS communications.

Dashboard 2FA and OTP codes sent through the SMS API are two different uses. The former protects sign-in to your SENDLY account. The latter verifies actions taken by users of your application. API tokens also need their own protection – never disclose them to unauthorized people.

Pay-as-you-go – an SMS gateway with no subscription or fixed fees

Pay-as-you-go with SENDLY means you pay only for the SMS messages you send. Nothing more. You do not pay simply for having an account or for months when you send no messages.

With SENDLY, there are no:

  • Monthly subscription fees.
  • Account setup or maintenance fees.
  • Fees for additional identifiers or webhooks.
  • Minimum monthly spending requirements.
  • Fees for access to the API and documentation.
  • Packages that expire after a set period.
  • Hidden administrative costs.

If your application sends no messages in a given month, you pay nothing. Your account stays active, your configuration is preserved, and your tokens and sender names remain ready to use.

Who is it for?Pay-as-you-go benefit
Startup or small businessNo fixed costs while growing.
Developer or freelancerPay only during active projects.
Marketing agencyFlexible budget allocation across clients.
Seasonal e-commerce businessHigh-volume sending in season, zero costs out of season.
Large enterprisePrecise cost control per project or department.

Check the rates on the current SENDLY pricing page. If you are comparing billing models, also see how much it costs to send SMS in Poland.

100 free SMS to get started – what can you test?

Every new user receives 100 free SMS messages after signing up – no credit card details required and no commitments.

You can use them to:

  • Test the API integration in your project or application.
  • Verify sender names and see how they appear on different devices.
  • Evaluate deliverability and message delivery speed.
  • Explore the dashboard and all available features.
  • Test 2FA and token management.

Signing up takes a minute. Your SMS messages are available immediately. No paperwork, no risk.

Create a free SENDLY account and get your first 100 SMS.

SENDLY at a glance – tokens, senders, security and billing

FeatureSENDLYTypical SMS gateway
Multiple API tokens on one accountYesUsually not
Multiple SMS sender names / Sender IDsYesUsually not
Numeric sender identificationYesPartially supported
Dashboard 2FAYesRare
Pay-as-you-go modelYesOften subscription-based
Monthly account feeNoneUsually charged
Free starter package100 SMSRare

Multiple tokens and sender names under one account give you organizational flexibility without splitting up billing. You configure them in the SMS Gateway section, 2FA protects dashboard access, and pay-as-you-go lets you use the service without monthly fees.

If you need an SMS gateway for several projects or brands, create a SENDLY account and test the setup with 100 free messages.

FAQ

Can I have multiple SMS API tokens on one SENDLY account?+

Yes. Within one account, you can generate an unlimited number of independent API tokens for projects, clients, environments or departments. You can deactivate or regenerate any token and monitor its activity.

Does each application need its own account and budget?+

No. Individual integrations can use separate tokens while sharing one account, budget and centralized billing. You do not need separate accounts for each brand or project.

Can one account have several SMS sender names?+

Yes. SENDLY lets you assign multiple approved SMS sender names, or Sender IDs, and numeric identifiers to one account. This lets each brand or type of communication have its own sender.

How do I set an approved sender name in the API?+

Add a service in the dashboard under SMS Gateway → Service list → Add service, enter the name and wait for approval. The from parameter in an API request takes exactly the value previously approved in the dashboard.

How do I enable 2FA in the SENDLY dashboard?+

In your account settings, open Security → Two-factor authentication. Set up your preferred method following the dashboard instructions and confirm activation. Every sign-in will then require a second factor in addition to your password.

Is dashboard 2FA the same as sending OTP codes by SMS?+

No. Dashboard 2FA protects access to your SENDLY account. Sending OTP codes through the SMS API authenticates users of your application. These are two different uses, and API tokens also require separate protection.

Does SENDLY charge a subscription or fees for additional identifiers?+

No. Pay-as-you-go means you pay only for the SMS messages you send, with no subscription or fees for your account, API access, additional identifiers or webhooks. There are no minimum monthly spending requirements or packages that expire after a set period.

Do I need a credit card to get the first 100 SMS?+

No. Every new user receives 100 free SMS after signing up, with no credit card and no commitments. You can use them to test API integration, senders, deliverability, the dashboard, 2FA and token management.

Read next

Start sending SMS today.

100 free messages. No credit card. No subscription. Activation in 30 seconds.