# Payment APIs

<figure><img src="/files/ZVBTexBVyMwusx8Tmimn" alt=""><figcaption></figcaption></figure>

Integrate PayRam’s Payment APIs to drive transactions from your app or backend, handle payments, webhooks, and more, all under your control.

***

### **Why it matters**

* **Full automations:** Let your backend create and manage payments, no manual intervention.
* **Custom workflows:** Tailor logic before triggering a payment.
* **Real-time feedback:** Use webhooks to react to payments as they arrive or settle.
* **Scalability & control:** Integrate with your architecture and scale usage programmatically.

***

### **Managing API keys**

API keys are required to authenticate all PayRam API requests. Each key is tied to a specific **project**, allowing for environment-level control and security.

**Creating or managing API keys:**

1. Go to **Settings → Accounts** in your PayRam dashboard.
2. Select the **Project** you want to integrate.
3. Navigate to **API Keys**.
4. Copy your **Key**.
5. You can also create new API Keys by clicking on **Add New**.
6. You can also deactivate existing keys by toggling them to inactive.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.payram.com/features/payment-apis.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.
