Integration marketplace

Connect Verify.ug to authoritative sources.

Connectors let a credential be checked against the register that owns it. Every connector is disabled by default and activated only under a signed integration agreement.

REST

Request/response lookups against a registry endpoint with scoped credentials.

GraphQL

Typed queries for systems exposing a graph API, with field-level selection.

Webhooks

Push notifications when a source record changes, revokes or expires.

CSV / batch

Scheduled bulk reconciliation for registries without a live API.

identity

  • UGPass

    planned

    Uganda national digital identity gateway. Interface defined and stubbed; activation requires an approved data-sharing agreement.

    identity.verifyidentity.assertsession.introspect
  • NIRA

    planned

    National Identification and Registration Authority.

    identity.verifynational_id.verify

government

  • UGHub

    planned

    Government service bus for inter-agency data exchange. Interface defined and stubbed; no live integration is enabled.

    registry.lookupservice.invokeagency.verify
  • Ministry of Education

    planned

    Ministry of Education and Sports.

    institution.verifyschool.lookup
  • Ministry of Health

    planned

    Ministry of Health.

    practitioner.verify

education

  • UNEB

    planned

    Uganda National Examinations Board.

    exam.verifycertificate.verify

business

  • URSB

    planned

    Uganda Registration Services Bureau.

    business.verifycompany.lookup

tax

  • URA

    planned

    Uganda Revenue Authority.

    tin.verify

professional

  • Professional Councils

    planned

    Umbrella connector for statutory councils (Law, Medical, Engineers, etc.).

    licence.verify

finance

  • Banks

    planned

    Aggregated banking KYC connector.

    account.verifykyc.verify
  • Insurance Companies

    planned

    Insurance policy verification.

    policy.verify

Government gateway readiness

The UGPass and UGHub connector interfaces are defined and stubbed in the platform: request and response shapes, capability names, audit logging and failure handling are in place. No live government integration is enabled — activation requires an approved data-sharing agreement with the relevant agency.