Skip to main content
The confirm endpoint lets you submit multiple WAEC certificates for confirmation in a single request. The platform looks up each one independently and returns the full candidate record when a match is found. This guide covers how to structure the request, process the response, and handle the case where a certificate is not found.

How it works

  1. You send a POST request with an array of certificate entries — each with a country, candidate_number, and year.
  2. The platform queries each entry against the WAEC database.
  3. The response contains one result object per entry. Entries that matched include the full certificate data; entries with no match return result: null.
  4. For confirmed certificates where the candidate has a registered email, a digital copy is sent to them automatically.
The entire request always returns 200 OK. Per-entry outcomes are determined by the result field — not the HTTP status code.

Confirm a single certificate

Confirm multiple certificates

Add as many entries as needed to the certificates array. Each is processed independently:

Processing the response

Iterate through the data array and check each entry’s result field:

Handling not-found results

When a candidate is not found, the entry looks like this:
is_error is false — this is an expected outcome, not an API error. Use result === null as your not-found check.

Viewing confirmation history

After confirming certificates, you can retrieve a full log of your account’s confirmations — filterable by year, candidate number, and date range:
See the Confirmation History reference for all available filters and the full response schema.