# Get templates

`GET https://api.cryptohopper.com/v1/template`

Part of [Templates](https://www.cryptohopper.com/api-documentation/api-reference/templates.md) in the Cryptohopper API reference.

Returns the user's own templates, sorted by name, with the number of templates in result.

OAuth scope: `read`

hasTriggers, hasConfigPool and hasSignals are 1 whenever the stored value is not empty, which includes an empty list, so they can be 1 for a template without triggers, pools or signals. logo is a bare file name (for example binance-usdt.jpg) when the template has no image of its own. item_id is null for own templates.

## Headers

| Name | Type | Required | Description |
|---|---|---|---|
| `access-token` | string | yes | The OAuth access token of the user. |

## Example request

```bash
curl "https://api.cryptohopper.com/v1/template" \
  -H "access-token: YOUR_ACCESS_TOKEN"
```

## Response

Example response (illustrative values):

```json
{
    "data": {
        "templates": [
            {
                "template_id": "138000",
                "type": "template",
                "item_id": null,
                "name": "My BTC bot",
                "description": "Trend following on USDT pairs",
                "logo": "https://cdn.cryptohopper.com/images/hoppers/templates/138000_2026-09-01-10-15-00.jpg",
                "exchange": "binance",
                "base_currency": "usdt",
                "currencies": "BTC,ETH",
                "hidden_configuration": "0",
                "hasTriggers": 1,
                "hasConfigPool": 1,
                "hasSignals": 1,
                "created_date": "2026-09-01 10:15:00"
            }
        ],
        "result": 1
    }
}
```

Status codes: 200. Errors return JSON with `status`, `error` and `message`, plus a numeric `code` when the error comes from the API itself rather than the gateway.