<?php namespace Drupal\mymodule\Plugin\rest\resource; use Drupal\rest\Plugin\ResourceBase; use Drupal\rest\ResourceResponse; use Symfony\Component\HttpKernel\Exception\BadRequestHttpException; /** * @RestResource( * id = "product_stock", * label = @Translation("Product Stock"), * uri_paths = { * "canonical" = "/api/products/{sku}/stock", * "create" = "/api/products/stock/update" * } * ) */ class ProductStockResource extends ResourceBase { public function get(string $sku): ResourceResponse { $node = $this->getProductBySku($sku); if (!$node) { throw new NotFoundHttpException("Product $sku not found"); } $response = new ResourceResponse([ 'sku' => $sku, 'stock' => (int) $node->get('field_stock_quantity')->value, 'available' => (bool) $node->get('field_in_stock')->value, ]); $response->addCacheableDependency($node); return $response; } public function patch(array $data): ResourceResponse { $sku = $data['sku'] ?? throw new BadRequestHttpException('SKU required'); $node = $this->getProductBySku($sku); $node->set('field_stock_quantity', $data['quantity']); $node->save(); return new ResourceResponse(['updated' => true], 200); } } 

Enable the resource in the admin: Configuration → Web Services → REST.

How to Optimize API Performance

Main Drupal API performance issues: N+1 queries, lack of caching, inefficient field selection. Use the following techniques:

• Including relationships (include) to reduce the number of queries.
• Sparse fieldsets—select only needed fields via the fields parameter.
• Caching—configure cache tags and use Varnish or FastCGI Cache.
• Database indexes—create indexes for fields that are frequently filtered.

Example optimization: when loading a list of articles with authors and tags, without include there are 1+N+M queries (1 for list, N for authors, M for tags). With include—one query. In a real project, this reduced response time from 3 to 0.2 seconds.

What's Included in Our Work

• Audit of current architecture and selection of the appropriate API approach (REST/JSON:API/GraphQL)
• Configuration of JSON:API with OAuth 2.0, filtering, relationship inclusion, pagination
• Development of custom REST resources for non‑standard scenarios
• Performance optimization: caching, cache tags, Varnish/FastCGI
• API documentation in OpenAPI format
• Client team training on working with the API
• Launch support (2 weeks of free support after launch)

Process

1. Analysis—we study your architecture, load, requirements.
2. Design—we select the stack (JSON:API or REST), design endpoints.
3. Implementation—code, configure authentication, caching.
4. Testing—load testing, checking for N+1, cache.
5. Deployment—roll out to production, monitoring.
6. Support—bug fixes, consultations.

Timeline and Cost

Basic JSON:API setup with OAuth—from 2 to 4 days. Custom REST resources—from 2 to 5 days. Cost is calculated individually after an audit. We guarantee stable API operation under loads up to 1000 requests per second.

Guarantees

• 5+ years of experience—delivered 20+ Drupal integrations
• Certified Drupal and Symfony specialists
• Code warranty—6 months of free fixes
• N+1 Query Prevention—no more than 4 SQL queries per page on all requests

Get Your Project Evaluated

Contact us for a consultation—we will analyze your task and propose the optimal solution. Order a turnkey integration development: get a ready API with documentation and support.