# "Recently joined" widget for WordPress (Illustrated Tutorial)

**URL:** <https://meta.discourse.org/t/recently-joined-widget-for-wordpress-illustrated-tutorial/31631>\
**Category:** Extras\
**Tags:** wordpress\
**Created:** [August 1, 2015, 4:27am UTC](https://meta.discourse.org/t/recently-joined-widget-for-wordpress-illustrated-tutorial/31631 "2015-08-01T04:27:28Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [August 4, 2015, 5:19pm UTC](https://meta.discourse.org/t/recently-joined-widget-for-wordpress-illustrated-tutorial/31631/10 "2015-08-04T17:19:35Z")

</div>

> [@AdamCapriola](#):
>
> I’m not 100% about this, but I think the user-specific API keys are meant for giving to developers to build apps around your forum and then having the power to revoke the keys if necessary.
> 
> So I guess if by “non-all-users API key” you mean an API key that works only in conjunction with a specific api\_username, I don’t think that exists. (@riking or anyone else knowledgeable, feel free to correct me.)

Nope, @meglio has the right idea here. Actually, for the per-user API keys, the `api_username` value is no longer needed (as it can be inferred from the key…).

User-accessible API keys are a wishlist item.

---

_[View the full topic](https://meta.discourse.org/t/recently-joined-widget-for-wordpress-illustrated-tutorial/31631)._