API Endpoint

[dshanske]

In #558, in order to accommodate a feature, an avatar API endpoint was added. I think having one of these is a good idea, but I wanted to discuss the design of this.

For one, we have 2 modes, with the store and without the store. So, how would the endpoint behave in that regard?

What functionality do we want in it?

• Delete
• Refresh
• Retrieve

It also goes to the broader question of whether we should have an API endpoint for webmention objects in general.

https://developer.wordpress.org/rest-api/reference/comments/

If you look at the abilities of the comment endpoint, it doesn't align with the webmention behavior, so I'm wondering if we should scope out what would be useful before building an endpoint specifically for avatars.

[dshanske]

@pfefferle Can you weigh in on this question? Would like to have a basic design we could extend on in mind before we add an endpoint we might want to change later.

[pfefferle]

I am not fully sure what issue it should solve and if that should be a public api or something like the parser in the tools section.

[dshanske]

I am not fully sure what issue it should solve and if that should be a public api or something like the parser in the tools section.

That is why I wanted to discuss it. The functionality proposed does not expressly require it