- How do I install alchemyguy/youtube-laravel-api in a Laravel application?
- Install it with composer require alchemyguy/youtube-laravel-api, then publish the package config using php artisan vendor:publish. After publishing, add your YouTube Data API credentials and OAuth details to the config or environment. Integration is a standard Laravel service provider and facade setup, so no bespoke wiring is required.
- What PHP and Laravel versions are required by youtube-laravel-api v2?
- Version 2.0.0 explicitly targets PHP 8.3 or newer and Laravel 11 or newer. That is a hard floor, so services on PHP 8.1/8.2 or Laravel 9/10 cannot consume v2.0.0. If your application has not met that baseline yet, treat the upgrade as a prerequisite project rather than a quick composer update.
- How do I configure YouTube API credentials and OAuth for this Laravel package?
- The package follows Laravel conventions with a publishable config file, so you provision YouTube Data API v3 credentials and place them in your config or environment. OAuth access and refresh tokens are part of the integration, and you should confirm whether the package owns token refresh or delegates it to your app. Keep credentials out of version control and scope them to the minimum YouTube permissions your feature needs.
- Can I upload videos to YouTube from a Laravel app with this package?
- Yes, the package advertises video uploads as part of its wrapper around the YouTube Data API v3. Uploads require OAuth credentials with the appropriate scope, so plan authorization and token storage before you build the upload flow. Also account for YouTube API quota, since write operations consume quota units and can fail when the daily limit is exhausted.
- Does alchemyguy/youtube-laravel-api support live streaming and liveBroadcasts?
- The package description lists live streaming alongside channels, OAuth, and video uploads, so it is intended to cover YouTube live streaming resources. You will still need valid OAuth credentials and the correct YouTube API scopes for live operations. Verify the specific liveBroadcast and liveStream methods you need against the package source before committing to it.
- How does YouTube Data API quota affect production use of this package?
- The YouTube Data API v3 default quota is 10,000 units per day, and a single search.list call costs 100 units. No Laravel package version changes that, so quota exhaustion is the most likely production failure and it is an operational problem. Cache responses where possible, monitor quota usage, and request additional quota from Google if your workload needs it.
- Can I mock the YouTube API HTTP client for testing in Laravel?
- The release notes do not disclose whether the package supports injecting a mockable HTTP client or hard-binds Guzzle, so this is an open verification item. Before relying on it in a test suite, inspect the service bindings and see whether the client is resolved from Laravel's container. If the client is injectable, you can swap in a fake or use Laravel's HTTP client fakes; if not, you may need integration tests against a sandbox or a wrapper of your own.
- What breaking changes are in youtube-laravel-api v2.0.0 compared with v1.0.3?
- Version 2.0.0 is a major release that combines a platform modernization with a full bug-fix sweep, but the release notes do not enumerate a complete breaking-change list. Treat framework-floor changes and behavior fixes as potential breaking changes for response shaping, pagination defaults, null handling, and exception types. Inventory facade calls, injected interfaces, config keys, and response assertions before upgrading.
- Is alchemyguy/youtube-laravel-api actively maintained and safe for production critical paths?
- The package is published from a single personal account, so bus factor and long-term maintenance confidence are legitimate concerns. It is composer-installable and fits Laravel idioms well, but no CI matrix, test coverage, or static-analysis signal is disclosed in the release notes. For critical paths, review the repository activity, pin versions, and have a fallback plan such as calling the YouTube API directly.
- How should I store and refresh OAuth tokens when using this package?
- The package requires OAuth credentials, but the notes do not state whether it owns token refresh or delegates that responsibility to the host Laravel app. Store refresh tokens securely, for example encrypted in your database or secrets manager, and rotate them according to your security policy. Confirm the refresh behavior in the source or documentation before building long-running background jobs that call YouTube.