---
updatedAt: 2026-06-12T17:49:15.000Z
agentTools:
  projectIndex: https://developers.rebrandly.com/llms.txt
---

# High-volume API link limitations

API fields that are silently dropped for high-volume API links, and sub-resource endpoints that return errors on high-volume API link IDs.

Links created via the high-volume API support a subset of features available to other Rebrandly links. Some API fields are accepted at creation with a `200 OK` response but are silently dropped at the persistence layer—the API gives no error, but the behavior has no effect.

This page documents confirmed limitations tested against the high-volume API (May 2026).

## Silently dropped fields

The following fields are accepted in the `POST` or `PUT /v1/links` body but have no effect on links created via the high-volume API:

| Field                                  | Behavior                                                                                                        |
| -------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| `tags`                                 | Accepted; silently dropped. No tag association is stored.                                                       |
| `password`                             | Accepted; resolver returns a clean `301` redirect with no password interstitial.                                |
| OpenGraph metadata (inline OG fields)  | Accepted; resolver returns a straight `301` with no OG customization.                                           |
| `description` and `title` (link notes) | Accepted; neither appears in the `GET` response. These are the link notes fields, not the link's display title. |

## Unsupported sub-resource endpoints

Per-link sub-resource endpoints return `404` or `500` for link IDs. These endpoints are gated by a workspace check that excludes links created via the high-volume API:

| Endpoint                       | Behavior on links |
| ------------------------------ | ----------------- |
| `GET /v1/links/{id}/rules`     | Returns `500`     |
| `GET /v1/links/{id}/apps`      | Returns `500`     |
| `GET /v1/links/{id}/scripts`   | `404` or `500`    |
| `GET /v1/links/{id}/opengraph` | `404` or `500`    |
| `GET /v1/links/{id}/tags`      | `404` or `500`    |

**Traffic routing rules** (`/rules`) and **mobile deep linking** (`/apps`) are not supported on links created via the high-volume API.

## What works at creation time

To attach metadata or behaviors to a link created via the high-volume API, use inline fields on `POST` or `PUT /v1/links` at creation time. Sub-resource management after creation is not available.

The following fields are reliably persisted at creation: `destination`, `slashtag`, `domain`, `ttl`, and `scripts`. Note that `expiresAt` is a response field returned after creation—pass `ttl` (in seconds) on the request to set expiration.

## Related pages

* [Creating links at scale for SMS and campaigns](https://developers.rebrandly.com/docs/high-volume-link-creation)—full high-volume API guide
* [High-volume API hosts and routing](https://developers.rebrandly.com/docs/high-volume-api-hosts)—dual-host behavior and WAF quirk
* [Troubleshooting](https://developers.rebrandly.com/docs/troubleshooting)—common errors