You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to see some sort of API documentation covering the various routes.
Additional context:
We over at https://github.com/catppuccin/userstyles are looking to potentially mirror our userstyles collection to userstyles.world - see catppuccin/userstyles#1392. Since much of our repository is automated through scripts, we would like to be able to manage creating userstyles, removing userstyles, listing userstyles, getting a userstyle, etc in order to keep the list of mirrored userstyles up to date with the contents of the repository.
The text was updated successfully, but these errors were encountered:
as of now, there are only user accounts and no API tokens, so you'll have to use a regular user account and auth via cookie. Which may or may not only last 91 days, I'm not sure if expiration is clientside-only.
there's a pull mirror feature for userstyles, it works well and eliminates the need to push style updates if you can tolerate a delay of 4 hours.
or you can trigger mirror on your style updates via a newer not-yet-documented endpoint: GET https://userstyles.world/mirror/<styleid>. It has a significant "rate limit" per-style though. So no frequent updates of the same style.
Describe the change you'd like:
I would like to see some sort of API documentation covering the various routes.
Additional context:
We over at https://github.com/catppuccin/userstyles are looking to potentially mirror our userstyles collection to userstyles.world - see catppuccin/userstyles#1392. Since much of our repository is automated through scripts, we would like to be able to manage creating userstyles, removing userstyles, listing userstyles, getting a userstyle, etc in order to keep the list of mirrored userstyles up to date with the contents of the repository.
The text was updated successfully, but these errors were encountered: