Overview
The Events Integration Service API lets you programmatically manage the complete event lifecycle on the Little Events platform — from creating an event and configuring tickets, to processing payments and pulling sales reports.
What is Little Events?
Little Events is an event management and ticketing platform that enables organisers to create events, sell tickets (with support for multiple ticket tiers), process payments via various providers such as (M-Pesa, Cards, Airtel), manage discount codes, and track affiliate sales — all from a single dashboard.
The Integration API opens up these capabilities to external applications, so you can embed Little Events functionality directly into your own website, mobile app, or backend system.
What can you do with the API?
| Capability | What you can do |
|---|---|
| Events | Create, update, and list events for your organiser account |
| Ticket Prices | Define ticket tiers with pricing, stock limits, sale windows, and display order |
| Discount Codes | Create percentage or fixed-amount codes with optional redemption caps |
| Affiliates | Set up affiliate tracking codes, link them to discounts, and pull per-affiliate sales data |
| Payments | Initiate ticket purchases with support for M-Pesa, Cards, Airtel, MTN, and TigoPesa |
| Sales Reporting | Query event-level and price-tier-level sales with date filters and pagination |
| Complimentary Tickets | Issue free tickets to guests, and pull a per-price summary of what you have sent against your free comp allowance |
| Webhooks | Receive real-time payment status callbacks (COMPLETED / FAILED) |
Typical integration flow
A typical integration follows these steps:
- Get your API key — Generate a key from your organiser dashboard.
- Create an event —
POST /eventswith your event details, poster image, and show timings. - Add ticket prices —
POST /ticket-pricesfor each tier (e.g. Regular, VIP). - Optionally add discounts / affiliates — Set up codes for promotions or tracking.
- Process payments —
POST /payments/initiateto start a ticket purchase. - Handle webhooks — Receive payment confirmation callbacks on your
CallbackURL. - Check sales —
GET /sales/{EventID}for revenue and ticket count breakdowns. - Issue comps —
POST /complimentaries/sendto give guests free tickets, andGET /complimentaries/event/{EventId}to review what you have sent.
Base URL
| Environment | URL |
|---|---|
| Production | https://apps.little.africa/events/integrations/api |
Response envelope
All endpoints return a consistent JSON structure:
{
"success": true,
"message": "Human-readable status message",
"data": { }
}
success—truefor successful operations,falsefor errors.message— A description of what happened.data— The endpoint-specific payload (object, array, or omitted on errors).
Some error responses also include a code field matching the HTTP status code.
Documentation sections
| Section | Description |
|---|---|
| Getting Started | Make your first API call in under 5 minutes |
| Authentication | API key usage, rotation, and security model |
| Pagination | Navigate large result sets |
| Error Handling | Status codes, error envelopes, and retry guidance |
| Webhooks | Payment callback flow and setup |
| Best Practices | Rate limits, idempotency, and production tips |
| Testing | Test events, going live, event visibility, and test card numbers |
| API Reference | Every endpoint with request/response schemas |