Getting started

The RedirHub API

Everything RedirHub serves on the edge — redirects, short links, hostnames, and the workspace around them — is available over a JSON API. 31 operations across 21 paths, one bearer token, and predictable payloads.

Base URL: https://api.redirhub.com/v1
Auth: Bearer token
Format: JSON
Spec: OpenAPI 3.1.0

Your first call

Every endpoint lives under the same base URL and expects the same Authorization header. GET /test is the cheapest way to confirm a token works before you build anything on top of it.

# Verify your API token
curl "https://api.redirhub.com/v1/test" \
  -H "Authorization: Bearer $REDIRHUB_TOKEN"

Keep tokens server-side. A RedirHub token carries full workspace access. Call the API from your backend, never from a browser bundle.

How the API is shaped

Collection endpoints answer with a data array; single-record endpoints answer with the record itself. The same record shape comes back from create, read, and update, so one parser covers all three.

Records are redirects and short links — the things that resolve traffic.
Hostnames are the domains you have connected. A record always points at one.
Bulk operations move many records at once, with a preview step before anything is written.
Workspace and account endpoints cover members, subscriptions, and settings.

Reference groups

RedirectsCreate and manage URL redirects.7 operations Short LinksCreate and manage short links.7 operations Bulk OperationsImport, export, update, and delete redirects and short links in bulk.2 operations HostnamesConnect hostnames, manage their configuration, and select a routing cluster.6 operations WorkspaceWorkspace details and subscriptions.5 operations Account & ReferenceAccount settings plus shared reference and recommendation endpoints.4 operations

Where to go next

Start with Authentication to get a working token, then create something with POST /link. Errors, Pagination, Rate limits, and Filtering & sorting cover the things every integration hits next.