Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Avendaosander/Plataforma-social/llms.txt
Use this file to discover all available pages before exploring further.
Plataforma Social provides three mutations for managing user accounts. postUser registers a new user and provisions their default settings; putUser updates one or more profile fields; and deleteUser permanently removes a user along with every piece of data associated with them. All mutations are sent as POST requests to /graphql — see the API Overview for request formatting details.
postUser
postUser(username: String!, email: String!, password: String!): User
Setting record for them so that their notification and privacy preferences are available immediately.
Parameters:
The desired display name for the new account. Must be unique across all users — the resolver checks for conflicts before writing.
The email address for the new account. Must be unique across all users — the resolver checks for conflicts before writing.
The plain-text password chosen by the user. It is hashed with bcrypt (10 salt rounds) before being stored; the raw value is never persisted.
User
Errors:
| Condition | Message |
|---|
username is already taken | Nombre de usuario ya esta en uso |
email is already registered | El correo ya esta en uso |
Example
mutation PostUser($username: String!, $email: String!, $password: String!) {
postUser(username: $username, email: $email, password: $password) {
id
username
email
description
avatar
}
}
{
"username": "johndoe",
"email": "john@example.com",
"password": "securepassword123"
}
{
"data": {
"postUser": {
"id": "new-uuid-here",
"username": "johndoe",
"email": "john@example.com",
"description": null,
"avatar": null
}
}
}
After a successful postUser, a Setting row is automatically created for the new user with all notification flags set to their defaults. There is no need to create settings separately.
putUser
putUser(id: String!, username: String, description: String, avatar: String): User
id is required; all other fields are optional and will be updated only when supplied. Fields not included in the call are left unchanged.
Parameters:
The UUID of the user to update.
A new display name for the user. When provided, uniqueness is enforced — the resolver will reject the update if the username is already held by another account.
A short profile bio or description. Pass an empty string to clear the existing value.
A URL pointing to the user’s profile image. Must be a fully qualified URL string (e.g. https://cdn.example.com/avatars/johndoe.png).
User — the full user record after applying the update.
Errors:
| Condition | Message |
|---|
username is already taken by another user | Nombre de usuario ya esta en uso |
Example
mutation PutUser(
$putUserId: String!
$username: String
$description: String
$avatar: String
) {
putUser(
id: $putUserId
username: $username
description: $description
avatar: $avatar
) {
id
username
email
description
avatar
}
}
{
"putUserId": "uuid-here",
"username": "johndoe_updated",
"description": "Full-stack developer and open source contributor",
"avatar": "https://cdn.example.com/avatars/johndoe.png"
}
{
"data": {
"putUser": {
"id": "uuid-here",
"username": "johndoe_updated",
"email": "john@example.com",
"description": "Full-stack developer and open source contributor",
"avatar": "https://cdn.example.com/avatars/johndoe.png"
}
}
}
deleteUser
deleteUser(id: String!): ResponseID
This operation is irreversible. All content created by the user — posts, comments, ratings, and settings — will be permanently deleted along with the account. There is no soft-delete or recovery mechanism.
The UUID of the user to delete.
ResponseID
The UUID of the user that was deleted. Useful for confirming which record was removed or for updating client-side caches.
Example
mutation DeleteUser($id: String!) {
deleteUser(id: $id) {
id
}
}
{
"data": {
"deleteUser": {
"id": "uuid-here"
}
}
}