- How do I install rickwest/laravel-wordpress-api in a Laravel app?
- Install it with Composer, optionally publish the package config, and set a WORDPRESS_API_URL environment entry for your WordPress origin. Then smoke-test a read against /wp-json/wp/v2/posts before wiring it into application code. Check the package composer.json for Laravel and PHP constraints first.
- Which Laravel and PHP versions does this package support?
- The evaluation does not verify a Laravel or PHP support matrix, so inspect composer.json for declared constraints and any CI matrix. The review flags version drift as a real risk, especially around annual Laravel majors and Guzzle major bumps. Treat those upgrades as likely break points and test them explicitly.
- Can I use this package with a headless WordPress setup?
- Yes, it fits the headless WordPress pattern where Laravel handles routing and rendering while WordPress remains the content store. The client maps REST API v2 resources such as posts, pages, categories, tags, media, and users into Laravel-friendly calls. The main feasibility check is whether your WordPress origin actually exposes those endpoints to the caller you intend.
- Does the package support pagination and filtering?
- The package description lists filtering and pagination, but the evaluation warns that pagination metadata such as X-WP-Total and X-WP-TotalPages is often thin in packages this size. Verify that query parameters pass through verbatim for page, per_page, search, _embed, and _fields. If not, build your own helpers around the client.
- Can I retrieve custom post types and ACF fields with it?
- Custom post types are in scope, but ACF fields and rest_prepare_* filters change the JSON shape per WordPress site. The client cannot insulate you from that schema instability. Keep your own mapping layer and test against the actual origin payloads.
- Does it support authenticated requests for draft or private content?
- Authentication is listed in the package description, but the evaluation flags it as something to verify: authenticated reads for draft or private content versus public endpoints only. Test with the auth mechanism your WordPress origin uses. The read-only design is still a virtue because it avoids write tokens and credential sprawl.
- How are WordPress REST API errors surfaced by this client?
- The evaluation does not confirm the error model, so inspect how WordPress code, message, and data.status envelopes are surfaced. It could be typed exceptions, a response object, or raw arrays. Also plan for origin-side 401, 403, or HTML error bodies that are not clean client exceptions.
- Is rickwest/laravel-wordpress-api actively maintained?
- Maintenance signals are weak: 37 stars and a composite score of 17.27, with an assumed single maintainer and no formal deprecation policy. The 2026-08-08 last-release stamp should be treated as unverified until you confirm it against tags and commit history. Plan to adopt, then potentially fork if needed.
- Does it cache WordPress API responses or handle retries?
- The evaluation warns that caching and retry/backoff are typically thin or absent in packages this size, so treat caching as your application's responsibility. Check whether the HTTP transport lets you inject middleware for logging and retries. If not, wrap calls in your own cached repository or service.
- How does this compare to alternatives for consuming WordPress in Laravel?
- The evaluation frames this as a convenience wrapper rather than an abstraction framework, so compare it with using Laravel's HTTP client directly or another WordPress API client. Check endpoint coverage, auth, error handling, pagination, and maintenance before choosing. Whatever you pick, keep it behind an owned interface such as ContentRepository so alternatives stay swappable.