how to get all templates

[vivekrsq]

there is no method to get all approved templates.

[aindot]

You need the business ID to be able to fetch the templates, this is a snippet that I have been using

<?php

namespace App\Jobs;

use App\Models\WhatsAppTemplate;
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\Arr;
use Illuminate\Support\Str;
use JoelButcher\Facebook\Facebook;
use Netflie\WhatsAppCloudApi\WhatsAppCloudApi;


        $facebook = new Facebook([
            'app_id' => config('app.app_id'),
            'app_secret' => config('app.app_secret'),
            'default_graph_version' => config('app.graph_version'),
            'default_access_token' => config('app.w_token'),
        ]);


        $w_buss_id = config('app.w_buss_id');
        $fields = [
            'id',
            'name',
            'status',
            'language',
            'category',
            'rejected_reason',
            'quality_score',
            'components',
            'health_status',
        ];
        $fields = implode(',', $fields);

        $feed = $facebook->get("$w_buss_id/message_templates?fields=$fields&limit=10");

        $feed = $feed->getGraphEdge();

[gumroler]

Not the prettiest solution, but I've got this done by extending WhatsAppCloudApi and making my own TemplateRequest class.
The issue I ran into though, and what makes this messy: Client class is pretty restrictive and does not have any generic request method, it's super specific. I've had to extent Client class too, override WhatsAppCloudApi constructor to use my override class, and then re-declare buildRequestUri() and buildBaseUri() methods on client class because they are private methods.

Anyway, I'm now able to add any number of my own Requests and handle the responses.
I think with a slight refactor of the Client class, it could be a bit easier to extend WhatsAppCloudApi without having to extend Client too. Just my 2c

[aalbarca]

Hi, The classes are quite restrictive (final classes and private methods) by design — it’s all about maintainability. If I made the classes and methods protected, then anyone could extend them. And once people start extending classes and changing their behavior, any future update I release would have a high chance of breaking those modifications. Best regards, Alex. El vie, 7 nov 2025 a las 9:18, Guy M ***@***.***>) escribió:

…

*gumroler* left a comment (netflie/whatsapp-cloud-api#223) <#223 (comment)> Not the prettiest solution, but I've got this done by extending WhatsAppCloudApi and making my own TemplateRequest class. The issue I ran into though, and what makes this messy: Client class is pretty restrictive and does not have any generic request method, it's super specific. I've had to extent Client class too, override WhatsAppCloudApi constructor to use my override class, and then re-declare buildRequestUri() and buildBaseUri() methods on client class because they are private methods. Anyway, I'm now able to add any number of my own Requests and handle the responses. I think with a slight refactor of the Client class, it could be a bit easier to extend WhatsAppCloudApi without having to extend Client too. Just my 2c — Reply to this email directly, view it on GitHub <#223 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKYKKPNOFXUI4PNWPANSID33RIVXAVCNFSM6AAAAABXBPWTV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMBRGIZDSNRZGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>