# Signup page

{% hint style="warning" %}
**Important:** As a prerequisite to this page, please read the [signup docs here](/developer/less-than-signup-greater-than.md).
{% endhint %}

## Construct the signup page URL

```
https://[SUBDOMAIN].bunny.com/portal/signup
    ?priceListCode=[PRICE_LIST_CODE]
    &token=[TOKEN]
    &returnUrl=[RETURN_URL]
    &couponCode=[COUPON_CODE]
    &firstName=[FIRST_NAME]
    &lastName=[LAST_NAME]
    &email=[EMAIL]
    &companyName=[COMPANY_NAME]
    &billingCountry=[BILLING_COUNTRY]
```

* **`[SUBDOMAIN]`**: Your Bunny account subdomain (e.g., `acme` if you access Bunny via `https://acme.bunny.com`).
* **`[PRICE_LIST_CODE]`**: The code for the price list you want customers to sign up for.
* **`[TOKEN]`** The token from the API client you created with `signup:read` and `signup:write` scopes.
* **`[COUPON_CODE]`** The default coupon code (if valid) be automatically applied.
* **`[RETURN_URL]`** (optional but recommended): A URL to which the user will be redirected after completing signup. Probably your company website.
* **`[FIRST_NAME]`** , **`[LAST_NAME]`** etc are optional default values that will be inserted into the signup fields.

**Example**

Suppose you have the following:

* **SUBDOMAIN**: `acme`
* **PRICE\_LIST\_CODE**: `business-annual`
* **TOKEN**: `12345`
* **RETURN\_URL**: `https://bunny.com`

Then your signup page link would look like this:

```
https://acme.bunny.com/portal/signup?priceListCode=business-annual&token=12345&returnUrl=https://bunny.com
```

When a user clicks this link, they will be taken to the Bunny portal’s **signup page**:

<figure><img src="/files/Vo7aUhxRl79KZupnv27O" alt=""><figcaption></figcaption></figure>


---

# 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://docs.bunny.com/developer/customer-portal/account-signup.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.