verified

Add To Linkedin

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.

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

Path parameters

public_badge_idstring required

Query parameters

srcstring
sitestring

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 1 revision of this API.