WAEC question bank for CBT app
A WAEC question bank for CBT app is a structured collection of WASSCE questions that developers can use to power examination-practice apps, school CBT systems, mock examinations and other EdTech platforms.
For developers, the important word is structured.
A collection of WAEC past-question PDFs may be useful to students reading manually, but it is not immediately suitable for software. A CBT application needs individual questions, options, answers, years, subjects and other information in a format it can process.
SdashAPI provides this type of structured examination data through an API, allowing developers to build the application while the question-data layer is handled separately.
What should a WAEC question bank contain?
At minimum, a useful question bank should provide:
- Question text
- Answer options
- Correct answer
- Subject
- Examination year
- Unique question ID
For more advanced applications, you may also want:
- Explanations
- Passages
- Images and diagrams
- Topics and subtopics
- Difficulty levels
- Other question metadata
A simplified question record could look like:
{
"id": 48291,
"question": "Which of the following statements is correct?",
"option": {
"a": "Option A",
"b": "Option B",
"c": "Option C",
"d": "Option D"
},
"answer": "b",
"solution": "Explanation of the answer.",
"examtype": "WASSCE",
"examyear": "2024"
}
Your CBT application can turn this structured information into an interactive examination.
Why not simply use WAEC past-question PDFs?
PDFs are designed primarily for people to read, while a CBT application needs data it can understand.
If you start with PDFs, you may need to manually:
- Extract every question.
- Separate the options.
- Identify the correct answer.
- Add the examination year.
- Categorise the subject.
- Preserve passages and diagrams.
- Create unique IDs.
- Convert everything into JSON or database records.
Doing this for a few questions is manageable. Doing it across many subjects and years becomes a separate data-management project.
This is why developers often use an API or licensed structured dataset instead.
Using a WAEC question bank in a CBT app
Suppose a student selects:
Examination: WASSCE
Subject: Biology
Year: 2023
Questions: 40
Your application can request matching questions and create a session:
Student selects examination
↓
Your backend requests questions
↓
Question bank/API returns data
↓
CBT session is created
↓
Student starts examination
The frontend can then provide the timer, Previous and Next buttons, question navigation and answer selection.
At submission, your system calculates the student's score using the correct answers.
Explanations make the question bank more valuable
A CBT app shouldn't necessarily stop at:
Correct Answer: C
If explanation data is available, you can show:
Your Answer: A
Correct Answer: C
Explanation:
[Why C is correct]
This makes the application useful for revision as well as examination simulation.
Students can understand their mistakes rather than simply memorising correct options.
Images and passages matter
Some WASSCE questions depend on diagrams, graphs, tables, maps or passages.
For example:
Study the diagram above and answer the question.
Without the associated image, the question is incomplete.
Your application should therefore be designed to handle optional question images and passages.
A good mobile interface might also allow students to enlarge diagrams or reopen a passage while answering related questions.
Organise questions by subject and year
A properly structured WAEC question bank lets you build useful filters such as:
WASSCE
↓
Mathematics
↓
2024
↓
40 Questions
You can also allow students to combine several years:
Biology Practice
2020–2024
30 Random Questions
This is much easier when subject and year information are stored consistently for every question.
Topic-based practice
If the question data includes topics, your application can go beyond year-based past questions.
For example:
Mathematics Practice
Algebra
Geometry
Statistics
Trigonometry
You can also analyse student performance by topic:
Algebra 82%
Geometry 71%
Statistics 48%
Trigonometry 63%
Your application can then recommend more Statistics practice.
This is one reason developers should consider the richness of a question bank, not just its total number of questions.
WAEC/WASSCE country support
WASSCE is relevant across multiple West African countries, so developers building regional products should avoid designing their database as if every WAEC-related question automatically belongs to Nigeria.
A scalable structure might include:
{
"exam": "wassce",
"country": "ghana",
"subject": "biology",
"year": "2024"
}
This makes it easier to support country-specific collections as your application expands.
You can review currently available examination data on the SdashAPI Coverage Page.
API access or your own question database?
There are two common approaches.
With an API:
CBT App
↓
Your Backend
↓
SdashAPI
↓
Question Data
With a licensed bulk dataset:
Question Dataset
↓
Your Database
↓
Your Backend
↓
CBT App
API access can be simpler when you don't want to maintain the entire examination database yourself.
A bulk dataset may make more sense for projects that specifically require extensive offline access or direct control of the database.
Developers with bulk or specialised requirements can discuss them through SdashAPI Contact.
Start building with 2,000 free credits
If you're still developing your CBT app, you don't need to purchase a large question bank simply to test whether your idea works.
SdashAPI provides 2,000 free development credits.
You can use them to test:
- Fetching WASSCE questions
- Subject and year filtering
- Displaying questions and options
- Answers and explanations
- Images and passages
- Scoring
- Error handling
- Your overall CBT flow
Start through the SdashAPI Website.
When your application is ready for real users, you can generate a separate production API key and choose a suitable option from SdashAPI Pricing.
Protect your production API key
For a production CBT application, avoid exposing sensitive API credentials unnecessarily inside public frontend code.
A common architecture is:
Mobile App / Website
↓
Your Backend
↓
SdashAPI
Your backend keeps the production key and can also enforce your own subscriptions, usage limits and authentication.
Build more than a basic quiz
Once you have a structured WAEC question bank, you can build features such as:
- Timed WASSCE mock examinations
- Practice by year
- Practice by subject
- Practice by topic
- Detailed explanations
- Bookmarked questions
- Questions I Got Wrong
- Weak-topic analysis
- Performance history
- Difficulty-based practice
The question bank provides the data. Your application determines how useful that data becomes to students.
Check coverage before launch
Don't assume every subject has exactly the same number of questions or years available.
Check the actual data your product requires through SdashAPI Coverage before promising specific coverage to users.
Your application can also display only the subjects and years currently available instead of hard-coding unsupported combinations.
Is SdashAPI an official WAEC service?
No. SdashAPI is an independent examination-data service for developers and is not an official API operated by the West African Examinations Council.
Applications using WASSCE data should also make their independent status clear to users.
Getting started
A straightforward development process is:
Create SdashAPI account
↓
Get 2,000 free credits
↓
Generate development API key
↓
Fetch WASSCE questions
↓
Build your CBT experience
↓
Test subjects, years, images and passages
↓
Generate production API key
↓
Choose a production plan
↓
Launch
You can start from SdashAPI, inspect available data through SdashAPI Coverage, and review production options on the SdashAPI Pricing Page.
A good WAEC question bank for CBT app development should save you from spending most of your time manually organising examination data. The question bank supplies structured WASSCE content, while you focus on building the CBT experience students actually use.