# The ActivityPub Client API

**URL:** <https://socialhub.activitypub.rocks/t/the-activitypub-client-api/3186>\
**Category:** Client to Server\
**Created:** [May 6, 2023, 7:44am UTC](https://socialhub.activitypub.rocks/t/the-activitypub-client-api/3186 "2023-05-06T07:44:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![helge](https://socialhub.activitypub.rocks/user_avatar/socialhub.activitypub.rocks/helge/32/1938_2.png) [@helge](https://socialhub.activitypub.rocks/u/helge)\
**Post date:** [May 6, 2023, 7:44am UTC](https://socialhub.activitypub.rocks/t/the-activitypub-client-api/3186/1 "2023-05-06T07:44:06Z")

</div>

As [FEP-proposal C2S: websocket endpoint](https://socialhub.activitypub.rocks/t/fep-proposal-c2s-websocket-endpoint/2955) is being used for more technical discussions on particular implementation choices, that I’ve already made my mind up on. I’m posting this in a linked topic.

I’ve split away [ActivityPub Client API](https://codeberg.org/helge/fep/src/commit/c0bacddb0c4677467e222e170b72f4737dc47f4d/feps/fep-xxx1.md) from my notes on how to improve client to server. The main point being: This will be the only important part a lot of developers. There will be some technical magic to get to this API from an ActivityPub server, but once it is implemented one no longer needs to worry about the details.
