How to use MeVerify API keys

A short guide on how to manage your API keys in the dashboard

Overview

This guide will help you understand the different type of key in your MeVerify Dashboard, how to manage them, and make effective use of them.

At MeVerify we have the following Keys;

Client Token
Public API Key
Secret Key

Client token

As the name implies, the client token is needed when you want to interface with the Client-side, this include using it in the web for getting support or resolving issues with our support desk.

Public API key

The Public API Key is such that gives you access to data in real-time.
It's majorly used alongside the secret key during integration.
Unlike the Client-Token, the Public API Key can be refreshed to generate a newer key.

Secret key
The secret key is your gateway to maximizing MeVerify suites of API's, the secret key is always needed at the point where you'll need to interface with MeVerify API.
The secret key should be kept safe and should not go to the public.

📘

📘 NOTE

Interchangeably using Secret Key in scenarios where you ought to use Public Key and Vice-Versa will cause an error, therefore ensure you cross-check your keys properly before and during testing your projects to avoid errors.

To get your keys, visit your dashboard