NECO questions JSON API

A NECO questions JSON API allows developers to retrieve NECO examination questions as structured JSON and use them directly inside CBT apps, exam-preparation platforms, school portals and other EdTech products.

Instead of manually typing hundreds or thousands of past questions into your database, your application can request the questions it needs and receive organised data that your software can process.

SdashAPI provides NECO examination data through its API alongside other supported examinations.

What does a NECO question look like in JSON?

A simplified question object could look like:

{
  "id": 73182,
  "question": "Which of the following is a characteristic of living organisms?",
  "option": {
    "a": "Respiration",
    "b": "Rusting",
    "c": "Melting",
    "d": "Evaporation"
  },
  "answer": "a",
  "solution": "Respiration is one of the essential processes carried out by living organisms.",
  "examtype": "NECO",
  "examyear": "2024",
  "image": null
}

Because the information is structured, your application can immediately identify the question, options, answer, explanation and examination year.

Why use JSON for NECO questions?

JSON works well with most popular development technologies, including:

JavaScript and Node.js
React and React Native
Flutter
PHP
Python
Java
Kotlin
Swift

It also makes it easier to build one question component that works across different subjects and years.

Instead of manually maintaining separate pages for Biology, Chemistry and Economics, your application simply receives different JSON data.

Fetch NECO questions by subject

A student might choose:

Exam: NECO
Subject: Biology
Questions: 40

Your backend can request the appropriate questions and return them to the CBT interface.

The same logic can be reused for another subject:

Exam: NECO
Subject: Economics
Questions: 40

This makes it easier to scale your application as you add more subjects.

Fetch questions by year

Year filtering allows students to practise specific past examinations.

For example:

NECO Mathematics

2024
2023
2022
2021

If the student chooses 2023, your request can specify the examination, subject and year.

Conceptually:

examtype = neco
subject = mathematics
year = 2023

For the current endpoint structure and available parameters, use the SdashAPI Documentation.

Build a CBT session from the JSON response

A simple application flow might be:

Student selects NECO
        ↓
Selects Biology
        ↓
Selects 40 Questions
        ↓
Backend requests question data
        ↓
JSON response is received
        ↓
CBT session starts

Your application can then handle:

Timer
Question navigation
Answer selection
Flag for review
Submission
Scoring
Result display

The API provides the examination data while you control the user experience.

Use explanations for revision

If explanations are available, don't limit your application to showing only the correct answer.

After submission, you could show:

Your Answer: C
Correct Answer: A

Explanation:
Respiration is a biological process carried out by living organisms...

This turns a basic CBT simulator into a more useful revision platform.

Students can understand why their answers were incorrect.

Handle images and passages properly

Some examination questions depend on diagrams, graphs, tables or passages.

Your frontend should therefore be prepared for records containing additional content such as:

{
  "question": "Study the diagram and answer the question.",
  "image": "https://example.com/image.jpg"
}

If image is available, display it.

If it is null, continue normally.

The same principle applies to passages. Your interface should keep the relevant passage accessible while students answer its associated questions.

Use question IDs for useful features

A stable question ID makes features such as these much easier:

Bookmarks

Save Question

Questions I Got Wrong

Review 23 Incorrect Questions

Question reporting

Report Question #73182

Analytics

How many students answered this question correctly?

Instead of saving entire questions repeatedly, your system can reference their IDs where appropriate.

API access vs storing JSON yourself

If you're using an API, the architecture might be:

CBT App
   ↓
Your Backend
   ↓
SdashAPI
   ↓
NECO JSON

If your project requires a licensed bulk dataset, the architecture could instead be:

JSON Dataset
    ↓
Your Database
    ↓
Your Backend
    ↓
CBT App

The second approach can be useful for certain offline applications or projects that specifically require their own examination database.

For specialised bulk-data requirements, you can discuss the project through SdashAPI Contact.

Start with 2,000 free credits

SdashAPI provides 2,000 free credits for development and testing.

That gives you room to test things such as:

NECO question requests
JSON parsing
Subject filters
Year filters
Scoring
Explanations
Images
Passages
Error handling

You can therefore test your application with actual API responses before deciding what production setup you need.

Start from SdashAPI.

Keep production credentials secure

For a live application, a common setup is:

React Native / Flutter / Website
             ↓
        Your Backend
             ↓
          SdashAPI

Your production API key stays on your backend rather than being unnecessarily exposed inside your public application.

Your backend can also control subscriptions, user authentication and usage limits.

Development and production should be separate

During development, use your development credentials to build and test.

When you're ready to launch, generate a separate production API key and choose the production option that fits your expected usage.

Current options are available on SdashAPI Pricing.

This separation also makes it easier to test future application changes without interfering with your live environment.

Check available NECO coverage

Don't hard-code every possible year and subject into your application without first checking what is available.

Review SdashAPI Coverage and design your interface around the data your product actually supports.

For example:

Select NECO
     ↓
Available Subjects
     ↓
Select Chemistry
     ↓
Available Years

This avoids sending users to empty question pages.

Is SdashAPI an official NECO API?

No. SdashAPI is an independent examination-data platform and is not an official API operated by the National Examinations Council.

Developers should also make this distinction clear in their own products.

Getting started

A practical integration can be kept simple:

Create SdashAPI account
        ↓
Get 2,000 free credits
        ↓
Generate development API key
        ↓
Request NECO questions
        ↓
Receive JSON
        ↓
Build your CBT features
        ↓
Test with real question data
        ↓
Create production API key
        ↓
Launch

You can use the SdashAPI Documentation for integration guidance, SdashAPI Coverage for available examination data, and SdashAPI Pricing when you're ready for production.

A NECO questions JSON API gives developers a cleaner way to work with examination questions. Rather than spending a large part of development manually converting past questions into software-ready data, you can focus on building the CBT, revision and learning experience around them.