What is possible
Integration starts with clear responsibilities.
Example of a project-specific REST integration: the brand frontend submits campaign reference, code and the agreed entry data. The Engine returns a process reference and result, or an input error that can be corrected. The frontend displays the appropriate feedback. Later, the warehouse system confirms dispatch separately; an accepted entry is not yet a shipped prize.
- Your frontendBrand design, user experience and touchpoint stay in your stack.
- REST integrationA project-specific contract passes participation, code evidence and campaign context.
- Engine and handoffsDraw, redemption, events, support and fulfilment have clear statuses and owners.
The campaign journey
The API hands over into the complete campaign lifecycle.
Your team owns the frontend, Prowerb the agreed Engine operations. Participation, review, prize allocation and follow-up steps stay connected through defined data handoffs.
View all ten campaign stages
- 01Idea
- 02Brand experience
- 03Entry
- 04Review
- 05Draw
- 06Confirm prize
- 07Source
- 08Deliver
- 09Support
- 10Learn
Workflow and software
Pass data and process the response.
See which data your frontend passes to the Engine and how the response is processed.
- Frontend contractForm, copy, consent and error states stay with the visible participation experience.
- Participation contractParticipation, code evidence and campaign context are passed unambiguously.
- Event handoffPrize allocation, redemption, shipment and reporting return the agreed statuses.
People and delivery
Developers and brand managers review the same handoff from two perspectives.
Brand experience, data contract, error handling and operational consequences are agreed together using a concrete integration handoff.
- Brand managerConfirms the brand moment, participation logic and visible status messages.
- DeveloperMaps REST handoff, participation, code evidence, events and error states.
- Campaign operationsTakes over decisions, redemptions, support and fulfilment with the required context.
Next step
Align the integration around your campaign workflow.
The integration workflow shows your frontend, project-specific REST connection, participation, code evidence, draw and responses as the basis for discussion.