# API Key Management

Similar to the Private User API, there is also a Public User API which any customer can access and use to build their own applications and software with information from the Ping Proxies platform.

The Public User API can be accessed by customers with API Keys which can be generated from the dashboard.

There are four API Routes for API Key Management:

```
API Key Search
API Key Retrieve
API Key Create
API Key Delete
```

#### **API Key Creation**

API Keys can be created by the user using the API Key Create Route. This route will an object with this structure:

```json
{
    "created": [
            123
        ],
    "data": {
        "api_key_private_key": "X9akD14swPxtoRtCFVLt00EgtlFha5freNLWIr87nBDK3YfIfopULr7LpiNdHFrd",
        "api_key_public_key": "2f84260dfdd60454f823158b00e60757b81d51e14954cc4ea4b91004d5c46c42"
        },
    "message": "API Key successfully created."
}
```

This private key is then hashed and stored in the database and the public key is kept in plain text for identification and management.

{% hint style="info" %}
There is a limit to the number of API Keys a customer can generate. If they are at the limit then the Create API Key Route will return a 422 Error with a representative message.
{% endhint %}


---

# 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://internal.developer.documentation.private.user.pingproxies.com/customer-account-management/api-key-management.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.