That’s right. Flairs are not currently in the api (edit: tags as well, see edit at bottom). The focus on the initial api implementation was to work with existing lemmy apps/frontends, so flair wasn’t prioritized (this is also why you don’t see feeds/topics in the api except for a couple undocumented endpoints). The other docs page that Blaze linked is an ongoing rewrite of parts of the api/documentation as part of making the api self-documenting.
Now that the first pass at the api is done, it would make sense to come back and add them…however, there are changes to flair that need to happen in the near future, so I think it makes sense to hold off on adding them to the api until those changes happen. I would also want to add possible flair to community endpoints as well so that apps know what flair a new post could have.
Edit: I read too quickly and mistook flairs for tags. Everything I wrote above is accurate for flairs and is similar for tags. Tags are not present in the api at the moment, but could be added without breaking anything. It is simply a matter of prioritization. My effort at the moment is focused on the aforementioned self-documentation overhaul of the api which is what app creators said would be the most helpful to them.
tl;dr - flairs are not in the api yet, but I hope they will be after some tweaks in preparation for lemmy 1.0, tags aren’t either, but could probably be added without breaking anything.
I just looked, according to the documentation, tags are not implemented in the API
That’s right. Flairs are not currently in the api (edit: tags as well, see edit at bottom). The focus on the initial api implementation was to work with existing lemmy apps/frontends, so flair wasn’t prioritized (this is also why you don’t see feeds/topics in the api except for a couple undocumented endpoints). The other docs page that Blaze linked is an ongoing rewrite of parts of the api/documentation as part of making the api self-documenting.
Now that the first pass at the api is done, it would make sense to come back and add them…however, there are changes to flair that need to happen in the near future, so I think it makes sense to hold off on adding them to the api until those changes happen. I would also want to add possible flair to community endpoints as well so that apps know what flair a new post could have.
Edit: I read too quickly and mistook flairs for tags. Everything I wrote above is accurate for flairs and is similar for tags. Tags are not present in the api at the moment, but could be added without breaking anything. It is simply a matter of prioritization. My effort at the moment is focused on the aforementioned self-documentation overhaul of the api which is what app creators said would be the most helpful to them.
Here is the more updated version of the API: https://crust.piefed.social/api/alpha/swagger (https://crust.piefed.social/api/alpha/swagger.json)
Not sure if tags are there, though
@Snoopy@jlai.lu, you may want to update the Wiki with those links
Is this the most up to date API ?
@wjs018@piefed.social can you confirm ?
Thanks, replied further up the chain.
tl;dr - flairs are not in the api yet, but I hope they will be after some tweaks in preparation for lemmy 1.0, tags aren’t either, but could probably be added without breaking anything.
"Post": { "type": "object", "properties": { "ap_id": { "type": "string", "format": "url" }, "community_id": { "type": "integer" }, "deleted": { "type": "boolean" }, "id": { "type": "integer" }, "language_id": { "type": "integer" }, "local": { "type": "boolean" }, "locked": { "type": "boolean" }, "nsfw": { "type": "boolean" }, "published": { "type": "string", "example": "2025-06-07T02:29:07.980084Z", "format": "datetime" }, "removed": { "type": "boolean" }, "sticky": { "type": "boolean" }, "title": { "type": "string" }, "user_id": { "type": "integer" }, "alt_text": { "type": "string" }, "body": { "type": "string", "format": "markdown" }, "small_thumbnail_url": { "type": "string", "format": "url" }, "thumbnail_url": { "type": "string", "format": "url" }, "updated": { "type": "string", "example": "2025-06-07T02:29:07.980084Z", "format": "datetime" }, "url": { "type": "string", "format": "url" } }, "required": [ "ap_id", "community_id", "deleted", "id", "language_id", "local", "locked", "nsfw", "published", "removed", "sticky", "title", "user_id" ] },If I’m reading this correctly, tags don’t seem to be there
Yes, I pinged Rimu and WSJ in another comment, let’s see what they say
FYI @rimu@piefed.social @wjs018@piefed.social