The biggest issue with working with third-party APIs is that we have very little visibility. We integrate them into our code base and test them - but we have no idea how often we use them unless the API we are integrating with has metrics we can use.

I will show you a rough outline of the base requirements below: class YourWatcher extends Watcher { public function register($app): void { // handle code for watcher here. }}

Let’s look at the buildClient method: private function buildClient(Application $app): Closure { return static function (Application $app): Client { $config = $app['config']['guzzle']??

So if you start seeing failures from API integrations, this will help you massively with your debugging.
Newsletter

Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week

Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge. Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge.
Fathom Analytics | Fast, simple and privacy-focused website analytics. Fathom Analytics | Fast, simple and privacy-focused website analytics.
Shirts painstakingly handcrafted by under-caffeinated developers. Shirts painstakingly handcrafted by under-caffeinated developers.
Community Partners