SparkGlim Developer
Integration paths with clear boundaries.
Start from your product and follow the relevant account, resource and checkout contract.
Build a real public campaign directory
Read the existing discovery endpoint from your backend, expose a narrow response and link to the real participant journey.
Start building02Connect the supported ticket purchase handoff
Use real ticket configuration and the existing protected Web client to open the server-created central checkout.
Start building03Hand a real nominee vote to central checkout
Keep nominee eligibility, vote quantities and recorded outcomes under SparkGlim Server authority.
Start building04Connect a real donation to central checkout
Collect configured donor fields and let Server determine currency, fees, eligibility and confirmed contributions.
Start building05Use Organization API Version 1 from your server
Start with an approved domain and complete keys, then use safe reads before private HMAC-signed operations.
Start building06Add a member through the real Reseller workflow
Use the existing session and creator-team relationship without inventing a creator-registration API.
Start buildingSafe implementation
For branded campaigns, establish Organization approval and domain verification before integrating scoped resources.
Public access
For a reseller operation, use the member workflow and assigned permissions. Do not substitute Organization keys for portal sessions.
Payment ownership
For public participation, display permitted information and pass supported requests into centralized checkout. Preserve original campaign and country context.
Prepare the prerequisites
Choose a task-specific tutorial and match every operation to its current endpoint reference. Keep unsupported project requirements visible rather than substituting a private dashboard route.