# linkedin_resolve_url - Veezee docs

Identify what a LinkedIn URL points at before fetching it. Give any LinkedIn profile, company, or post URL (utm params, www/m subdomains, trailing slashes are fine); get back {type: person|company|post, id, handle, canonical_url}. For profile URLs, id is the stable person URN; for company URLs, id is the stable company URN; for post URLs, id is the activity URN extracted from the URL. For people, use the returned handle or id with linkedin_get_profile or linkedin_get_posts. For companies, use the returned HANDLE with linkedin_get_company or linkedin_get_posts; the company URN/id is a linkedin_search_people filter input, not a fetch identifier. Costs 2 credits. Skip this tool when you already have a slug, URN, or clean URL: linkedin_get_profile and linkedin_get_company accept those directly, so resolving first would waste 2 credits. Not for non-LinkedIn URLs; it returns INVALID_INPUT for those.

## Parameters

| Param | Required | Type | Description |
| --- | --- | --- | --- |
| `url` | yes | `string` | A LinkedIn URL, e.g. https://www.linkedin.com/in/williamhgates or .../company/microsoft. |

## REST

`GET /v1/linkedin/resolve-url` (auth: `required`, metered: `true`)

```
curl "https://api.veezee.io/v1/linkedin/resolve-url?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fwilliamhgates%3Futm_source%3Dshare" \
  -H "Authorization: Bearer $VEEZEE_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"
```

## MCP

```json
{
  "method": "tools/call",
  "params": {
    "name": "linkedin_resolve_url",
    "arguments": {
      "url": "https://www.linkedin.com/in/williamhgates?utm_source=share"
    }
  }
}
```

## Input examples

**Profile URL from a user message**

```json
{
  "url": "https://www.linkedin.com/in/williamhgates?utm_source=share"
}
```

**Company URL**

```json
{
  "url": "https://linkedin.com/company/anthropicresearch"
}
```

## Output

Returns a `url_resolution` envelope. Full field list: https://veezee.io/docs/fields#url_resolution

## Errors

REST returns `application/problem+json`; MCP returns the same content as an error result. `message` is written as the next-turn instruction.

| Code | HTTP status | Retriable | Meaning |
| --- | --- | --- | --- |
| `INVALID_INPUT` | 400 | no | A parameter failed validation. Check param and message for what to fix. |
| `NOT_FOUND` | 404 | no | Nothing matches the given identifier or URL. |
| `UNAUTHORIZED` | 401 | no | Missing, invalid, or revoked API key. |
| `NOT_ENTITLED` | 403 | no | This account is not enabled for the platform you called. |
| `INSUFFICIENT_CREDITS` | 402 | no | Your balance can't cover this call's quote. Check get_usage or add credits. |
| `QUOTE_EXCEEDS_MAX_CREDITS` | 402 | no | The call's quote is higher than the max_credits you set. Nothing was charged. |
| `IDEMPOTENCY_KEY_REQUIRED` | 400 | no | This is a metered call; send an Idempotency-Key header. |
| `IDEMPOTENCY_KEY_REUSED` | 409 | no | That Idempotency-Key was already used with different arguments. Use a new key for a new call. |
| `CONCURRENCY_LIMIT` | 429 | yes | Too many calls in flight for this key's plan. Wait for one to finish. |
| `RATE_LIMITED` | 429 | yes | Too many calls per minute for this key's plan. Back off and retry. |
| `TRIAL_CAP_EXCEEDED` | 403 | no | A trial-only limit was hit (concurrency, rate, search size, or realtime fetches). |
| `BUDGET_EXHAUSTED` | 503 | no | A configured spend budget has been used up. |
| `UPSTREAM_UNAVAILABLE` | 502 | yes | LinkedIn data wasn't reachable. Safe to retry. |
| `PAYLOAD_TOO_LARGE` | 413 | no | The request or response exceeded the size limit. |
| `INTERNAL` | 500 | yes | Something failed on our side. Safe to retry. |

Errors a payment can fix add fields to this shape. INSUFFICIENT_CREDITS, TRIAL_CAP_EXCEEDED, and BUDGET_EXHAUSTED carry `upgrade_url` (give it to your human) and `offer`, its machine-readable twin; RATE_LIMITED and CONCURRENCY_LIMIT carry both on trial accounts only, where a paid plan raises the limit. `offer` holds `offer_version` (1), `reason` (the error code), `currency` ("usd"), `recommended` (which pack to lead with, currently `flex`), `packs` (pack, mode, price_usd_cents, credits or credits_per_month, and `when`, a short label for when that pack fits), `rails` (currently `stripe_checkout`), `checkout_url` (the same account-bound link as `upgrade_url`), `resume`, and `refund_policy`. Follow `offer.resume` after payment: INSUFFICIENT_CREDITS retries the same call with the SAME Idempotency-Key; TRIAL_CAP_EXCEEDED and BUDGET_EXHAUSTED retry with a fresh key; the two limit codes clear on their own with back-off, payment only raises the limit. INSUFFICIENT_CREDITS also sets `credits_required`: the credits the failed call needed. The failed attempt charged nothing.