# API Tools & Resources

This section provides essential tools and resources for developers working with the DeDi.global API.

## Overview

To help you get started quickly and efficiently with DeDi.global APIs, we provide comprehensive toolsets including:

* **Postman Collection**: Ready-to-use API requests for testing and development
* **OpenAPI Specification**: Complete API documentation in machine-readable format

## Quick Access

### 🚀 [Postman Collection](/docs/api-tools-and-resources/api-tools/postman-collection.md)

Import our complete Postman collection to start making API requests immediately. Includes pre-configured environments, authentication, and example requests for all endpoints.

### 📋 [OpenAPI Specification](/docs/api-tools-and-resources/api-tools/openapi-specification.md)

Access the complete OpenAPI 3.0 specification for automated tooling, code generation, and comprehensive API documentation.

## Getting Started

1. **For Interactive Testing**: Start with our [Postman Collection](/docs/api-tools-and-resources/api-tools/postman-collection.md)
2. **For Code Generation**: Use our [OpenAPI Specification](/docs/api-tools-and-resources/api-tools/openapi-specification.md)
3. **For Production Integration**: Refer to our [API Reference](/docs/dedi.global-developers/standard-apis.md)

These tools complement our comprehensive [Developer Documentation](/docs/dedi.global-developers/developer-documentation.md) and provide practical resources for seamless API integration.


---

# 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://dedi-global.gitbook.io/docs/api-tools-and-resources/api-tools.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.