> For the complete documentation index, see [llms.txt](https://docs.goproxies.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goproxies.com/proxies/faq/general-questions/e-mail-dashboard-user-vs-api-user.md).

# E-mail Dashboard user vs API user

### Intro

When using Goproxies, you will have two types of credentials - one is the **Dashboard Access** and the other is **API user** for proxy.  Each serves a different purpose — one for managing your account and accessing reports, the other for accessing proxy services.

### **Dashboard Access:**

The format of these credentials are:

* email for a username, e.g <someone@example.com>
* alpha-numeric password.

\
They are used when going to [dashboard.goproxies.com](http://dashboard.goproxies.com) , or by pressing “log in” on the top-right of the general [goproxies.com](http://goproxies.com) website:

<img src="/files/OSMeOKZ4DaLxoHwD1Oo3" alt="" data-size="original">&#x20;

Unless you registered on your own with Google authentication, please enter the email and password for the dashboard access under “Email” and “Password” respectively:

<img src="/files/DR51nMeUvU5MPSQwt0Pe" alt="" data-size="original">

### **API users (for proxy access)**

### &#x20;These are credentials that you use to make proxy requests with, for example (if you’ve purchased a residential proxy):

`curl --proxytunnel --proxy "https://customer-USERNAME:PASSWORD@proxy.goproxies.com:1080" https://ip.goproxies.com`

Where the username and password are the ones that either the GoProxies team manually created for you (which they will always label as “API User”) or you’ve either generated one on your own on the dashboard as you were purchasing the product:<br>

![](/files/DVxidhzhBlauHhlG9u4x)<br>

![](/files/xhJ0UFayETRy3tuSCoMX)

**Important! If you’ve missed this window and failed to copy the password, please reach out to the GoProxies support team and they will help you have it recovered.**

<br>

{% tabs %}
{% tab title="JavaScript" %}

```javascript
const message = "hello world";
console.log(message);
```

{% endtab %}

{% tab title="Python" %}

```python
message = "hello world"
print(message)
```

{% endtab %}

{% tab title="Ruby" %}

```ruby
message = "hello world"
puts mess
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.goproxies.com/proxies/faq/general-questions/e-mail-dashboard-user-vs-api-user.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.