How to implement GraphQL in a Laravel application?
Jul 27, 2025 am 01:27 AMInstall Lighthouse via Composer using composer require nuwave/lighthouse. 2. Publish configuration and schema files with php artisan vendor:publish --provider="Nuwave\Lighthouse\LighthouseServiceProvider". 3. Define your GraphQL schema in graphql/schema.graphql using types, queries, and mutations with Lighthouse directives like @all and @find. 4. Set up the Post model and migration using php artisan make:model Post -m, run migration, and ensure fillable attributes are set. 5. Test the GraphQL endpoint at /graphql by sending queries or using the built-in IDE in development. 6. Customize logic with resolvers by updating the schema to use @field(resolver: "Post@posts") and creating a resolver class in app/GraphQL/Queries/Post.php. 7. Add authentication and authorization using directives like @guard and @can on queries and mutations. 8. Apply input validation with the @rules directive to enforce constraints like required or min:3. 9. Optimize performance by leveraging Lighthouse’s built-in DataLoader to resolve relationships such as @hasMany and avoid N 1 queries. 10. Secure the API in production by disabling the GraphQL IDE, adding rate limiting, enabling persisted queries, and configuring caching as needed. Using Lighthouse allows seamless integration of a full-featured, secure, and efficient GraphQL API into Laravel using schema-first design and native Eloquent integration.
Implementing GraphQL in a Laravel application can greatly enhance how your frontend consumes data, especially when you want flexible, efficient queries. While Laravel doesn’t include GraphQL support out of the box (unlike REST), you can integrate it smoothly using packages. The most popular and well-maintained package for this is Lighthouse by Nuwave.

Here’s a step-by-step guide to get GraphQL working in your Laravel app.
? 1. Install Lighthouse via Composer
Start by installing the Lighthouse package:

composer require nuwave/lighthouse
Lighthouse is a powerful GraphQL server implementation for Laravel that uses schema-first design and leverages Laravel’s features.
? 2. Publish Configuration and Schema
Run the vendor publish command to get the config and default schema:

php artisan vendor:publish --provider="Nuwave\Lighthouse\LighthouseServiceProvider"
This creates:
config/lighthouse.php
– configuration fileroutes/graphql.php
– GraphQL routeapp/GraphQL
directory (if not present)graphql/schema.graphql
– your main schema file
? 3. Define Your GraphQL Schema
Open graphql/schema.graphql
. This is where you define types, queries, mutations, etc.
For example, let’s assume you have a Post
model. Define a basic schema:
type Post { id: ID! title: String! content: String created_at: DateTime! } type Query { posts: [Post!]! @all post(id: ID! @eq): Post @find } type Mutation { createPost(title: String!, content: String!): Post @create updatePost(id: ID!, title: String, content: String): Post @update deletePost(id: ID!): Post @delete }
? Note: Directives like
@all
,@find
,@create
,@update
,@delete
are built-in Lighthouse directives that map to Eloquent operations.
? 4. Set Up the Model and Migration (if needed)
Make sure your Post
model exists and the database table is set up:
php artisan make:model Post -m
Update the migration and run:
php artisan migrate
Ensure your model is set up correctly:
// app/Models/Post.php namespace App\Models; use Illuminate\Database\Eloquent\Model; class Post extends Model { protected $fillable = ['title', 'content']; }
?? Don’t forget to update
config/lighthouse.php
if you're using custom model namespaces.
? 5. Test the GraphQL Endpoint
Lighthouse sets up a route at /graphql
by default (defined in routes/graphql.php
).
You can now send POST requests to /graphql
with queries like:
query { posts { id title content created_at } }
Or use the built-in GraphQL IDE (if enabled):
- Visit:
http://your-app.test/graphql
(only in local/dev by default) - This opens GraphiQL or Altair, where you can test queries.
? In production, make sure to disable the GraphQL IDE for security.
? 6. Customize with Resolvers (Optional)
If you need custom logic (e.g., filtering, permissions, complex data), create a resolver.
For example, customize the posts
query:
Update schema:
type Query { posts(search: String): [Post!]! @field(resolver: "Post@posts") }
Create a resolver class:
// app/GraphQL/Queries/Post.php namespace App\GraphQL\Queries; class Post { public function posts($_, array $args) { $query = \App\Models\Post::query(); if (isset($args['search'])) { $query->where('title', 'LIKE', '%' . $args['search'] . '%'); } return $query->get(); } }
? 7. Authentication & Authorization
To protect queries/mutations, use Lighthouse directives like @guard
or @can
.
Example:
type Mutation { createPost(title: String!, content: String!): Post @create @guard }
This ensures the user is authenticated.
For policies:
deletePost(id: ID!): Post @delete @can(ability: "delete", model: "App\\Models\\Post")
? 8. Validation
Use the @rules
directive to validate inputs:
createPost( title: String! @rules(apply: ["required", "min:3"]) content: String @rules(apply: ["max:1000"]) ): Post @create
? 9. Optimize with DataLoader (Avoid N 1)
Lighthouse supports DataLoader out of the box for resolving relationships efficiently.
For example, if a Post
has many Comments
, define the relationship in Eloquent, then use @hasMany
in the schema:
type Post { id: ID! title: String! comments: [Comment!]! @hasMany }
Lighthouse will automatically batch-load comments.
? 10. Deploy & Secure
Before going live:
- Disable GraphQL IDE in production (
lighthouse.php
→'route' => ['middleware' => ['your-middleware']]
) - Add rate limiting
- Use persisted queries in production (optional)
- Enable caching if needed
Summary
Using Lighthouse is the cleanest way to add GraphQL to Laravel. It lets you:
- Define schema in
.graphql
files - Use Eloquent directly via directives
- Extend with custom resolvers
- Secure with Laravel’s auth system
With this setup, you get a full-featured GraphQL API that feels native to Laravel.
Basically, just install Lighthouse, define your schema, and go.
The above is the detailed content of How to implement GraphQL in a Laravel application?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

When choosing a suitable PHP framework, you need to consider comprehensively according to project needs: Laravel is suitable for rapid development and provides EloquentORM and Blade template engines, which are convenient for database operation and dynamic form rendering; Symfony is more flexible and suitable for complex systems; CodeIgniter is lightweight and suitable for simple applications with high performance requirements. 2. To ensure the accuracy of AI models, we need to start with high-quality data training, reasonable selection of evaluation indicators (such as accuracy, recall, F1 value), regular performance evaluation and model tuning, and ensure code quality through unit testing and integration testing, while continuously monitoring the input data to prevent data drift. 3. Many measures are required to protect user privacy: encrypt and store sensitive data (such as AES

There are three main ways to set environment variables in PHP: 1. Global configuration through php.ini; 2. Passed through a web server (such as SetEnv of Apache or fastcgi_param of Nginx); 3. Use putenv() function in PHP scripts. Among them, php.ini is suitable for global and infrequently changing configurations, web server configuration is suitable for scenarios that need to be isolated, and putenv() is suitable for temporary variables. Persistence policies include configuration files (such as php.ini or web server configuration), .env files are loaded with dotenv library, and dynamic injection of variables in CI/CD processes. Security management sensitive information should be avoided hard-coded, and it is recommended to use.en

To enable PHP containers to support automatic construction, the core lies in configuring the continuous integration (CI) process. 1. Use Dockerfile to define the PHP environment, including basic image, extension installation, dependency management and permission settings; 2. Configure CI/CD tools such as GitLabCI, and define the build, test and deployment stages through the .gitlab-ci.yml file to achieve automatic construction, testing and deployment; 3. Integrate test frameworks such as PHPUnit to ensure that tests are automatically run after code changes; 4. Use automated deployment strategies such as Kubernetes to define deployment configuration through the deployment.yaml file; 5. Optimize Dockerfile and adopt multi-stage construction

To build a PHP content payment platform, it is necessary to build a user management, content management, payment and permission control system. First, establish a user authentication system and use JWT to achieve lightweight authentication; second, design the backend management interface and database fields to manage paid content; third, integrate Alipay or WeChat payment and ensure process security; fourth, control user access rights through session or cookies. Choosing the Laravel framework can improve development efficiency, use watermarks and user management to prevent content theft, optimize performance requires coordinated improvement of code, database, cache and server configuration, and clear policies must be formulated and malicious behaviors must be prevented.

Laravel's EloquentScopes is a tool that encapsulates common query logic, divided into local scope and global scope. 1. The local scope is defined with a method starting with scope and needs to be called explicitly, such as Post::published(); 2. The global scope is automatically applied to all queries, often used for soft deletion or multi-tenant systems, and the Scope interface needs to be implemented and registered in the model; 3. The scope can be equipped with parameters, such as filtering articles by year or month, and corresponding parameters are passed in when calling; 4. Pay attention to naming specifications, chain calls, temporary disabling and combination expansion when using to improve code clarity and reusability.

The core idea of PHP combining AI for video content analysis is to let PHP serve as the backend "glue", first upload video to cloud storage, and then call AI services (such as Google CloudVideoAI, etc.) for asynchronous analysis; 2. PHP parses the JSON results, extract people, objects, scenes, voice and other information to generate intelligent tags and store them in the database; 3. The advantage is to use PHP's mature web ecosystem to quickly integrate AI capabilities, which is suitable for projects with existing PHP systems to efficiently implement; 4. Common challenges include large file processing (directly transmitted to cloud storage with pre-signed URLs), asynchronous tasks (introducing message queues), cost control (on-demand analysis, budget monitoring) and result optimization (label standardization); 5. Smart tags significantly improve visual

User permission management is the core mechanism for realizing product monetization in PHP development. It separates users, roles and permissions through a role-based access control (RBAC) model to achieve flexible permission allocation and management. The specific steps include: 1. Design three tables of users, roles, and permissions and two intermediate tables of user_roles and role_permissions; 2. Implement permission checking methods in the code such as $user->can('edit_post'); 3. Use cache to improve performance; 4. Use permission control to realize product function layering and differentiated services, thereby supporting membership system and pricing strategies; 5. Avoid the permission granularity is too coarse or too fine, and use "investment"

Laravel's configuration cache improves performance by merging all configuration files into a single cache file. Enabling configuration cache in a production environment can reduce I/O operations and file parsing on each request, thereby speeding up configuration loading; 1. It should be enabled when the application is deployed, the configuration is stable and no frequent changes are required; 2. After enabling, modify the configuration, you need to re-run phpartisanconfig:cache to take effect; 3. Avoid using dynamic logic or closures that depend on runtime conditions in the configuration file; 4. When troubleshooting problems, you should first clear the cache, check the .env variables and re-cache.
