SparkGlim Developer
Connect a public campaign experience.
Keep campaign information and participation on their existing public paths, within your approved integration model.
Public access
Use documented public data to render eligible information, or link to the canonical campaign page. There is no universal iframe URL promised here.
Organization access
Organization storefront reads expose permitted campaigns and ticket types under an approved domain and a limited key.
Safe implementation
Keep private keys, signing and protected records on your server. Use the existing checkout URL for paid participation.
Keep the integration dependable
Reserve responsive media space and provide direct campaign links if embedded presentation is unavailable. A custom display must preserve the campaign’s actual dates, currency, availability and public visibility.
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 building