How to Send WhatsApp Messages from Laravel Without Twilio

·8 min read
How to Send WhatsApp Messages from Laravel Without Twilio

You are running a Laravel application in Karachi or Mumbai. Your checkout page is ready, your database is configured, and your users expect an instant WhatsApp notification when their order is confirmed or when they request a one-time password (OTP).

Naturally, you look at Twilio. Then you see the pricing.

Twilio charges a hefty markup on top of Meta's standard WhatsApp fees. In addition to that, setting up billing on Twilio using a Pakistani or Indian debit card often ends in a blocked transaction because of local state bank regulations on international SaaS subscriptions. You do not need an expensive US-based middleman to send a message to a phone number that is physically located down the street from you.

You can connect your Laravel application directly to Meta's official WhatsApp Business Cloud API. It is cheaper, faster, and gives you direct control over your templates. Here is exactly how to do it, what to avoid, and the actual code you need to deploy.

The Three Ways to Send WhatsApp Messages (And the Truth About Them)

Before writing any PHP code, you must choose your path. There are three ways to send WhatsApp messages from a backend application. Two of them are viable; one is a disaster waiting to happen.

1. Meta's Direct Cloud API (The Best Option)

Meta allows you to connect directly to their servers. You pay Meta directly for the messages you send, with no extra per-message markup. The first 1,000 service conversations every month are completely free. If you exceed that, you pay Meta's regional rates, which are significantly lower than Twilio's bundled pricing.

The downside? Meta's developer interface is messy. Finding your API keys, setting up permanent system tokens, and getting templates approved requires clicking through a dozen confusing dashboards.

2. Unofficial Web Scraping / Puppeteer APIs (The Dangerous Option)

You will find packages on GitHub that use Node.js, Puppeteer, or libraries like Baileys to control a web version of WhatsApp. They promise "free unlimited messages" because you are just automating a personal phone number.

Do not use these for business. WhatsApp actively scans for automated web sessions. Your number will be banned. It is not a matter of if, but when. Usually, it happens on a Friday evening when your support team has gone home, leaving your customers with zero notifications.

3. Local Wrappers and Gateways

If you want to avoid the headache of navigating Meta's developer console but still want official, reliable delivery, you can use a dedicated WhatsApp API wrapper. This is where we at WA Link fit in. We provide a simplified API and a team inbox interface that sits on top of the official Meta API. It gets you up and running in minutes without dealing with Meta's developer portal, though you still have to comply with Meta's official template guidelines.

Setting Up Your Meta Developer Account

To go direct without Twilio, you need a Meta Developer account. Here is the exact sequence to get your credentials.

  1. Go to the Meta Developers Portal and log in with your Facebook account.
  2. Create a new App. Select "Other" as the use case, and choose "Business" as the app type.
  3. Scroll down to the WhatsApp section and click "Set Up".
  4. Link your Meta Business Portfolio (formerly Business Manager). If you do not have one, Meta will guide you to create it during this step.

At this point, Meta will assign you a temporary access token and a test phone number. This test number can only send messages to verified developer phone numbers. To go live, you must add your own phone number and a payment method to your Meta Business Tool.

Generating a Permanent Access Token

The temporary token Meta gives you expires in 24 hours. Your Laravel app will stop working tomorrow if you use it. You must generate a System User Token:

  1. Go to your Meta Business Suite settings.
  2. Navigate to Users > System Users.
  3. Add a new System User and set the role to "Admin".
  4. Click "Generate New Token", select your WhatsApp app, and check the boxes for whatsapp_business_messaging and whatsapp_business_management.
  5. Copy this token immediately. Meta will never show it to you again. Store it safely in your Laravel .env file.

Integrating WhatsApp into Laravel

You do not need a heavy third-party Laravel package to send these messages. Standard packages often go abandoned when Meta updates its API version. Laravel's built-in Http client is all you need to make clean, secure requests to Meta's endpoints.

1. Update Your Environment File

Add your credentials to your .env file. Replace the placeholders with your actual Meta Phone Number ID, your Business Account ID, and the permanent System User Token you generated.

WHATSAPP_TOKEN=your_permanent_system_user_token_here
WHATSAPP_PHONE_NUMBER_ID=your_phone_number_id_here
WHATSAPP_API_VERSION=v20.0

2. Create a Dedicated WhatsApp Service Class

Run the Artisan command to create a service class where we will handle the API logic:

php artisan make:class Services/WhatsAppService

Open the newly created file and write the following code. This service uses Laravel's HTTP client to send a template message, which is required by Meta for any business-initiated conversation.

<?php

namespace App\Services;

use Illuminate\Support\Facades\Http;
use Illuminate\Support\Facades\Log;

class WhatsAppService
{
    protected string $token;
    protected string $phoneNumberId;
    protected string $version;

    public function __construct()
    {
        $this->token = config('services.whatsapp.token');
        $this->phoneNumberId = config('services.whatsapp.phone_number_id');
        $this->version = config('services.whatsapp.version', 'v20.0');
    }

    public function sendTemplate(string $to, string $templateName, string $languageCode = 'en_US', array $parameters = []): bool
    {
        $url = "https://graph.facebook.com/{$this->version}/{$this->phoneNumberId}/messages";

        // Format parameters for Meta's payload structure
        $formattedParameters = array_map(function ($value) {
            return [
                'type' => 'text',
                'text' => $value
            ];
        }, $parameters);

        $payload = [
            'messaging_product' => 'whatsapp',
            'to' => $to,
            'type' => 'template',
            'template' => [
                'name' => $templateName,
                'language' => [
                    'code' => $languageCode
                ],
                'components' => [
                    [
                        'type' => 'body',
                        'parameters' => $formattedParameters
                    ]
                ]
            ]
        ];

        $response = Http::withToken($this->token)
            ->post($url, $payload);

        if ($response->successful()) {
            return true;
        }

        Log::error('WhatsApp API delivery failed', [
            'status' => $response->status(),
            'body' => $response->json(),
            'payload' => $payload
        ]);

        return false;
    }
}

3. Map Configuration in services.php

Open config/services.php and add the WhatsApp configuration array so your service can read the environment variables:

'whatsapp' => [
    'token' => env('WHATSAPP_TOKEN'),
    'phone_number_id' => env('WHATSAPP_PHONE_NUMBER_ID'),
    'version' => env('WHATSAPP_API_VERSION', 'v20.0'),
],

Sending Your First Message

Meta requires you to get templates pre-approved before you can send them. You cannot send raw, free-form text messages to a customer unless they have messaged you first within the last 24 hours.

For your initial test, use Meta's default template called hello_world. It requires no variables.

Here is how you can trigger this from a route or controller in your Laravel application:

use App\Services\WhatsAppService;
use Illuminate\Support\Facades\Route;

Route::get('/test-whatsapp', function (WhatsAppService $whatsapp) {
    // Recipient number must include the country code without '+' or leading zeros.
    // Example: 923001234567 for Pakistan or 919876543210 for India.
    $recipient = '923001234567'; 

    $sent = $whatsapp->sendTemplate($recipient, 'hello_world', 'en_US');

    if ($sent) {
        return 'Message sent successfully!';
    }

    return 'Message delivery failed. Check your laravel.log file.';
});

Handling Custom Templates with Variables

In a real application, you will want to send custom messages like: "Hi Ahmed, your order #1084 has been shipped."

First, go to your WhatsApp Manager inside the Meta Business Suite, navigate to Message Templates, and create a template named order_shipped. Set the body text to: Hi {{1}}, your order {{2}} has been shipped.

Once Meta approves it (which usually takes between two minutes and an hour), you can send it from Laravel by passing the dynamic variables in your array:

$whatsapp->sendTemplate(
    '923001234567', 
    'order_shipped', 
    'en_US', 
    ['Ahmed', '#1084']
);

Mistakes to Avoid When Going Direct

Skipping Twilio saves you money, but it also removes a safety net. You must handle certain edge cases yourself.

The 24-Hour Session Rule

If a customer replies to your automated notification, a "customer service window" opens. For the next 24 hours, you can send them free-form text messages instead of pre-approved templates. If you try to send a plain text message outside this 24-hour window, Meta's API will reject it with a 131047 error code.

Failing Webhooks and Status Updates

When you send a message, Meta's API returns a 200 OK response with a message ID. This only means Meta accepted your request; it does not mean the user received the message.

To know if a message was actually delivered or read, you must set up a Webhook route in Laravel. This route must accept POST requests from Meta and parse the status array. Without this, you are flying blind, unable to verify if your OTPs are actually reaching your users' phones.

Card Authorization Issues

Meta charges your registered card at the end of the month or when you hit a specific billing threshold. If you are in Pakistan or India, ensure your bank allows international online transactions without requiring a one-time SMS verification password for automated charges. If Meta's payment fails twice, they will immediately suspend your WhatsApp API access, disabling all transactional notifications across your Laravel platform.

Frequently Asked Questions

Do I need a physical SIM card to use Meta's Cloud API?

You need a clean phone number that is not currently associated with an active personal or business WhatsApp app on a physical phone. You can use a virtual number, a landline, or a new SIM card. If the number is already registered on a phone app, you must delete that account before registering it with the Cloud API.

Is the WhatsApp Business API completely free?

No. Meta gives you 1,000 free service conversations per month. After that, they charge per conversation, not per individual message. A conversation is a 24-hour window. The cost of a conversation varies depending on the category (Utility, Authentication, Marketing) and the recipient's country code. Check Meta's official pricing sheets for current rates in your region.

Why did my API call return error code 131026?

This is a common error indicating that the recipient's phone number is not registered on WhatsApp, or they have blocked your business profile. It can also occur if you are using a test account and have not added the recipient's number to your verified developer test list.

Can I send PDFs, images, and audio files without Twilio?

Yes. You can send media by uploading the files to Meta's servers first using their media endpoint, or by hosting the file on your public Laravel storage disk and passing the direct URL in your template parameters. The Cloud API fully supports media templates.

Share:WhatsAppFacebookXLinkedIn

Read the API documentation