Find answers to common questions about the Speso USSD Simulator.
Each USSD interaction starts with a unique session ID. The simulator generates this automatically, allowing your endpoint to track multi-step USSD flows. A session ID helps maintain context across multiple USSD requests within a single conversation.
Yes! You can test locally using a tunneling tool like ngrok. Here's how:
ngrok http 8000The simulator sends the following parameters based on your aggregator's specification:
Not strictly required for testing, but it's recommended for production environments. The simulator supports both HTTP and HTTPS URLs. When deploying to production, always use HTTPS to ensure secure communication between the simulator and your endpoint.
Each USSD session maintains a sequence number that increments with every request sent. This helps your endpoint track the flow of the conversation. For example:
The simulator supports the following USSD aggregators:
Your endpoint should return appropriate responses for different scenarios:
The simulator will display any response your endpoint returns, making it easy to debug issues in real-time.
Yes! The simulator allows you to test with different networks (AT, Glo, MTN, Telecel) and aggregators. This helps ensure your USSD application works correctly across different telecom providers and aggregation platforms. Simply change the network and aggregator dropdowns and send a new request.
The Reset button clears the current USSD session and returns you to the simulator home page. This is useful when you want to:
Yes! You can share pre-filled simulator links by adding query parameters to the URL. Click the example below to try it:
Available parameters:
url - Host URL for your USSD endpointmethod - Request method (get or post)network - Network operator (at, glo, mtn, telecel)phone - Phone numberaggregator - Aggregator (korba, nsano, nalo, arkesel, africastalking)ussd - Initial USSD codeIf you're experiencing connection issues:
© 2025. Speso Technologies Limited