Skip to main content
NEMSA Logo

Nigerian Electricity Management Services Agency

Developer Services

NEMSA Certificate Verification API

Integration guide for ITISEMS, REA and other approved developers and partner systems that need to verify a NEMSA certificate number and retrieve its current certificate status.

API version

v1

Base URL

web.nemsa.gov.ng

Authentication

None for public verification

Method

GET · read only

Recommended integration pattern

Verify one certificate when the user supplies it

For ITISEMS and most partner applications, NEMSA recommends verifying the certificate at the point it is entered or used for a decision. Send the certificate number exactly as supplied by the certificate holder. The same endpoint accepts current canonical NEMSA IDs and preserved historical certificate-number formats.

GET/api/v1/public/certifications/verify?certificateNumber={certificateNumber}
1

Collect

Receive the NEMSA certificate number from the applicant or certificate holder.

2

Verify

Call the public verification endpoint using the supplied number.

3

Check status

Use data.status or data.isActive; HTTP 200 alone does not mean ACTIVE.

4

Link

Where useful, present the returned verificationUrl as the official NEMSA record.

Request contract

The public verification endpoint takes one query parameter.

ParameterRequiredDescription
certificateNumberYesCurrent or preserved historical NEMSA certificate number. Preserve slashes, hyphens and leading zeros. URL-encode the value when constructing the request.

Certificate numbers accepted

Do not remove slashes, hyphens or leading zeros. Send the number as supplied by the certificate holder. NEMSA resolves preserved legacy numbers to the current canonical certificate record where a match is available.

Current NEMSA ID

NEMSA-CEI-ID-000091

Canonical certificate and verification ID used by the current NEMSA platform.

Older short number

D00105

Preserved historical certificate numbers can resolve to their current canonical NEMSA record.

Older scheme format

EMIP/CEIF/PR/II/00382

Legacy values containing slashes are supported. Use URLSearchParams, http_build_query or equivalent URL encoding.

Supported certificate families

The same verification endpoint covers every published NEMSA certificate directory record. Integrators do not need a different endpoint for each certification family.

Conventional Electrical Installation

NEMSA-CEI-IA-000001

CEI uses IA, IB, IC and ID for Individual Categories A-D and C for Corporate certificates.

Renewable Electrical Installation

NEMSA-REI-I2-000001

REI uses I1/I2 for Individual Categories 1-2 and C for Corporate certificates.

Metering Installation Personnel

NEMSA-MIP-I1-000001

MIP uses I1/I2 and C1/C2 because both Individual and Corporate certificates are categorized.

Technical Personnel Certification

NEMSA-TPC-I2B-000001

TPC combines Individual, Level 1-3 and Category A-C in the certificate family code.

Concrete Pole Manufacturer

NEMSA-CPM-C-000143

Canonical certificate family CPM-C.

Meter Manufacturer / Assembler

NEMSA-MMA-C-000045

Canonical certificate family MMA-C.

Historical numbers are resolved whenever NEMSA has that number stored against the migrated certificate record. Some legacy records did not contain a historical certificate number and can only be verified using their canonical NEMSA identifier.

Quick integration examples

These examples all call the same public verification endpoint.

JavaScript / browser

async function verifyNemsaCertificate(certificateNumber) {
  const params = new URLSearchParams({ certificateNumber });
  const response = await fetch(
    "https://web.nemsa.gov.ng/api/v1/public/certifications/verify?" + params.toString()
  );
  const result = await response.json();

  if (!response.ok) {
    return {
      found: false,
      statusCode: response.status,
      error: result.error ?? "Verification failed"
    };
  }

  return {
    found: true,
    holder: result.data.holderName,
    status: result.data.status,
    active: result.data.isActive,
    certificateId: result.data.certificateId,
    certificateNumber: result.data.certificateNumber,
    verificationUrl: result.data.verificationUrl
  };
}

Node.js / TypeScript

const certificateNumber = input.certificateNumber;
const query = new URLSearchParams({ certificateNumber });

const response = await fetch(
  "https://web.nemsa.gov.ng/api/v1/public/certifications/verify?" + query.toString()
);
const result = await response.json();

if (response.status === 404) {
  // No published NEMSA certificate matched the supplied number.
}

if (response.ok && result.data.isActive === true) {
  // Certificate exists and is currently ACTIVE.
}

cURL

curl --get \
  --data-urlencode "certificateNumber=EMIP/CEIF/PR/II/00382" \
  "https://web.nemsa.gov.ng/api/v1/public/certifications/verify"

PHP

$certificate = "D00105";
$url = "https://web.nemsa.gov.ng/api/v1/public/certifications/verify?" .
       http_build_query(["certificateNumber" => $certificate]);

$response = file_get_contents($url);
$result = json_decode($response, true);

if (($result["success"] ?? false) === true) {
    $status = $result["data"]["status"] ?? null;
    $certificateId = $result["data"]["certificateId"] ?? null;
}

Example successful response

The example below illustrates a historical number resolving to its canonical NEMSA certificate record.

{
  "success": true,
  "apiVersion": "1.0",
  "verified": true,
  "submittedCertificateNumber": "D00105",
  "matchedBy": "previousCertificateNumber",
  "data": {
    "certificateId": "NEMSA-CEI-ID-000091",
    "certificateNumber": "NEMSA-CEI-ID-000091",
    "holderName": "CERTIFICATE HOLDER",
    "holderType": "INDIVIDUAL",
    "certificateType": "ELECTRICAL_INSTALLATION_CONTRACTOR",
    "certificateFamily": "CEI-ID",
    "certificateSequence": 91,
    "certificateScheme": "CONVENTIONAL_ELECTRICAL_INSTALLATION",
    "certificateLabel": "Conventional Electrical Installation",
    "scheme": "CONVENTIONAL_ELECTRICAL_INSTALLATION",
    "category": "CATEGORY_D",
    "status": "ACTIVE",
    "isActive": true,
    "expiryDate": "",
    "previousCertificateNumbers": ["D00105"],
    "verificationUrl": "https://web.nemsa.gov.ng/v/NEMSA-CEI-ID-000091"
  }
}

Response fields developers should use

FieldPurpose
verifiedIndicates that a published NEMSA certificate record was found for the submitted number.
submittedCertificateNumberThe certificate number sent by the integrating system.
matchedByIndicates how the supplied identifier matched the NEMSA record, for example a preserved previous certificate number.
data.certificateIdCanonical immutable NEMSA certificate identity.
data.certificateNumberCurrent canonical certificate number returned for the matched record.
data.holderNamePublished certificate-holder name.
data.certificateFamilyCanonical NEMSA certificate family such as CEI-IA, MIP-I2 or CPM-C.
data.statusCurrent lifecycle status. Use this when your workflow requires a specific status.
data.isActiveBoolean convenience flag for workflows that only need to know whether the certificate is currently ACTIVE.
data.expiryDatePublished expiry date where one is available.
data.previousCertificateNumbersHistorical certificate numbers preserved against the same canonical record.
data.verificationUrlOfficial NEMSA verification page that may be shown to an operator or opened from another system.

How ITISEMS and other systems should interpret the result

HTTP / statusMeaningRecommended handling
200 · ACTIVECertificate record exists and its current NEMSA lifecycle status is ACTIVE.Accept as active where your business rule requires a current certificate.
200 · EXPIREDCertificate exists but has expired.Show EXPIRED and the returned expiry date where available; do not treat it as active.
200 · SUSPENDEDCertificate exists but is currently suspended.Show SUSPENDED and do not treat it as active.
200 · REVOKEDCertificate exists but has been revoked.Show REVOKED and do not treat it as active.
200 · PENDINGA published record exists but NEMSA does not currently classify it as active.Show PENDING; do not treat HTTP 200 alone as approval.
404No published record matches the supplied certificate number.Show Certificate not found and allow the user to check the number entered.

Systems that require a currently active NEMSA certificate should check data.status === "ACTIVE" or data.isActive === true. A successful HTTP response confirms that the certificate record was found; the lifecycle status must still be evaluated separately.

Integration guidance

ITISEMS inspection workflow

Verify the certificate when an applicant enters it or before an inspection request is accepted. Store the canonical certificateId with the transaction if your system needs a stable reference.

Partner portals

Use the single-certificate endpoint for eligibility checks, onboarding, application validation or compliance workflows without maintaining a separate local certificate register.

Back-office systems

Display the returned holder, family and lifecycle status to staff, and provide the official verificationUrl when manual confirmation is useful.

Historical certificate numbers

Allow users to enter an older certificate number. Where NEMSA has preserved that number, the API resolves it to the current canonical certificate identity.

Official verification page

Use verificationUrl when a staff member needs to open the official NEMSA verification record in a browser.

QR-code workflows

Printed NEMSA certificates can point to the official verification page, allowing field staff to confirm the current certificate record.

Optional directory integration

The single-certificate endpoint is recommended when a system only needs to validate a certificate supplied by an applicant. Approved integrations that need to search or synchronize published NEMSA directory data can use the public directory endpoint instead.

GET /api/v1/public/certifications/directory

Developer implementation checklist

✓

Send certificateNumber exactly as entered or printed; do not strip slashes, hyphens or leading zeros.

✓

URL-encode the query value by using URLSearchParams, http_build_query or an equivalent library.

✓

Treat the returned canonical certificateId as the stable NEMSA identity when you need to store a reference.

✓

Check data.status or data.isActive; do not use HTTP 200 by itself as evidence that a certificate is currently active.

✓

Handle 404 as Certificate not found and allow the user to verify the number they entered.

✓

Use verificationUrl when staff need to open the official NEMSA verification record.

Public-data boundary

The public API is read-only and returns verification-safe certificate information. It does not expose application documents, payment information, private contact details, staff information or internal workflow data.