links.arjun.tv/docs/end-user/use-cases/uc-05-link-crud-redirect-behavior

UC-05: Link CRUD and Redirect Behavior

Role-gated control-plane steps are intentionally excluded from this public guide; use support escalation when those operations are required. Shared company context: Gharart.com Company Context Need operator help? Escalate through Troubleshooting and Support with request IDs and repro artifacts.

Developer Outcome

Ship link crud and redirect behavior for Gharart.com with reproducible API steps, operational limits, and clear debugging playbooks.

Prerequisites

  • A valid handle and environment access for Gharart.com.
  • JWT and/or PAT credentials with required scope for this use case.
  • Access to logs, support escalation endpoints, and test workspace.

Gharart Scenario

Flash-sale link launch and redirect assurance.

Persona: Performance marketer

Business goal: Create high-volume promotion links and guarantee predictable redirects during flash-sale traffic spikes.

Step-by-Step Flow (UI + API)

  1. Open the relevant Gharart workflow in the dashboard and confirm actor role access.
  2. Execute route calls in sequence for this use case and capture response IDs.
  3. Validate expected state in UI and API after each step before moving forward.
  4. Record artifacts (request ID, run ID, deployment ID, slug, or token) for support handoff.

Primary API Routes

MethodPath
ANY/v2/public/handles/{handle}/{proxy+}
DELETE/v2/handles/{handle}/links/{slug}
DELETE/v2/public/handles/{handle}/links/{slug}
GET/_edge/redirect/{handle}/{slug}
GET/v2/handles/{handle}/links
GET/v2/handles/{handle}/links/{slug}
GET/v2/handles/{handle}/links/{slug}/history
GET/v2/handles/{handle}/links/export
GET/v2/public/handles/{handle}/links
GET/v2/public/handles/{handle}/links/{slug}
POST/v2/handles/{handle}/links/{slug}/rollback
POST/v2/handles/{handle}/links/{slug}/route-preview

Limits and Quotas

  • Respect per-route throttles and daily write limits before bulk operations.
  • Use idempotency-safe retries for write endpoints to avoid duplicate business actions.
  • Schedule high-volume workflows outside peak campaign windows where possible.

Where This Breaks

  • 404 not_found on newly created slug from typo mismatch
  • invalid_destination_url during campaign import
  • edge redirect showing stale destination after rapid edits

How Gharart Debugs It

  1. Read link by slug and confirm destinationUrl is current
  2. Use route-preview and redirect probe in incognito mode
  3. Validate edge redirect path and handle casing

Escalation

Use end-user escalation path:

  • Submit POST /v2/support/report.
  • Include summary, details, and when available handle, sessionId, requestId, reproArtifact.

Audience boundaries:

  • POST /v2/operator/escalations is an internal operator workflow and not an end-user escalation action.
  • POST /v2/public/content-report is for public abuse moderation reports, not product incident escalation.