Laravel API development and integrations
APIs for your own apps, APIs for partners, and connections to the systems you already use: CRMs like Salesforce, booking and payment providers, market data. I build them so they keep working when the other side changes, for companies with no developer of their own and for teams that want someone who has done this before.
I'm all in on AI. It lets me get through a lot of work in a short time, and I stay careful about the code and about what goes live. Laravel and Vue are what I use most. I'm based in Germany and work with clients in Europe and the US.
I usually reply within one working day.
What I build
APIs in both directions: the ones you offer and the ones you consume.
APIs for your web and mobile apps
A clean REST API with authentication over Sanctum or Passport, versioning so old app versions keep working, and documentation your app developers can build from without asking me.
APIs for partners and customers
API keys, rate limits, per-partner permissions, usage you can see and bill. I have built partner APIs on top of a search platform with more than 200 million records.
Two-way sync with CRMs and ERPs
Salesforce, HubSpot, your accounting system. Sync in both directions without duplicates or lost updates, with logs that show what happened when a record does not match.
Payments, bookings and market data
Stripe, Paddle, booking providers with OAuth logins and webhooks, financial data feeds. I have shipped all of these in production.
Webhooks that don't lose events
Verified signatures, retries, idempotency, and a queue in between so a slow database never makes you miss a payment event.
Keeping integrations alive
The other side changes its API, rotates keys, or goes down for a while. Monitoring, alerts and sensible fallbacks, so you hear about it from a notification and not from a customer.
How I work
You don't need to have everything figured out before we talk. An idea, access to the repo, a screen recording or a list of problems is enough. I look at what is there, tell you what I would do and what it costs, and then I build it.
I use Claude Code, Codex and my own agent workflows for reading code, planning changes, writing tests, refactoring and debugging. It is not vibe coding. It is senior engineering with a much faster loop.
AI-first, on the boring parts too
Claude Code and Codex write the API clients, the request validation, the tests against recorded responses and the documentation, which used to be the slow, tedious part of integration work. I decide how the integration should behave when things go wrong, and I test that part myself.
I stay in control
AI writes a lot of my code. I still make every technical decision, read every change before it ships, and test it. Fast, but meticulous: the speed is only worth something if what goes live is right.
The way you want to work
Some clients want to look at every change before it goes live, others want me to deploy. Some want a weekly call, most prefer written updates. I work well asynchronously, and I still ask the important questions when they come up.
I think like an owner
I still run my own online products. So when I build or fix yours, I think about traffic, conversion, revenue and support as much as about the code, and I tell you when something is not worth building.
Ways to work with me
Fixed price, a flat monthly rate, or hourly. It's always me doing the work, not an agency. If you're not sure, describe what you need and I'll suggest one.
Examples of my work
APIs and integrations I have built.
Second booking provider with OAuth and webhooks
I built a second booking-provider integration for a live healthcare product: staff login over OAuth, data sync, appointments, notes, classes and webhooks, and moved the existing integration onto the same clean pattern, while the product kept running.
Salesforce sync made reliable
A two-way Salesforce sync for property listings and inquiries inside a Laravel site that had been unreliable for years, fixed as part of a larger takeover and upgrade.
Partner API over 200 million records
A secure API for external partners on top of a search platform with more than 200 million records and answers in under 50 milliseconds, built with Laravel and MeiliSearch across multiple servers.
What clients say
"Vincent is one of those rare developers who can jump into a complex codebase, become useful immediately, and solve real problems without hand-holding."
"Vincent works very well asynchronously: communication stays focused, there is little unnecessary back-and-forth, and he still raises the important questions when needed."
"Vincent was easy to work with and produced high-quality code. Would recommend."
Questions
Can you connect us to a specific system?
I have connected Salesforce, booking providers with OAuth and webhooks, Stripe and Paddle, market-data APIs, DeepL, several AI providers, freelancer platforms and TMDb. If the other side has an API, the answer is usually yes.
Do you write documentation for the API?
Yes. Partners and app developers get documentation they can work from without asking me, usually as an OpenAPI spec plus examples.
How do you handle security?
Tokens or OAuth for access, rate limits, verified webhook signatures, and permissions that are checked on the server. The usual things, done properly.
What happens when the other side's API changes?
That is why integrations need monitoring and tests against recorded responses. You find out from an alert, and the fix is usually small if the integration was built cleanly.
Do you build the mobile app too?
No. I build the API and the backend for it, and I work with your app developer.
How do you charge?
Fixed price for a job with a clear outcome, a flat monthly rate for ongoing work, or hourly. Describe what you need and I'll suggest one.
Get a quote
What should talk to what, and what exists already. A few sentences are enough. I'll reply with how I would build it and what it would cost.
If you would rather talk first, book a 30-minute call.