Laravel API Developer UK
APIs and integrations as data-flow problems: auth, idempotency, retries, and what happens when the other system lies.
API work is mostly integration work
A Laravel API that only serves your own SPA is still an API: versioning, auth, pagination, and error shapes. A Laravel API that must stay in sync with a warehouse, an ERP-style system, or WooCommerce is a different job — queues, idempotency keys, and an explicit conflict policy.
Genuine integration pages exist only where the work has been done: Stripe, WooCommerce, WordPress, ERP / warehouse-style systems.
REST APIs, Sanctum, and queued side effects
Product APIs need versioning, auth (Laravel Sanctum where it fits), rate limits, pagination, and error shapes a client can handle. Integration APIs need the other half: Stripe or WooCommerce webhooks, idempotency keys, and an owner for the queue. I will not do seven HTTP calls in a controller and call it an integration.
Process
- Name the contract Who is source of truth, what is sync vs event, what is allowed to fail.
- Auth and abuse Tokens, signing, rate limits. Especially inbound webhooks.
- Queue the side effects Do not do seven HTTP calls in a controller and call it an integration.
- Observe it Failed jobs, replay, a way to see the last payload without SSHing.
Questions that usually come up
Do you build public APIs or just integrations?
Both. Public/product APIs need versioning and auth design. Integrations need failure modes and an owner for the queue.
Can you integrate Laravel with Stripe?
Yes u2014 including webhooks, billing state, and the usual failure modes. See the Stripe integration page.
Can you connect Laravel to WordPress or WooCommerce?
Yes, where there is a real ownership boundary (catalogue, orders, customers) rather than u201cjust embed itu201d.
Do you use Laravel Sanctum or Passport?
Sanctum when it fits (first-party SPA, mobile, simple token APIs). Passport when you actually need a full OAuth server. Neither is a substitute for webhook signing and an owner for the queue.
Qualification
Discuss your Laravel project
Name, work email, and a short description of the application is enough. No discovery call theatre before I know whether I can actually help.
- UK businesses with a real Laravel (or legacy PHP) application
- Build, support, rescue, upgrade or integration work
- Reply from Oliver Burton, usually within one working day