Weave Code
Laravel Envato Laravel Package
infyomlabs/laravel-envato
Laravel wrapper for the Envato API that lets you query marketplace items, users, and sales from your app. It packages authentication, configuration, and a clean client interface so you can integrate Envato data without writing raw HTTP calls yourself.
Envato API Wrapper for Laravel
Frequently asked questions about Laravel Envato
- What is infyomlabs/laravel-envato used for?
- It is a Laravel wrapper around the Envato API that lets you query marketplace data such as users, items, sales, and earnings from your application. It provides a service provider, facade, publishable config, and fluent client methods so you do not have to write raw HTTP calls. Typical uses are dashboards, author statistics, and small marketplace integrations.
- How do I install infyomlabs/laravel-envato in a Laravel app?
- Install it with Composer using infyomlabs/laravel-envato:^2.0, then publish the package config file and add your Envato personal API token to your environment. The service provider and facade integrate with Laravel's container, so you can resolve the client or use the facade directly. The main onboarding step is generating an Envato API token with the right scopes.
- How do I configure the Envato API token for laravel-envato?
- Configuration is handled through the package config file, where you store your Envato personal token. In practice you publish the config and reference an environment variable so the token is not committed to source control. You also need an Envato account with a generated API token and awareness of its scopes and rate limits.
- Which Laravel versions does laravel-envato support?
- Version 2.0.0 drops Laravel 6, 7, and 8, so the target environment should be Laravel 9 or 10 on a currently supported PHP version. Laravel 11 support is not stated, which makes the package one major Laravel release behind the current line. If a service is still on Laravel 6, 7, or 8, this package is out of scope for that service until the framework is upgraded.
- How do I fetch Envato item or user data using the facade?
- Resolve the package client from Laravel's service container or use the provided facade, then call its fluent methods for users, items, and sales. The package exposes Envato marketplace endpoints through a clean client interface rather than requiring raw HTTP calls. Keep call sites small, such as an admin tool that resolves item metadata or a checkout flow that checks marketplace data.
- Does laravel-envato support Envato purchase code verification?
- The package gives you access to Envato marketplace data such as users, items, and sales, which can support license or purchase-related checks. It is a thin client wrapper, not a system of record, so you should keep your own verification logic and persistence in your application. Do not treat the package as the authority for entitlements or long-term license state.
- What are the Envato API rate limits and how does laravel-envato handle them?
- The package does not add a caching or rate-limit layer in front of the upstream Envato API, so Envato's own limits and token policies apply directly. For high-throughput catalog sync or dashboards with heavy traffic, put a caching layer in front of your calls rather than calling the API on every request. Token rotation and expected call volume should be planned as operational concerns.
- How do I test laravel-envato without hitting the real Envato API?
- Because the package is a thin wrapper, the practical approach is to bind a fake client in Laravel's container or fake the underlying HTTP layer in your test suite. No dedicated testing utilities are documented, so keep your own integration tests around the call sites that use the facade. This also helps isolate your application from upstream Envato API changes.
- What changed in laravel-envato v2.0.0 and how do I upgrade from 1.x?
- The visible change is that v2.0.0 drops Laravel 6, 7, and 8, and the release notes are sparse, listing framework support changes only. A major bump on a thin package usually implies namespace, config key, facade alias, method signature, or exception type changes, so read the actual diff between v1.3.9 and v2.0.0 before upgrading. Budget roughly one engineer-day to inventory consumers and review the changes.
- Are there alternatives to infyomlabs/laravel-envato for Envato API integration?
- You can call the Envato API directly with Laravel's HTTP client and wrap it in your own small anti-corruption layer, which gives you full control over caching, retries, and token handling. Other community wrappers may exist, but evaluate their Laravel version support and maintenance cadence the same way. For a thin integration, a first-party client plus your own facade is often a reasonable alternative.
Weaver
How can I help you explore Laravel packages today?