How to Send SMS from Laravel with the Grupo Tecnophone API

Send an SMS with Laravel

1. Configuration. Add the credentials to config/services.php and define GTP_SMS_TOKEN in your .env:

// config/services.php
'gtp_sms' => [
    'token'    => env('GTP_SMS_TOKEN'),
    'endpoint' => env('GTP_SMS_ENDPOINT', 'https://api.grupotecnophone.com/prod/v1/sms/send'),
],

2. Service. Centralize sending in a reusable class:

<?php

namespace App\Services;

use Illuminate\Support\Facades\Http;
use RuntimeException;

class SmsService
{
    public function send(string $to, string $body): array
    {
        $response = Http::withToken(config('services.gtp_sms.token'))
            ->withHeaders(['User-Agent' => 'MiEmpresa/1.0'])
            ->acceptJson()
            ->timeout(30)
            ->post(config('services.gtp_sms.endpoint'), [
                'to'   => $to,
                'body' => $body,
            ]);

        $data = $response->json() ?? [];

        if ($response->successful() && ($data['status'] ?? null) === 'success') {
            return $data; // sid, encoding, num_chars, num_segments
        }

        $code = $data['error']['code'] ?? 'HTTP_' . $response->status();

        throw new RuntimeException($code . ': ' . ($data['error']['message'] ?? $response->body()));
    }
}

3. Queued sending. To avoid blocking the web request —and to absorb sending peaks— dispatch a job:

<?php

namespace App\Jobs;

use App\Services\SmsService;
use Illuminate\Bus\Queueable;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Foundation\Bus\Dispatchable;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Queue\SerializesModels;
use Illuminate\Support\Facades\Log;

class SendSms implements ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;

    public int $tries = 1; // avoids duplicate resends on network errors

    public function __construct(public string $to, public string $body)
    {
    }

    public function handle(SmsService $sms): void
    {
        $result = $sms->send($this->to, $this->body);

        Log::info('SMS aceptado', ['sid' => $result['sid'], 'segmentos' => $result['num_segments']]);
    }
}

// Desde un controlador o un listener:
// SendSms::dispatch('+525512345678', 'Your verification code is 482913. It expires in 5 minutes.');

{
  "sid": "sms_20261012143201_39bdafbd",
  "status": "success",
  "to": "+525512345678",
  "body": "Your verification code is 482913. It expires in 5 minutes.",
  "encoding": "GSM7",
  "num_chars": 56,
  "num_segments": 1,
  "error": null
}

Common errors

HTTP	Code	Meaning
400	ENCRYPTION_REQUIRED	The connection requires to and body to be encrypted with RSA-OAEP
400	ENCRYPTION_NOT_ALLOWED	The connection operates in plain text and encrypted content was received
400	INPUT_PHONE_BLACKLISTED	The destination number is on the blacklist
400	INSUFFICIENT_BALANCE	Insufficient balance for the send
401	—	Missing or invalid token
403	—	The source IP is not authorized for the token
500	—	Unexpected internal error

On 400 errors the response includes an error object with code, code_num and message.

Best practices

• Set a timeout and log each response with its sid.
• After a network error with no response, do not resend blindly: check first so you don’t duplicate the message to the user.
• Retry only 500 errors, with progressive backoff and a maximum number of attempts.
• Queue bulk sends instead of sending them within a web request cycle.
• If the content is sensitive, enable connection encryption; the API documentation includes an RSA encryption example in PHP without external libraries.

See also the SMS API for Mexico, the SMPP connection and the guides for PHP, Python, Node.js and Java. If you need test credentials, contact us.