API archive entry · source-reported

Lanyard

Retrieve your presence on Discord through an HTTP REST API or WebSocket

Provider / source website

From the publisher

README & documentation

Source preview

Read the project’s overview, installation instructions and usage examples. The original README is the source of truth.

Lanyard is a service that makes it super easy to export your live Discord presence to an API endpoint (api.lanyard.rest/v1/users/:yourid) and to a WebSocket (see below) for you to use wherever you want - for example, I use this to display what I'm listening to on Spotify on my personal website. It also acts as a globally-accessible realtime KV store which you can update from the Lanyard Discord bot or from the Lanyard API. You can use Lanyard's API without deploying anything yourself - but if you want to self host it, you have the option to, though it'll require a tiny bit of configuration. Just join this Discord server and your presence will start showing up when you GET api.lanyard.rest/v1/users/:yourid. It's that easy. Many Lanyard users render their presence on websites. The recommended library for React is use-lanyard. It subscribes over the WebSocket, so presences update live, and any…

Phineas/lanyard on GitHub A short preview, not the full document.

Read the full README ↗ · Preview checked 2026-10-29T06:32:46.465Z

Inside the original README — Document outline
  1. 🏷️ Expose your Discord presence and activities to a RESTful API and WebSocket in less than 10 secon
  2. Get started in < 10 seconds
  3. Table of Contents
  4. In a React app
  5. Community Projects
  6. API Docs
  7. Getting a user's presence data
  8. KV
  9. Use cases
  10. Limits
  11. Getting an API Key
  12. Setting a key->value pair

Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.

Links from the README

References supplied by the publisher, not independently verified endorsements. Check the destination before downloading files or entering credentials.

Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.

Where these facts came from

AltAPIs imported it from public-apis/public-apis. The source link and dates remain visible for independent inspection.

What is reported

  • Name, category, and short description
  • Authentication label
  • HTTPS and CORS labels
  • Provider/source URL

What is not established

  • Current uptime or availability
  • Pricing, quotas, and rate limits
  • Security, compliance, or licensing posture
  • SDK quality or endpoint completeness

Record checkpoints

  1. First observed: Sep 14, 2026
  2. Last directory-field change: Sep 14, 2026
  3. Current source observation: Oct 30, 2026

Submit a source-backed correction

Source reference

public-apis/public-apis

This page separates source-reported facts from questions that need live provider verification.