# API Endpoints

PananaSwap provides **read-only API endpoints** to support analytics, dashboards, and integration use cases.

APIs are designed as a **convenience layer** and do not replace on-chain execution or verification.

***

### Purpose of the API

PananaSwap APIs exist to:

* Improve developer experience
* Reduce the need for direct on-chain indexing
* Provide structured access to aggregated data

APIs are not required to use the PananaSwap protocol.

***

### Read-Only by Design

All PananaSwap API endpoints are **read-only**.

They do **not**:

* Execute swaps
* Sign transactions
* Move user funds
* Modify protocol state

All state-changing actions occur exclusively on-chain via smart contracts.

***

### Typical API Use Cases

Developers may use APIs to:

* Fetch aggregated swap volume
* Display wallet-level statistics
* Show VIP status and progress
* Render dashboards and analytics views
* Monitor protocol usage metrics

APIs are intended for informational purposes only.

***

### Relationship to On-Chain Data

API responses are derived from:

* On-chain transaction data
* Smart contract events
* Deterministic aggregation logic

The blockchain remains the **source of truth**.

API data may lag behind real-time on-chain activity due to indexing and aggregation cycles.

***

### No Execution Guarantees

API data:

* Does not guarantee execution outcomes
* Does not reserve liquidity
* Does not lock prices or fees

Developers should not rely on API responses for critical execution decisions.

***

### Rate Limiting and Availability

API availability may be subject to:

* Rate limits
* Infrastructure maintenance
* Temporary service interruptions

PananaSwap does not guarantee uptime or service levels for API access.

***

### Versioning and Compatibility

API endpoints may evolve over time.

* New endpoints may be introduced
* Existing endpoints may be updated or deprecated
* Breaking changes will be communicated where possible

Developers are responsible for maintaining compatibility.

***

### Security Considerations

When using PananaSwap APIs, developers should:

* Avoid exposing API keys (if applicable)
* Validate and sanitize responses
* Handle errors gracefully

PananaSwap is not responsible for misuse of API data.

***

### Independent Verification

Developers are encouraged to:

* Cross-check API data with on-chain explorers
* Validate assumptions against smart contract events
* Treat APIs as a convenience layer

Critical logic should always rely on on-chain verification.

***

### Disclaimer

API data is provided **“as is”** without warranties of accuracy, completeness, or timeliness.

Use of the API constitutes acceptance of these limitations.
