API and System Integration Services

Most business software problems live between systems. The data exists, but it sits in one tool while the work happens in another.

I connect systems through their APIs and webhooks, and I build the layer in the middle so the connection survives bad data, outages, and rate limits.

Integrations I have built

Payments with Stripe webhooks

I built the Stripe webhook handling for RE/AMP. Webhooks need care: events can arrive late, twice, or out of order, so the handler has to tolerate all three.

SMS with Twilio

RE/AMP sends and receives text messages through Twilio using each company’s own API key and credentials. That design keeps each company’s messaging separate from the others.

Email through IMAP

I integrated self-hosted Mailcow email with IMAP processing. The work covers message metadata, body retrieval, caching, polling, and pausing a connection when authentication fails.

Ad platform feeds

I wrote a Go API and ETL pipeline that moves vehicle inventory from dealership data into Google and Facebook advertising systems. It is still used for inventory marketing. Read the inventory feed project.

Data validation APIs

My phone scrubber checks numbers through the Trestle API in batches that respect the provider’s rate limit. See the phone scrubber project.

Browser to API calls

I wrote a JavaScript snippet that read a VIN from the ad click URL, called the same API that built the ad feed, and updated the vehicle page price and legal disclaimer to match the ad.

What makes an integration hold up

• Idempotency. Running the same event twice must not create two charges or two records.
• Retries and backoff. Temporary failures should retry on a schedule, not hammer the other service.
• Queues for limits. A queue turns a hard rate limit into a predictable job.
• Authorization. Each tenant’s credentials stay separated and stored with care.
• Visibility. Logs and alerts tell you which connection failed and why.

How I approach an integration project

1. Read the API documentation. I check limits, authentication, and failure modes first.
2. Map the data. I define what each side calls things and how they translate.
3. Build the connector with tests. I test with bad input, empty responses, and repeated events.
4. Add monitoring. I wire up health checks and error alerts.
5. Document. I write down how to rotate keys, retry failures, and add the next integration.

Frequently asked questions

Do you build the API itself or only connect to existing ones?

Both. I build REST APIs in Node, Express, Django, and Go, and I connect your systems to outside APIs.

Can you integrate with software that has no API?

Sometimes. If a tool offers only a web interface, browser automation may work, but it is more fragile. I will tell you the tradeoff before building.

Do you handle payments?

I have built Stripe webhook handling. I have not built a full subscription billing platform, and I will say so before you plan around it.

How do you keep integrations from breaking?

I test for failure cases, add queues and retries, and monitor the connection. Outside APIs change, so ongoing support is available.

Can you work with Zapier or n8n instead of custom code?

Yes. If a workflow tool does the job, it is the cheaper answer, and I will recommend it.

Tell me which systems need to talk

Name the tools and what should happen between them. I will reply with how I would connect them.

Request a quote or see how engagements work.