Validation model

{
  "message": "The given data was invalid.",
  "errors": {
    "reference": ["The reference format is invalid."],
    "link": ["The link field must be a valid URL."]
  }
}

Do not parse the human message to identify a field. Use the keys of errors; display every string in the corresponding array.

Status codes

• 200: successful read or availability result
• 201: resource created
• 204: deletion on supported administrative routes
• 401: credential missing or invalid
• 403: feature or operation not permitted
• 409: hostname or reference conflict
• 422: validation, quota, or domain-ownership failure
• 429: rate limit
• 502/503: upstream or configured service unavailable
• 500: unexpected server error

Limits

Plans control link quotas, custom aliases, campaign parameters, managed hosts, custom domains, and related capabilities. Anonymous creation also has platform-configured maximum links, expiration, and claim behavior.

Retry policy

• Do not retry 401, 403, 409, or 422 without changing the request.
• For 429, honor Retry-After when present.
• Retry 502, 503, and transient network failures with bounded exponential backoff and jitter.
• Use an idempotency strategy in the caller before retrying creation after an unknown network outcome.

Forward compatibility

Response objects may gain fields. Clients and agents should ignore unknown properties and must not rely on JSON property order.