Deniz Kaya
Back to selected work
Postcode Lottery GroupVriendenLoterij

Postcode Loterij / Campaigns & APIs

Campaign websites
& API integrations.

For three and a half years, I worked on campaign websites and partner integrations at Postcode Loterij. Alongside the planned work, I was often called in to help investigate incidents.

70+Campaign websites per year
More than doubledAnnual partner integrations
3½ yearsAcross campaigns and platform teams
Client
Postcode Loterij
Duration
Three and a half years
My contribution
Campaign delivery, API onboarding & incident investigation

My role & approach

My role

I worked across campaign delivery, partner API integrations and incident investigation. For campaign launches, I checked requirements and technical feasibility, tested functionality and data processing in production, and gave the final go or no-go.

How I approached it

I worked with marketers on campaign ideas and A/B tests. When the CMS could not support a requirement, I took it to the platform team. Together, we turned recurring needs into reusable features rather than building a separate fix for each campaign.

Getting a campaign partner connected
Partner accessPartner APIs.
Different campaigns.

Football clubs and other partners connected their own forms to the lottery platform.

Documentation
Explain the API and answer technical questions
Access
Arrange the systems and environments needed
Implementation
Support the partner while they build
Production checks
Check that data is processed correctly

Working with external partners

Helping partners use our APIs

Football clubs and other campaign partners used our APIs in their own forms. I explained the documentation, arranged access and helped them through implementation and production testing.

Making room for more integrations

We simplified onboarding and automated parts of the process. That helped us more than double the number of external integrations we delivered each year.

When something went wrong

Service management often brought me in during incidents. I looked through the logs to work out where the problem came from, shared what I found with the teams involved and helped get a fix started quickly.

Get in touch