# Quickstart

* **Create an Account**\
  Sign up on [Padiwise](https://padiwise.com) and complete your KYC verification. The process is fast, it takes less than a minute.
* **Start Building**\
  Use our comprehensive API documentation and endpoints to begin integrating Padiwise services into your platform. Our tokens are long-lived, so you don’t need to worry about frequent renewals.

{% hint style="info" %}
*Note: API tokens are available only to registered agent users.*
{% endhint %}

#### **API Environment Details**

To make testing and developing with our API, we make use of the different API endpoints for sandbox and production, with the same **access token** used when calling the APIs.

| Name          | Value                                                                 |
| ------------- | --------------------------------------------------------------------- |
| {{ BASE }}    | <https://padiwise.com/api/v1/>                                        |
| {{ SANDBOX }} | [https://padiwise.com/api/sandbox/](https://padiwise.com/api/sandbox) |

### Requests and Responses <a href="#requests-and-responses" id="requests-and-responses"></a>

Both request body data and response data are formatted as JSON. Content type for responses will always be `application/json`. Generally, all responses will be in the following format:

{% code overflow="wrap" lineNumbers="true" %}

```php
{
  "status": "[boolean]",
  "message": "[string]",
  "data": "[object]"
}
```

{% endcode %}


---

# 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://padiwise.gitbook.io/padiwise/getting-started/quickstart.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.