Texau logo

Find URL Redirect Destination (Utility)

Texau → Find URL Redirect Destination (Utility)

POST/v1/texau-find-redirect-page
texau__texau-find-redirect-pageenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/texau-find-redirect-page
{
  "url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "final_status_code": "valid",
    "is_redirected": true,
    "original_link": "sample",
    "redirect_count": 1,
    "redirect_link": "sample",
    "resolved_successfully": true
  }
}

Resolves a URL to its final destination and returns the full redirect chain with HTTP status codes.

Install

Add find url redirect destination (utility) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__texau-find-redirect-page

When to use this.

The "Find Redirect Page" action, identified as texau-find-redirect-page, is designed to resolve a given URL and determine its final destination, along with the redirect chain and HTTP status. This action requires a single input parameter, the original URL (text), which is the starting point for the resolution process. Upon execution, it outputs several key fields, including the final status code (number), a boolean indicating whether the URL was redirected (is_redirected), the original link (url), the total count of redirects encountered (redirect_count), the final redirect link (url), and a boolean indicating if the resolution was successful (resolved_successfully). This action is particularly useful in web scraping, SEO analysis, and link validation, making it an essential tool in the enrichment category for developers and digital marketers seeking to optimize their online presence and ensure accurate URL navigation.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Find URL Redirect Destination (Utility)

Try it

The original URL to resolve and check for redirects.

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • final_status_code
    Final Status Code
    nullablenumber
  • is_redirected
    Is Redirected
    nullableboolean
  • original_link
    Original Link
    nullabletext
  • redirect_count
    Redirect Count
    number
  • redirect_link
    Redirect Link
    nullabletext
  • resolved_successfully
    Resolved Successfully
    nullableboolean

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/texau-find-redirect-page. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/texau-find-redirect-page
curl -X POST 'https://v3-api.texau.com/api/v1/texau-find-redirect-page' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"url":"https://acme.com"}'
200 Accepted
{
  "ok": true,
  "data": {
    "final_status_code": "valid",
    "is_redirected": true,
    "original_link": "sample",
    "redirect_count": 1,
    "redirect_link": "sample",
    "resolved_successfully": true
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Find URL Redirect Destination (Utility)→Remove Extra Whitespace (Utility)→Identify Email Type (Utility)

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → find url redirect destination (utility) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Find URL Redirect Destination (Utility)Texau action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit300 / min
  • Per-day limit10,000 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Light tier

Pricing tier on /pricing. Per-action credit cost is private.

Related

More Texau actions.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__texau-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Find URL Redirect Destination (Utility) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs