Assign and list group AI agent assignments
Wellesley Platform API (1.0)
Download OpenAPI description
Languages
Servers
Mock server
https://docs.wellesley.social/_mock/openapi/
Simple setup, all in one. Digital Ocean
https://dust.allroads.social/
Simple setup, db is separate. Digital Ocean
https://meteor.allroads.social/
- Mock serverhttps://docs.wellesley.social/_mock/openapi/api/v1/admin/change/password
- Simple setup, all in one. Digital Oceanhttps://dust.allroads.social/api/v1/admin/change/password
- Simple setup, db is separate. Digital Oceanhttps://meteor.allroads.social/api/v1/admin/change/password
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
'https://docs.wellesley.social/_mock/openapi/api/v1/admin/change/password?id=us_01hxcvk1hjexere4pvtrj0ymqq&password=string&username=string'Query
User ID to assign the role to. Must be a valid USER type ID. Either username or id must be provided.
Example: id=us_01hxcvk1hjexere4pvtrj0ymqq
Role ID to assign in format 'Scope:RoleName' (e.g., 'System:ADMIN', 'Group:MODERATOR'). Must be a valid role.
Example: role=
'admin',
'System:admin',
'rr_01hxcvk1hjexere4pvtrj0ymqq',
'System:rr_01hxcvk1hjexere4pvtrj0ymqq',
'gr_1lkjvfdoibb126576:rr_01hxcvk1hjexere4pvtrj0ymqq',
Username of the user to assign the role to. Case-insensitive. Either username or id must be provided.
- Mock serverhttps://docs.wellesley.social/_mock/openapi/api/v1/admin/change/role/assign
- Simple setup, all in one. Digital Oceanhttps://dust.allroads.social/api/v1/admin/change/role/assign
- Simple setup, db is separate. Digital Oceanhttps://meteor.allroads.social/api/v1/admin/change/role/assign
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
'https://docs.wellesley.social/_mock/openapi/api/v1/admin/change/role/assign?id=us_01hxcvk1hjexere4pvtrj0ymqq&role=%0A++++++++%27admin%27%2C%0A++++++++%27System%3Aadmin%27%2C%0A++++++++%27rr_01hxcvk1hjexere4pvtrj0ymqq%27%2C%0A++++++++%27System%3Arr_01hxcvk1hjexere4pvtrj0ymqq%27%2C%0A++++++++%27gr_1lkjvfdoibb126576%3Arr_01hxcvk1hjexere4pvtrj0ymqq%27%2C%0A++++&username=string'OK
Account details including email, login type, and creation date
Non-empty list of users associated with this account. Most accounts have one user, but multiple users are supported.
User's summary or bio
Example: "Pixels are my paint, code is my canvas, creativity is my brush."
User stats
users[].​stats.​followingHiddenbooleanrequired
privacy setting to hide followings
User fields
Registration mode:
- REGULAR - just regular state
- SENSITIVE - all media attachments are flagged as sensitive, i.e. all user's posts should be marked as sensitive, old posts and all future ones.
- LIMITED - all user's old and future posts should be set maximum to followers only unless user set it to direct himself. non-followers should not be notified, i.e. if user mentions non-follower we do not create notification.
- SUSPENDED - User can login, but cannot do anything in his account except to read, cannot change anything, cannot create new posts or comments etc. All his posts are marked as deleted, but we do not delete them just yet. User is scheduled to be deleted in one month. During this month it is possible to restore it via admin.
Enum"REGULAR""SENSITIVE""LIMITED""SUSPENDED"
Software platform type (wellesley, mastodon, threads.net)
Example: "wellesley"
- PUBLIC - Channel is visible to everyone and can be followed by anyone.
- PRIVATE - Channel is visible only to group members and can only be followed by group members.
Enum"PUBLIC""PRIVATE"
Types that an Actor can be assigned. Coincide with ActivityPub Actor types:
- APPLICATION: Apps will have this type
- GROUP: Interest Groups and Generic Groups wil have this type
- ORGANIZATION: Formal Organizations such as Companies, Institutions, etc. will have this type
- PERSON: Individual people will have this type
- SERVICE: Bots, Services, and other automated tools which are not also Apps will have this type
Enum"Application""Group""Organization""Person""Service"
Response
application/json
{ "account": { "id": "act_ytweuysdjfhguyt", "email": "john@example.com", "password": "string", "phone": "+12345678901", "createdAt": "2022-03-10T16:15:50Z", "updatedAt": "2022-03-10T16:15:50Z" }, "users": [ { … } ], "selectedUserId": "usr_kjhauygmxcvkhwe" }
Query
User ID to revoke the role from. Must be a valid USER type ID. Either username or id must be provided.
Example: id=us_01hxcvk1hjexere4pvtrj0ymqq
Role ID to revoke in format 'Scope:RoleName'. Must currently be assigned to the user.
Example: role=
'admin',
'System:admin',
'rr_01hxcvk1hjexere4pvtrj0ymqq',
'System:rr_01hxcvk1hjexere4pvtrj0ymqq',
'gr_1lkjvfdoibb126576:rr_01hxcvk1hjexere4pvtrj0ymqq',
Username of the user to revoke the role from. Case-insensitive. Either username or id must be provided.
- Mock serverhttps://docs.wellesley.social/_mock/openapi/api/v1/admin/change/role/revoke
- Simple setup, all in one. Digital Oceanhttps://dust.allroads.social/api/v1/admin/change/role/revoke
- Simple setup, db is separate. Digital Oceanhttps://meteor.allroads.social/api/v1/admin/change/role/revoke
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
'https://docs.wellesley.social/_mock/openapi/api/v1/admin/change/role/revoke?id=us_01hxcvk1hjexere4pvtrj0ymqq&role=%0A++++++++%27admin%27%2C%0A++++++++%27System%3Aadmin%27%2C%0A++++++++%27rr_01hxcvk1hjexere4pvtrj0ymqq%27%2C%0A++++++++%27System%3Arr_01hxcvk1hjexere4pvtrj0ymqq%27%2C%0A++++++++%27gr_1lkjvfdoibb126576%3Arr_01hxcvk1hjexere4pvtrj0ymqq%27%2C%0A++++&username=string'OK
Account details including email, login type, and creation date
Non-empty list of users associated with this account. Most accounts have one user, but multiple users are supported.
User's summary or bio
Example: "Pixels are my paint, code is my canvas, creativity is my brush."
User stats
users[].​stats.​followingHiddenbooleanrequired
privacy setting to hide followings
User fields
Registration mode:
- REGULAR - just regular state
- SENSITIVE - all media attachments are flagged as sensitive, i.e. all user's posts should be marked as sensitive, old posts and all future ones.
- LIMITED - all user's old and future posts should be set maximum to followers only unless user set it to direct himself. non-followers should not be notified, i.e. if user mentions non-follower we do not create notification.
- SUSPENDED - User can login, but cannot do anything in his account except to read, cannot change anything, cannot create new posts or comments etc. All his posts are marked as deleted, but we do not delete them just yet. User is scheduled to be deleted in one month. During this month it is possible to restore it via admin.
Enum"REGULAR""SENSITIVE""LIMITED""SUSPENDED"
Software platform type (wellesley, mastodon, threads.net)
Example: "wellesley"
- PUBLIC - Channel is visible to everyone and can be followed by anyone.
- PRIVATE - Channel is visible only to group members and can only be followed by group members.
Enum"PUBLIC""PRIVATE"
Types that an Actor can be assigned. Coincide with ActivityPub Actor types:
- APPLICATION: Apps will have this type
- GROUP: Interest Groups and Generic Groups wil have this type
- ORGANIZATION: Formal Organizations such as Companies, Institutions, etc. will have this type
- PERSON: Individual people will have this type
- SERVICE: Bots, Services, and other automated tools which are not also Apps will have this type
Enum"Application""Group""Organization""Person""Service"
Response
application/json
{ "account": { "id": "act_ytweuysdjfhguyt", "email": "john@example.com", "password": "string", "phone": "+12345678901", "createdAt": "2022-03-10T16:15:50Z", "updatedAt": "2022-03-10T16:15:50Z" }, "users": [ { … } ], "selectedUserId": "usr_kjhauygmxcvkhwe" }
Admin Domain Blocks
Administrative APIs for managing domain blocks. Provides endpoints to block specific domains with different severity levels (SUSPEND, LIMIT, NOOP), update existing blocks, unblock domains, and list currently blocked domains. Domain blocks prevent or limit federation with specified domains.
Operations
Group Channels
API endpoints for managing channels within groups. Channels are specialized accounts that enable organized content distribution within groups. They support hierarchical organization with main and default channels, privacy controls inherited from parent groups, and both scoped (group-specific) and global usernames for discovery. Group administrators manage channels while members can follow them.
Operations
Group Members
API endpoints for managing group membership. Provides functionality to add, update, and remove members from groups, as well as retrieve membership information. Supports both local and federated groups through ActivityPub protocol. Access control is enforced based on group privacy settings and user permissions.
Operations
Group Questions
API endpoints for managing group entry questions. Groups can require prospective members to answer questions before joining. Questions support multiple types (text, single choice, multiple choice) and are used to screen members when the group's join mode is set to QUESTIONS. Answers are validated and generate a token that can be used during the join process.
Operations
Group Rules
API endpoints for managing community rules within groups. Rules define the expected conduct and content policies that members must follow. Each rule consists of text (the rule itself), a hint (explanation or context), and an ordering value for display sequence. Rules are scoped to specific groups and can be managed by users with appropriate permissions.
Operations
Platform Data
Endpoints for managing platform-wide and group-specific data storage. Unlike application data, this provides direct data management not tied to specific applications. Supports flexible ownership models including platform-level, group-level, and user-level data with appropriate access controls.
Operations
RBAC
Endpoints for retrieving Role-Based Access Control (RBAC) configurations and managing roles, resources, permissions and role-to-user assignments. Scoped Role Definition (RBACRole):
- Represents roles within the RBAC system.
- Each role has a unique
roleId, aname, an optionaldescription, and ascope. - The
scopedefines the domain or area in which the role is valid. - The
scopecan be Global (hardcoded), currently the only one is "System" - The
scopealso can be dynamic, currently we use Group Ids, like "gr_05hxcvk1hjexere4pvtrj0hggt" - Roles come with assigned permissions (
RBACPermissions) that define what actions the role can perform on system resources. - Metadata such as
createdAtandupdatedAttimestamps track the role's lifecycle events.
Permissions** (RBACPermissions):
- Encapsulates resource-specific access controls.
- Each permission object specifies the
resource(e.g., "user", "document") and an associated list of allowedRBACAccesstypes. RBACAccessenumerates the supported actions:Read,Add,Modify,Delete.
Role Assignments to Actors (RBACActorRole):
- Maps actors (e.g., users, services) to specific roles.
- Tracks the association through
actorId(representing the unique entity being assigned) androleId(specific role ID). - Includes timestamps to record when the assignment was created or updated.
Operations