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

# Configure Your Repost Bucket Settings After Creation

> Edit bucket name, color, response behavior, active status, and deletion guardrails from the Repost dashboard bucket settings page.

Bucket settings let you manage an existing ingress URL without recreating it. From settings you can rename a bucket, update its dashboard color, toggle its active status, tune the sender response contract, update the endpoint label, and permanently delete the bucket when it is no longer needed.

## What each settings area controls

Settings are organized into four areas. Each one controls a different part of the bucket contract — keep runtime behavior changes separate from dashboard organization changes to avoid unintended side effects.

<CardGroup cols={2}>
  <Card title="General" icon="sliders">
    Rename the bucket, change its dashboard color, toggle active or inactive status, and open the deletion flow.
  </Card>

  <Card title="Behavior" icon="repeat">
    Configure the response the webhook sender receives. Queue buckets return a static acknowledgement; proxy buckets wait for the downstream destination response.
  </Card>

  <Card title="Domains" icon="globe">
    Change the editable label segment of the generated Repost endpoint. Repost checks availability before saving the new endpoint.
  </Card>

  <Card title="Delete" icon="trash">
    Permanently remove the bucket after typing its exact name to confirm. Active replay jobs block deletion until they are resolved.
  </Card>
</CardGroup>

<Note>
  Response mode — Queue or Proxy — is permanent after creation and does not appear in settings. To change modes, create a new bucket.
</Note>

## General: identity and status

General settings control how the bucket appears in the dashboard and its operational status. Changes here do not affect stored event payloads or the provider-facing endpoint URL.

<AccordionGroup>
  <Accordion title="Name" icon="tag">
    Renames the bucket and updates its internal slug. The generated endpoint label under Domains stays unchanged unless you edit it separately. The new name must produce a unique slug — Repost rejects the save if another bucket already uses it.
  </Accordion>

  <Accordion title="Color" icon="palette">
    Sets the dashboard label color using a hex value. Use distinct colors to tell environments or providers apart at a glance.
  </Accordion>

  <Accordion title="Status" icon="toggle-left">
    Toggles the bucket between **active** and **inactive**. Today, inactive buckets still accept and record incoming webhook requests. To stop delivery, pause or disable the bucket's forwarders directly.
  </Accordion>
</AccordionGroup>

## Behavior: tune the sender response

The Behavior settings expose only the fields that apply to the mode you chose when creating the bucket. You cannot switch an existing bucket between Queue and Proxy mode from this screen.

<Tabs>
  <Tab title="Queue bucket">
    <Steps>
      <Step title="Set the acknowledgement status code">
        Use any integer from `100` to `599`. The default set at creation is `200`. This is the HTTP status Repost returns to the provider for every incoming event.
      </Step>

      <Step title="Write the response body">
        Choose JSON or plain text format. When JSON is selected and the body is not empty, it must parse as valid JSON. The dashboard pre-fills `{"status":"received"}`.
      </Step>
    </Steps>

    ```json Example body theme={"languages":{"custom":["/languages/repost.json"]}}
    {
      "status": "received"
    }
    ```
  </Tab>

  <Tab title="Proxy bucket">
    <Steps>
      <Step title="Set the proxy timeout">
        Use a positive integer in milliseconds. The default set at creation is `30000`. This controls how long Repost holds the provider's connection open while waiting for the downstream forwarder.
      </Step>

      <Step title="Align with the provider's own timeout">
        Keep the Repost timeout shorter than the webhook sender's own timeout. If the provider retries requests it considers timed out, a shorter Repost timeout lets it receive a clean error rather than a duplicate.
      </Step>

      <Step title="Remember the proxy constraints">
        Proxy mode returns the downstream response directly to the sender. It does not support async retries, rate limits, functions, secrets, or failed-delivery recovery.
      </Step>
    </Steps>
  </Tab>
</Tabs>

<Warning>
  You cannot switch an existing bucket from Queue to Proxy mode, or from Proxy to Queue mode. Create a new bucket when the sender response model needs to change, then update the provider's webhook URL.
</Warning>

## Domains: change the endpoint label

The Repost endpoint is split into an editable label and a fixed base domain. Changing the label changes the provider-facing URL — the base domain stays the same.

<CardGroup cols={2}>
  <Card title="Valid labels" icon="badge-check">
    Use lowercase letters, numbers, and hyphens. Labels must be between `1` and `63` characters and cannot start or end with a hyphen.
  </Card>

  <Card title="Availability check" icon="radar">
    Repost checks whether the full generated domain is available before enabling the Save button. Save stays disabled while the label is being checked or is unavailable.
  </Card>
</CardGroup>

<Warning>
  Changing the endpoint label takes effect immediately. The old URL stops accepting traffic, so update the webhook provider's configuration before routing production events to the new URL.
</Warning>

<Info>
  The Domains settings page also shows Custom Domains as an upcoming capability. Generated Repost domains are the configurable endpoint available today.
</Info>

## Delete: remove a bucket safely

Deleting a bucket is permanent. It removes the bucket's forwarding configuration, replay jobs, domain settings, and all associated records. The deletion flow requires you to confirm by typing the exact bucket name.

<Steps>
  <Step title="Open General settings">
    Navigate to the bucket's settings page and find the destructive operations area in the General section.
  </Step>

  <Step title="Review what deletion removes">
    Deletion removes the forwarders configured for this bucket, any active or pending replay jobs, the bucket configuration, and the bucket domain. Review this list before proceeding.
  </Step>

  <Step title="Type the exact bucket name">
    The confirmation input is case-sensitive. Repost rejects the deletion request if the typed name does not exactly match the bucket name.
  </Step>

  <Step title="Resolve active replay jobs first">
    If the bucket has replay jobs in a pending, estimating, processing, or paused state, deletion is blocked. Cancel those jobs or wait for them to complete before retrying.
  </Step>
</Steps>

<Note>
  Event history and forward logs are retained for quota tracking purposes and are cleaned up according to your plan's retention policy after deletion.
</Note>

## Related pages

<CardGroup cols={3}>
  <Card title="Create a bucket" icon="inbox" href="/docs/buckets/create">
    Choose the permanent response mode and create the first ingress endpoint.
  </Card>

  <Card title="Response behavior" icon="reply" href="/docs/buckets/response-behavior">
    Understand how Queue and Proxy modes respond to webhook providers.
  </Card>

  <Card title="Bucket domains" icon="globe" href="/docs/buckets/domains">
    Change the generated Repost endpoint label and verify availability.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Configure forwarders" icon="route" href="/docs/forwarders/configuration">
    Tune destination, timeout, retry, rate limit, pause, and delete behavior for each forwarder.
  </Card>

  <Card title="Inspect event history" icon="history" href="/docs/history">
    Confirm provider calls, delivery attempts, responses, and failures after making settings changes.
  </Card>
</CardGroup>