Weave Code
Placid Php Laravel Package
placidapp/placid-php
Official PHP SDK for the Placid creative automation API. Generate images, videos, and PDFs from templates by merging dynamic data, then retrieve rendered assets through a simple client for Laravel or any PHP app.
✨ Automatic image creation from templates
Frequently asked questions about Placid Php
- Is placidapp/placid-php a Laravel package?
- No. It is a thin, framework-agnostic PHP SDK that wraps the Placid SaaS REST API, so there is no service provider, facade, config publishing, queue integration, or filesystem integration. In a Laravel app you instantiate it yourself and bind it into the container with your own service provider entry if you want dependency injection.
- How do I install placidapp/placid-php with Composer?
- Install it with composer require placidapp/placid-php, then put your Placid API token in .env and expose it through config/services.php rather than calling env() directly. Before committing, check the SDK's PHP and Guzzle version constraints in its composer.json against your Laravel version. Expect roughly one to two days for a spike and three to five days to productionise a first use case with jobs, storage, retries, and observability.
- Does placidapp/placid-php work with Laravel 10 and Laravel 11?
- It is not officially packaged for Laravel, so support depends entirely on whether its dependency constraints resolve on your target version. A 2022-era SDK may pin a narrow Guzzle constraint that conflicts with packages pushing Guzzle 7, which can block upgrades or force --ignore-platform-reqs workarounds. Run a Composer resolve check against Laravel 10 or 11 first, because this five-minute check can rule the package out entirely.
- How do I configure the Placid API token in a Laravel application?
- Add the token to .env, reference it from config/services.php, and bind the Placid client as a singleton in a service provider so it is resolved once per request. Keep the token out of source control and out of any front-end bundle. Then wrap the SDK inside an application-owned service class so controllers and jobs never touch the client directly.
- Should I use the SDK or Laravel's HTTP client directly for Placid?
- The SDK is a convenience layer of roughly the same size as a handful of Http::withToken() calls, so it buys you maybe a day of endpoint plumbing. Define your own contract such as ImageRenderer::render(TemplateRef $template, array $params): RenderedImage and implement it once with the SDK. That gives you a single seam to swap in raw HTTP calls later, a seam to add a second provider, and easy faking in tests.
- Can placidapp/placid-php generate videos and PDFs, or only images?
- The SDK is described as generating images, videos, and PDFs from Placid templates by merging dynamic data and then retrieving the rendered assets. However, the last release was 2022-07-20 and Placid's API has evolved since, so endpoint shapes and response formats may have changed. Verify each asset type you need against the current live API documentation before relying on it.
- Does the Placid SDK support asynchronous rendering and webhooks?
- The SDK metadata does not guarantee that its async path or webhook helpers match the current API version. Placid rendering may be synchronous or async/webhook-driven depending on the endpoint and your plan, so confirm this in the live docs. If you need webhooks, expect to implement signature verification and idempotency yourself inside your Laravel application.
- Can I run Placid image generation inside a Laravel queue job?
- Yes. The SDK is plain PHP, so you can call it from a queued job, but the SDK itself provides no retry, backoff, or HTTP instrumentation. Implement those concerns in your job and service layer, and store rendered assets in your own filesystem or S3 disk rather than depending solely on Placid's asset hosting. Also account for rate limits and metered per-image pricing in your job design and business case.
- How do I test code that uses placidapp/placid-php?
- Do not hit the live Placid API in tests. Because the SDK is not Laravel-aware, test against your own interface by binding a fake ImageRenderer implementation in the container and asserting the template reference and parameters your code passes. If you go the direct HTTP route instead, Laravel's Http::fake() covers the same ground with less setup.
- Is placidapp/placid-php actively maintained, and what are the risks?
- The last release was 2022-07-20, stars are around 10, the source repository is not clearly listed, and there is no visible CI or test signal, so treat it as a single-vendor artifact with a low bus factor. The top risk is staleness against the current Placid API, followed by dependency conflicts and the fact that rendering is a metered SaaS with rate limits and overage costs. Plan an adapter plus a direct-HTTP fallback as the likely medium-term state, and verify commit history, API version support, and DPA options if template parameters include customer PII.
Weaver
How can I help you explore Laravel packages today?