# Developers

The "**Developers**" menu offers you with his submenu "**API Keys**" and "**Logs**" a technical overview of the various activities in your account.

### API keys

There are three (03) KKiaPay API keys, required to integrate the payment aggregator, that identify you as a KKiaPay approved user.

\
Customer-oriented, the **KKiaPay public key** can be integrated into your Javascript and Android code and is intended to be entered on your WordPress table in the Settings section of our WordPress plugin.&#x20;

**The KKiaPay private key**, only known by you and KKiaPay, is intended for server-side use and allows the verification of transactions made on your account by the KKiaPay API.&#x20;

The latest KKiaPay API key, the **secret key** is a key for server-side use to transfer to your KKiaPay account.

![](/files/-L_JMVpP-xF4PkKaW6mI)

### Logs

This submenu provides you with a complete list of the various requests initiated from your KKiaPay account. For a given request, the following information is available:&#x20;

* The client that initiated the request (Android, Rest, WooCommerce);&#x20;
* The IP address of the initiator;&#x20;
* The resource used; The method used (POST, GET, PUT, etc.);&#x20;
* The date on which the said request was initiated;&#x20;
* The country from which this request was initiated;&#x20;
* The host.

Please note that the list of various requests initiated from your KKiaPay account can be downloaded in CSV format (Excel file).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kkiapay.me/v1/en-1.0.0/tableau-de-bord/untitled/menu-developpeurs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
