# Welcome

Documentation is broken down into different sections based on use.

### WEB REST REQUESTS <a href="#web-rest-requests" id="web-rest-requests"></a>

Web requests are offered using HTTP GET, HTTP POST, or HTTP Json POST, at your preference.&#x20;

To use Json POST, set your header to: Content-Type: application/json

```php
curl https://v1.api19.com/dids/ratecenters/list  \
   -u 'API-Token'

OR

curl https://v1.api19.com/dids/ratecenters/list?key=apitoken

OR

curl https://v1.api19.com/dids/ratecenters/list \
   -d '{key:"mykey", npa:"720"}' \
   -H 'Content-Type: application/json'
```

For instance, the above request would list any areas our phone number pool covers. You can send the API token as a username/password, as a GET variable (token), or as a POST variable.

### NUMBERS / ORDERING <a href="#numbers-ordering" id="numbers-ordering"></a>

This section gives information on listing states / ratecenters, and ordering numbers.

### MY INVENTORY <a href="#my-inventory" id="my-inventory"></a>

Your numbers, listing them and ability to remove them, or reroute them.

### SMS / MMS <a href="#sms-mms" id="sms-mms"></a>

Send and receive SMS / MMS message via our API.

### CALL APIS <a href="#call-apis" id="call-apis"></a>

This section is dedicated to the Call API which allows you to make and receive calls via web REST API calls.

### LOOKUPS <a href="#call-apis" id="call-apis"></a>

Get information about numbers via web REST calls.

### NUMBER PORTABILITY <a href="#call-apis" id="call-apis"></a>

Submit port requests and review port information.

### FAXING <a href="#call-apis" id="call-apis"></a>

Send and receive faxes via the API


---

# 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://apidocs.api19.com/welcome.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.