---
title: "Add To Linkedin"
method: GET
path: "/api/verified/{public_badge_id}/linkedin"
tags: ["verified"]
---

# Add To Linkedin

`GET /api/verified/{public_badge_id}/linkedin`

## Request

- Base URL: `https://api.ruzora.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.ruzora.com/api/verified/{public_badge_id}/linkedin`
- Auth: none declared

Tracked hop behind every "Add to LinkedIn" button (B4 FR-7).

Same 404 path as the JSON endpoint (no enumeration oracle). An archived
badge still redirects — the engineer may already have the cert, and the
verify page is what reports it as no longer valid. The click is counted
fire-and-forget; it never delays or blocks the 302.

`site` is the public origin the /verified page was served on (talent vs
developers); only allow-listed origins are honoured.

## Path parameters

- `public_badge_id` string, required

## Query parameters

- `src` string
- `site` string

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/ruzora/apis/ruzora-candidate-crm-api.md) · [All operations](https://skmtc.dev/ruzora/apis/ruzora-candidate-crm-api/llms.txt) · [OpenAPI document](https://skmtc.dev/ruzora/apis/ruzora-candidate-crm-api/revisions/f9b8223f3ac4?raw)