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

# Creating Requests

> Create a BeatPass request by writing a clear brief, adding a reference track, choosing a 24, 48, or 72-hour duration, and spending the required tokens.

Creating a beat request is how you tell BeatPass producers what sound you need. The stronger your brief is, the better your incoming matches tend to be.

***

## Before You Start

<CardGroup cols={3}>
  <Card title="Tokens Available" icon="coins">
    You need at least one token to post, and longer durations cost more.
  </Card>

  <Card title="Reference Track Ready" icon="music">
    A valid public URL is required before the request can be submitted.
  </Card>

  <Card title="Clear Brief" icon="file-lines">
    Plan the style, mood, tempo, and use case you want before opening the form.
  </Card>
</CardGroup>

<Warning>
  Posting the request spends tokens immediately. The cost is **1 token** for **24 hours**, **2 tokens** for **48 hours**, and **3 tokens** for **72 hours**.
</Warning>

***

## Step-by-Step Guide

<Steps>
  <Step title="Open Beat Requests">
    Go to **Beat Requests** and click **Submit Request**.
  </Step>

  <Step title="Fill out your brief">
    In **What kind of beat do you need?**, write a clear description of the sound, mood, tempo, and context. The description must be between **10** and **500** characters.
  </Step>

  <Step title="Add optional Beat Details">
    Use the **Beat Details** area for **Genre**, **BPM**, **Mood**, **Key**, **Scale**, and **Budget**. These fields are optional, but they usually help producers self-filter and send better matches.
  </Step>

  <Step title="Add your Reference Track">
    Paste a valid public URL into **Reference Track**. The form accepts links such as YouTube, Spotify, SoundCloud, and other public URLs.
  </Step>

  <Step title="Choose Request Duration">
    Under **Request Duration**, choose **24**, **48**, or **72** hours. The selected duration determines how many tokens are spent.
  </Step>

  <Step title="Submit the request">
    Click **Submit Request**. BeatPass posts it immediately, deducts the token cost, and starts the live countdown right away.
  </Step>
</Steps>

***

## Writing an Effective Description

Your description is the most important part of your request. Here's how to write one that attracts the right producers:

### Do Include

* **Specific genre and subgenre** — "Melodic trap" is better than just "trap"
* **Mood and energy level** — "High energy, aggressive" or "Laid back, smooth"
* **Instrumentation preferences** — "Heavy 808s," "Live guitar," "Synth-heavy"
* **Artist references** — "Similar to Drake's recent style" or "Metro Boomin vibes"
* **Purpose** — "For a club track" or "For a personal project"

### Avoid

* **Being too vague** — "I need a good beat" doesn't help producers
* **Conflicting requirements** — "Fast and slow" or "Happy but sad"
* **Unrealistic expectations** — Be reasonable with your requests

### Example Descriptions

**Good Example:**

> Looking for a melodic trap beat with emotional piano melodies and hard-hitting 808s. Think Lil Baby or Gunna style. Need something around 140 BPM in a minor key. This is for a personal project about overcoming struggles.

**Poor Example:**

> Need a fire beat ASAP, something that slaps. Make it good.

***

## What Happens After You Submit

| What Happens                        | What It Means                                              |
| ----------------------------------- | ---------------------------------------------------------- |
| **Request goes live**               | Producers can see it right away in the public request feed |
| **Token cost is applied**           | BeatPass deducts 1, 2, or 3 tokens based on your duration  |
| **Verified producers are notified** | Auto-notifications go to verified producers                |
| **Countdown starts**                | Your request stays active for the selected window          |
| **Submission count can increase**   | Producers can submit matching tracks from their catalog    |

***

## Request Requirements

| Field           | Required | Limits                                                             |
| --------------- | -------- | ------------------------------------------------------------------ |
| Description     | Yes      | 10-500 characters                                                  |
| Reference Track | Yes      | Valid URL, max 500 characters                                      |
| Genre           | No       | Max 100 characters                                                 |
| BPM Range       | No       | Max 20 characters, numbers/dashes/spaces                           |
| Key             | No       | Max 10 characters                                                  |
| Mood            | No       | Max 50 characters                                                  |
| Budget          | No       | Max 50 characters, usually amount/range plus USD, CAD, EUR, or GBP |

***

## Common Questions

<AccordionGroup>
  <Accordion title="Can I edit my request after posting?">
    No. If you need to change something, delete the request and post a new one. Active requests can refund tokens up to the original spend, capped by your current plan limit.
  </Accordion>

  <Accordion title="What if I don't have any tokens?">
    You need to wait for the monthly reset, delete an active request to recover tokens if you are below your plan cap, or change to a plan with a higher allowance.
  </Accordion>

  <Accordion title="Can I create multiple requests at once?">
    Yes, as long as you have enough tokens. Each request costs 1 to 3 tokens depending on the duration tier you choose.
  </Accordion>

  <Accordion title="Why is a reference track required?">
    Reference tracks help producers understand exactly what sound you're looking for. Without one, you're likely to receive submissions that don't match your vision.
  </Accordion>
</AccordionGroup>

***

## Related Topics

<CardGroup cols={2}>
  <Card title="Understanding Tokens" icon="coins" href="/help/beat-requests/understanding-tokens">
    Learn how the token system works.
  </Card>

  <Card title="Request Specifications" icon="sliders" href="/help/beat-requests/request-specifications">
    Details on all the optional fields.
  </Card>
</CardGroup>