> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cccambox.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Making Requests

> Learn how to send your first authenticated request to the CCCAMBOX TV Reseller API using cURL.

This page shows how to make your first API request with cURL.

Before you begin, make sure you have:

* A valid API key
* HTTPS access to the API
* A terminal with `curl` available

If you still need a key, see [API Keys](/doc/api-keys).

## Your first request

Store your API key in an environment variable:

```bash theme={null}
export CCCAMBOX_TV_API_KEY="YOUR_API_KEY"
```

Then send a request to the `/v1/me` endpoint:

```bash theme={null}
curl --request GET \
  --url https://api.reselliptv.com/v1/me \
  --header "x-api-key: $CCCAMBOX_TV_API_KEY"
```

This endpoint returns information about the authenticated reseller account.

## Example response

If the request succeeds, the response will look similar to this:

```json theme={null}
{
  "credits": 1000,
  "lines_count": 42,
  "server_information": {
    "hostname": "http://example-iptv.com",
    "mag_portal_url": "http://example-iptv.com/mag/portal.php"
  }
}
```

Here is what the response fields mean:

* `credits`: the number of credits currently available on your account
* `lines_count`: the total number of lines linked to your account
* `server_information`: connection details related to your reseller service

## Common issues

If the request fails, check the following first:

* Your `x-api-key` header is present
* Your API key value is correct and complete
* The request is being sent over HTTPS
* The API key is still active

If authentication fails, the API will usually return a `401 Unauthorized`
response. For more details, see [Authentication](/doc/authentification) and
[Error Handling](/doc/error-handling).

## Next steps

* Explore [Protocol](/doc/protocol) to understand request and response rules
* Review the endpoint reference to start creating and managing lines
* Use the same `x-api-key` header pattern for all authenticated requests