Skip to main content
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.

General

Rename the bucket, change its dashboard color, toggle active or inactive status, and open the deletion flow.

Behavior

Configure the response the webhook sender receives. Queue buckets return a static acknowledgement; proxy buckets wait for the downstream destination response.

Domains

Change the editable label segment of the generated Repost endpoint. Repost checks availability before saving the new endpoint.

Delete

Permanently remove the bucket after typing its exact name to confirm. Active replay jobs block deletion until they are resolved.
Response mode — Queue or Proxy — is permanent after creation and does not appear in settings. To change modes, create a new bucket.

​
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.
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.
Sets the dashboard label color using a hex value. Use distinct colors to tell environments or providers apart at a glance.
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.

​
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.
1

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.
2

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"}.
Example body
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.

​
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.

Valid labels

Use lowercase letters, numbers, and hyphens. Labels must be between 1 and 63 characters and cannot start or end with a hyphen.

Availability check

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.
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.
The Domains settings page also shows Custom Domains as an upcoming capability. Generated Repost domains are the configurable endpoint available today.

​
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.
1

Open General settings

Navigate to the bucket’s settings page and find the destructive operations area in the General section.
2

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.
3

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.
4

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.
Event history and forward logs are retained for quota tracking purposes and are cleaned up according to your plan’s retention policy after deletion.

Create a bucket

Choose the permanent response mode and create the first ingress endpoint.

Response behavior

Understand how Queue and Proxy modes respond to webhook providers.

Bucket domains

Change the generated Repost endpoint label and verify availability.

Configure forwarders

Tune destination, timeout, retry, rate limit, pause, and delete behavior for each forwarder.

Inspect event history

Confirm provider calls, delivery attempts, responses, and failures after making settings changes.