User Management
Overview and use cases
Full lifecycle management of users in a project (administrator view): create / query / update / disable / delete users, manage login identities, sessions, MFA factors, push targets and labels, and issue short-lived tokens for Custom Token login. Use cases: backend account operations, automated onboarding, Custom Token issuance, session governance.
Prerequisites
Server API Key:
users.read/users.write(session-related operations additionally require the sessions scope).The administrator view has a different boundary from the user's "self-service" account surface (profile.md): here you operate on any project user.
Usage workflow
Create user:
users.create({ userId, email, phone, password, name })(email,phone,password,nameall optional) (password at least 8 characters;ID.unique()or a custom ID); for migrating accounts with pre-hashed passwords usecreateArgon2User/createBcryptUser/createMD5User/createPHPassUser.Query:
users.list({ queries, search, total })(queries,search,totalall optional) (supports keyword search and pagination);users.get(userId)for a single lookup.Update:
updateEmail/updatePassword/updatePhone/updateName/updatePrefs; status and verification:updateStatus(disable / enable),updateEmailVerification/updatePhoneVerification.Identities and labels:
listIdentitiesto view bound OAuth / external identities,deleteIdentityto unlink; labels are used for label-based role authorization (Role.label) and are maintained via the management plane.Session governance:
listSessions/createSession/deleteSession/deleteSessions. For sessions created server-side, the secret is not in the response body and only lands in thea_session_<projectId>Cookie; when a user-state client is needed, read that Cookie and thenClient().setSession(secret).Custom Token issuance: after the business backend completes external identity verification, call
users.createToken({ userId })and hand the one-timesecretto the frontendaccount.createSession({ userId, secret })to exchange for a full Session (see the flow in authentication.md).User JWT:
users.createJWTissues short-lived JWTs for users (server-side orchestration scenarios).MFA management:
listMfaFactors/deleteMfaAuthenticator/createMfaRecoveryCodes/getMfaRecoveryCodes/updateMfaRecoveryCodes— administrators reset authenticators / recovery codes on behalf of users.Push targets:
createTarget/listTargets/getTarget/updateTarget/deleteTarget(used with Messaging's user-targeted delivery).Audit:
listLogsfor user-level operation logs;listMembershipsfor the teams this user has joined.
Key parameters and returns
| Call | Key parameters | Returns |
|---|---|---|
create | userId, email (optional), phone (optional), password (optional), name (optional) | Models.User ($id, email, labels, status…) |
list | queries (optional; Query.limit/offset/orderDesc etc.), search (optional), total (optional) | UserList (users + total) |
createToken | userId | Token (one-time secret, short-lived) |
createSession | userId | Session (secret only in the Cookie) |
createJWT | userId | { jwt } |
updatePrefs | userId, prefs object | User |
On the Java side, typed models are returned synchronously; in-row business data defaults to Map<String,Object>, and Type can be passed to deserialize into POJOs; on the Python side, the methods are snake_case isomorphs.
Errors and boundaries
409:
userId/email/phonealready exists; 400: password policy not satisfied.The
users.createTokenofsecretappears only once and is short-lived; transmit it over a controlled channel and never write it to logs.Disabling via
updateStatusimmediately blocks the user's sessions; deleting a user is irreversible (cleanup of associated data is handled by the platform deletion policy).After creating a session for a user server-side, the secret is not obtainable (it is only in the Cookie); do not attempt to parse it from the response body.
Users are globally unique per project; users with the same name across projects are different entities.
SDK Category Differences
Server SDK: the main body of this page (full lifecycle + Custom Token / JWT issuance).
Client SDK: no user management capabilities (cannot list users / modify others); account self-service operations go through profile.md.
Console SDK: does not handle project user management; for accounts / members from the Console view, see organization.md.
Difference entry points: server-sdk/nodejs.md, client-sdk/web.md.
Examples by language
The following provides examples by language, item by item along the usage workflow; each card can switch languages (synced across the page).
Create and query
This page has no Web / Console tabs: Client SDK has no user management capabilities (cannot list users / modify others); account self-service operations are covered in profile.md; Console SDK likewise does not handle project user management. This card covers both creation (including pre-hashed password migration import) and querying.
- Node.js (Server)
- Java
- Python
- Go
- REST (curl)
import { Client, Users, ID, Query } from 'agentbase-node-sdk';
const client = new Client()
.setEndpoint(process.env.APPBASE_ENDPOINT!) // Must include /v1
.setProject(process.env.APPBASE_PROJECT_ID!)
.setKey(process.env.APPBASE_API_KEY!); // users.read / users.write minimum scope
const users = new Users(client);
const user = await users.create({
userId: ID.unique(), // or custom ID; duplicate email/phone/userId returns 409
email: 'user@example.com',
password: '<password>', // Plaintext, at least 8 characters; hashed server-side
name: 'Example User',
});
const page = await users.list({ queries: [Query.limit(25)], search: 'user@example.com' });
const one = await users.get('<userId>');
// Pre-hashed password migration import: createArgon2User / createBcryptUser / createMD5User / createPHPassUser (pass the source system's hash string, the server does not re-hash)import io.agentbase.ID;
import io.agentbase.Query;
import io.agentbase.services.Users;
Users users = new Users(client); // For client initialization, see server-sdk/java.md
var user = users.create(
ID.unique(), // userId: or a custom ID; duplicate email/phone/userId returns 409
"user@example.com", // email
null, // phone
"<password>", // password: plaintext, at least 8 characters; hashed on the server side
"Example User" // name
);
var page = users.list(List.of(Query.limit(25)), "user@example.com", null); // queries / search / total
var one = users.get("<userId>");
// Pre-hashed password migration import (positional arguments userId / email / password / name; pass the source system's hash string, the server does not re-hash):
var migrated = users.createArgon2User("migrated-1", "legacy@example.com", "<argon2-hash>", "Legacy User");
// createBcryptUser / createMD5User / createPHPassUser are isomorphic (/users/bcrypt, /md5, /phpass)from agentbase.id import ID
from agentbase.query import Query
from agentbase.services.users import Users
users = Users(client) # Synchronous call, returns a pydantic model
created = users.create(
user_id=ID.unique(), # Or a custom ID; duplicate email/phone/user_id returns 409
email='user@example.com',
password='<password>', name='Example User')
page = users.list(queries=[Query.limit(25)], search='user@example.com')
one = users.get(user_id='<user_id>')
# Pre-hashed password migration import (pass the source system hash string; the server does not hash again):
migrated = users.create_argon2_user(
user_id='migrated-1', email='legacy@example.com',
password='<argon2-hash>', name='Legacy User')
# create_bcrypt_user / create_md5_user / create_ph_pass_user are isomorphic (note the ph_pass spelling)users := agentbase.NewUsers(cl) // facade constructor; cl is a Client already loaded with an API Key
created, err := users.Create(id.Unique(),
users.WithCreateEmail("user@example.com"),
users.WithCreatePassword("<password>"),
users.WithCreateName("Example User"))
_ = created
page, err := users.List( // Optional parameters follow the With<方法名><参数名> pattern
users.WithListQueries([]string{query.Limit(25)}),
users.WithListSearch("user@example.com"))
one, err := users.Get("user-123")
migrated, err := users.CreateArgon2User("migrated-1", "legacy@example.com",
"<argon2-hash>", users.WithCreateArgon2UserName("Legacy User")) // Pass the source system's hash string; the server does not hash again
_, _ = page, one, migrated
// CreateBcryptUser / CreateMD5User / CreatePHPassUser are isomorphic (UserId / Email / Password positional args + Name option)curl -sS -X POST "$APPBASE_ENDPOINT/users" \
-H 'Content-Type: application/json' \
-H "X-Appwrite-Project: $APPBASE_PROJECT_ID" \
-H "X-Appwrite-Key: $APPBASE_API_KEY" \
-d '{"userId":"user-123","email":"user@example.com","password":"<password>","name":"Example User"}'
# Returns 201; returns 409 user_already_exists if the email/phone/userId already exists
# List (supports search fuzzy search, total=false to skip counting):
curl -sS "$APPBASE_ENDPOINT/users?queries[]=limit(25)&search=user@example.com&total=false" \
-H "X-Appwrite-Project: $APPBASE_PROJECT_ID" -H "X-Appwrite-Key: $APPBASE_API_KEY"Update, ban and delete
updateStatus bans (false) take effect immediately; updatePrefs merges and writes preferences; updateEmail does not automatically rewrite the email verification state. Deleting a user is irreversible: it cascades to delete all of their Sessions, OAuth identities, message targets and team memberships, and the ID can be reused after deletion.
- Node.js (Server)
- Java
- Python
- Go
- REST (curl)
await users.updateEmail({ userId: '<userId>', email: 'new@example.com' });
await users.updateStatus({ userId: '<userId>', status: false }); // Block; true re-enables
await users.updatePrefs({ userId: '<userId>', prefs: { theme: 'dark' } });
await users.delete({ userId: '<userId>' }); // Irreversible; cascades to delete Sessions, identities, targets, and team membershipsusers.updateEmail("<userId>", "new@example.com"); // Does not automatically alter the email verification state
users.updateStatus("<userId>", false); // Block; true re-enables, effective immediately
users.updatePrefs("<userId>", Map.of("theme", "dark")); // Merge-write preferences
users.delete("<userId>"); // Irreversible; cascades to delete Sessions, identities, targets, and team membershipsusers.update_email(user_id='<user_id>', email='new@example.com') # Does not automatically alter the email verification state
users.update_status(user_id='<user_id>', status=False) # Ban; True re-enables
users.update_prefs(user_id='<user_id>', prefs={'theme': 'dark'}) # Merge-write preferences
users.delete(user_id='<user_id>') # Irreversible; cascades to delete Sessions, identities, targets, and team memberships_, err = users.UpdateEmail("user-123", "new@example.com") // Does not automatically alter the email verification state
_, err = users.UpdateStatus("user-123", false) // Block; true re-enables
_, err = users.UpdatePrefs("user-123",
map[string]interface{}{"theme": "dark"}) // Merge-write preferences
_, err = users.Delete("user-123") // Irreversible; cascades to delete Sessions, identities, targets, and team membershipscurl -sS -X PATCH "$APPBASE_ENDPOINT/users/user-123/email" \
-H 'Content-Type: application/json' \
-H "X-Appwrite-Project: $APPBASE_PROJECT_ID" \
-H "X-Appwrite-Key: $APPBASE_API_KEY" \
-d '{"email":"new@example.com"}'
# Ban/enable: PATCH /users/{userId}/status, body {"status": false} (ban takes effect immediately)
# Preferences: PATCH /users/{userId}/prefs; body is a key-value object merged into the write
# Password: PATCH /users/{userId}/password; phone: PATCH /users/{userId}/phone; name: PATCH /users/{userId}/name
# Verification state (does not send verification email/SMS): PATCH /users/{userId}/verification, PATCH /users/{userId}/verification/phone
# Delete user: DELETE /users/{userId} (cascades to sessions, identities, targets and memberships; IDs may be reused after deletion)Custom Token and JWT issuance
createToken issues a one-time, short-lived secret for users (by default 6 characters and 900 seconds, in OTP form); the frontend exchanges it via account.createSession({ userId, secret }) for a full Session; createJWT issues short-lived JWTs for existing Sessions (default 900 seconds, maximum 3600).
- Node.js (Server)
- Java
- Python
- Go
- REST (curl)
const token = await users.createToken({ userId: '<userId>' }); // { secret, expire }; secret appears only once, delivered via a controlled channel
const jwt = await users.createJWT({ userId: '<userId>' }); // { jwt }; issued for an existing Sessionimport io.agentbase.models.Token;
Token token = users.createToken("<userId>", null, null); // length / expire nullable; secret appears only once
var jwt = users.createJWT("<userId>", null, null); // sessionId / duration nullable; short-lived JWT (default 900 seconds), issued for an existing Sessiontoken = users.create_token(user_id='<user_id>') # { secret, expire }; secret appears only once, delivered via a controlled channel
jwt = users.create_jwt(user_id='<user_id>') # Short-term JWT (default 900 seconds), issued for an existing Sessiontoken, err := users.CreateToken("user-123") // { secret, expire }; secret appears only once, delivered via a controlled channel
jwt, err := users.CreateJWT("user-123") // Short-term JWT (default 900 seconds), issued for an existing Session
_, _ = token, jwtcurl -sS -X POST "$APPBASE_ENDPOINT/users/user-123/tokens" \
-H 'Content-Type: application/json' \
-H "X-Appwrite-Project: $APPBASE_PROJECT_ID" \
-H "X-Appwrite-Key: $APPBASE_API_KEY" \
-d '{"length":6,"expire":900}'
# Returns 201 token model (secret returns the actual value only when called with an API Key)
# JWT: POST /users/{userId}/jwts, body {"sessionId":"<sessionId>","duration":900} (defaults to the most recent Session, max 3600)Identities and labels
listIdentities is a project-level identity view (for investigating the same third-party account bound by multiple users); after deleteIdentity unlinks an identity, that user can no longer log in with the corresponding third-party account; labels are the basis for label:<name> permission decisions, and updates follow whole-replacement semantics (labels not listed are removed).
- Node.js (Server)
- Java
- Python
- Go
- REST (curl)
const identities = await users.listIdentities({ queries: [Query.limit(25)] }); // Project-level OAuth / external identity view
await users.deleteIdentity({ identityId: '<identityId>' }); // Unlink third-party login
await users.updateLabels('<userId>', ['admin', 'premium']); // Full replacement; tags not listed are removedimport io.agentbase.Query;
var identities = users.listIdentities(List.of(Query.limit(25)), null, null); // queries / search / total; project-level OAuth / external identity view
users.deleteIdentity("<identityId>"); // After unbinding, the user can no longer log in with the corresponding third-party account
users.updateLabels("<userId>", List.of("admin", "premium")); // Full replacement; tags not listed are removedidentities = users.list_identities(queries=[Query.limit(25)]) # Project-level OAuth / external identity view
users.delete_identity(identity_id='<identity_id>') # After unbinding, the user can no longer log in with the corresponding third-party account
users.update_labels(user_id='<user_id>', labels=['admin', 'premium']) # Full replacement; anything not listed is removedidentities, err := users.ListIdentities(
users.WithListIdentitiesQueries([]string{query.Limit(25)})) // Project-level OAuth / external identity view
_, err = users.DeleteIdentity("identity-id") // After unbinding, the user can no longer log in with the corresponding third-party account
_, err = users.UpdateLabels("user-123", []string{"admin", "premium"}) // Full replacement; anything not listed is removed
_ = identities# Project-level identity list (cross-user third-party login binding view):
curl -sS "$APPBASE_ENDPOINT/users/identities?queries[]=limit(25)" -H "X-Appwrite-Project: $APPBASE_PROJECT_ID" -H "X-Appwrite-Key: $APPBASE_API_KEY"
# Unbind: DELETE /users/identities/{identityId}
# Full label replacement: PUT /users/{userId}/labels, body {"labels":["admin","premium"]}Session governance
For sessions created server-side, the secret is not in the response body and only lands in the a_session_<projectId> Cookie; when a user-state client is needed, read that Cookie and then load the Session.
- Node.js (Server)
- Java
- Python
- Go
- REST (curl)
const sessions = await users.listSessions({ userId: '<userId>' }); // Multi-device login view, useful for auditing abnormal logins
const created = await users.createSession({ userId: '<userId>' }); // Server-side login (no password verification); secret is only in the Cookie
await users.deleteSession({ userId: '<userId>', sessionId: '<sessionId>' }); // Sign out a single device (e.g., lost device)
await users.deleteSessions({ userId: '<userId>' }); // Force sign-out across all clients, often combined with a password resetvar sessions = users.listSessions("<userId>", null); // Multi-device login view, useful for auditing abnormal logins
var created = users.createSession("<userId>"); // No password verification; the secret lands only in the a_session_<projectId> Cookie
users.deleteSession("<userId>", "<sessionId>"); // Sign out a single device (e.g., lost device)
users.deleteSessions("<userId>"); // Force sign-out across all clients, often combined with a password resetsessions = users.list_sessions(user_id='<user_id>') # Multi-device login view, useful for auditing abnormal logins
created = users.create_session(user_id='<user_id>') # Server-side login (no password verification); secret is only in the Cookie
users.delete_session(user_id='<user_id>', session_id='<session_id>') # Sign out a single device (e.g., lost device)
users.delete_sessions(user_id='<user_id>') # Force sign-out across all clients, often combined with a password resetsessions, err := users.ListSessions("user-123") // Multi-device login view, useful for auditing abnormal logins
created, err := users.CreateSession("user-123") // No password verification; the secret lands only in the a_session_<projectId> Cookie
_, err = users.DeleteSession("user-123", "session-id") // Sign out a single device (e.g., lost device)
_, err = users.DeleteSessions("user-123") // Force sign-out across all clients, often combined with a password reset
_, _ = sessions, created# Server-side login (no password verification); secret is only written to the a_session_<projectId> Cookie:
curl -sS -X POST "$APPBASE_ENDPOINT/users/user-123/sessions" -H "X-Appwrite-Project: $APPBASE_PROJECT_ID" -H "X-Appwrite-Key: $APPBASE_API_KEY"
# List: GET /users/{userId}/sessions
# Sign out a single device: DELETE /users/{userId}/sessions/{sessionId}; sign out all devices: DELETE /users/{userId}/sessionsMFA management
Administrators reset authenticators and recovery codes on behalf of users: after deleting a TOTP authenticator, the user must re-bind or switch to another factor; recovery codes are generated on first use (409 is returned if they already exist), and regeneration wholly overwrites the old codes.
- Node.js (Server)
- Java
- Python
- Go
- REST (curl)
const factors = await users.listMfaFactors({ userId: '<userId>' }); // totp / phone / email / recoveryCode
await users.deleteMfaAuthenticator({ userId: '<userId>', type: 'totp' }); // Delete a TOTP authenticator
const codes = await users.createMfaRecoveryCodes({ userId: '<userId>' }); // First-time generation; returns 409 if it already exists
const current = await users.getMfaRecoveryCodes({ userId: '<userId>' }); // Read the currently valid recovery codes
await users.updateMfaRecoveryCodes({ userId: '<userId>' }); // Regenerates and fully overwrites the old codevar factors = users.listMfaFactors("<userId>"); // totp / phone / email / recoveryCode
users.deleteMfaAuthenticator("<userId>",
io.agentbase.enums.AuthenticatorType.TOTP); // After deletion, re-bind or switch to another factor
var codes = users.createMfaRecoveryCodes("<userId>"); // First-time generation; returns 409 if it already exists
var current = users.getMfaRecoveryCodes("<userId>"); // Read the currently valid recovery codes
users.updateMfaRecoveryCodes("<userId>"); // Regenerates and fully overwrites the old codefactors = users.list_mfa_factors(user_id='<user_id>') # totp / phone / email / recoveryCode
users.delete_mfa_authenticator(user_id='<user_id>', type='totp') # After deletion, re-bind or switch to another factor
codes = users.create_mfa_recovery_codes(user_id='<user_id>') # First-time generation; returns 409 if it already exists
current = users.get_mfa_recovery_codes(user_id='<user_id>') # Read the currently valid recovery codes
users.update_mfa_recovery_codes(user_id='<user_id>') # Regenerates and fully overwrites the old codefactors, err := users.ListMfaFactors("user-123") // totp / phone / email / recoveryCode
_, err = users.DeleteMfaAuthenticator("user-123", "totp") // After deletion, re-bind or switch to another factor
codes, err := users.CreateMfaRecoveryCodes("user-123") // First-time generation; returns 409 if it already exists
current, err := users.GetMfaRecoveryCodes("user-123") // Read the currently valid recovery codes
_, err = users.UpdateMfaRecoveryCodes("user-123") // Regenerates and fully overwrites the old code
_, _ = factors, codes
_ = current# Factor list: GET /users/{userId}/mfa/factors
curl -sS "$APPBASE_ENDPOINT/users/user-123/mfa/factors" -H "X-Appwrite-Project: $APPBASE_PROJECT_ID" -H "X-Appwrite-Key: $APPBASE_API_KEY"
# Toggle MFA as a whole: PATCH /users/{userId}/mfa, body {"mfa":false} (factors and recovery codes are retained after disabling)
# Delete TOTP authenticator: DELETE /users/{userId}/mfa/authenticators/totp
# Recovery codes: GET to read; PATCH generates for the first time (409 if already exists); PUT regenerates and overwrites old codesPush Targets
Message targets (providerType: email email / sms E.164 phone number / push push token) are delivery endpoints referenced by Messaging for targeted delivery; a user can have multiple targets.
- Node.js (Server)
- Java
- Python
- Go
- REST (curl)
const target = await users.createTarget({
userId: '<userId>',
targetId: ID.unique(),
providerType: 'email', // email / sms / push
identifier: 'user@example.com', // Email / E.164 phone number / push token
providerId: 'sendgrid', // Optional; if not passed, the first provider of the same type is used
name: 'Ada 主邮箱',
});
const targets = await users.listTargets({ userId: '<userId>' });
const one = await users.getTarget({ userId: '<userId>', targetId: '<targetId>' });
await users.updateTarget({ userId: '<userId>', targetId: '<targetId>', name: 'Ada 备用邮箱' });
await users.deleteTarget({ userId: '<userId>', targetId: '<targetId>' });import io.agentbase.ID;
var target = users.createTarget("<userId>", ID.unique(),
io.agentbase.enums.MessagingProviderType.EMAIL,
"user@example.com", "sendgrid", "Ada 主邮箱"); // providerType: EMAIL / SMS / PUSH enum
var targets = users.listTargets("<userId>", null, null);
var one = users.getTarget("<userId>", "<targetId>");
users.updateTarget("<userId>", "<targetId>",
null, null, "Ada 备用邮箱"); // identifier / providerId / name; only the name can be changed, pass null for other optional fields
users.deleteTarget("<userId>", "<targetId>");from agentbase.id import ID
target = users.create_target(
user_id='<user_id>', target_id=ID.unique(),
provider_type='email', # email / sms / push
identifier='user@example.com', # Email / E.164 phone number / push token
provider_id='sendgrid', name='Ada 主邮箱') # Optional; if not passed, the first provider of the same type is used
targets = users.list_targets(user_id='<user_id>')
one = users.get_target(user_id='<user_id>', target_id='<target_id>')
users.update_target(user_id='<user_id>', target_id='<target_id>', name='Ada 备用邮箱')
users.delete_target(user_id='<user_id>', target_id='<target_id>')target, err := users.CreateTarget("user-123", id.Unique(), "email", "user@example.com",
users.WithCreateTargetProviderId("sendgrid"), // Optional; if not passed, the first provider of the same type is used
users.WithCreateTargetName("Ada 主邮箱")) // ProviderType / Identifier are positional parameters: email / sms / push
targets, err := users.ListTargets("user-123")
one, err := users.GetTarget("user-123", "target-id")
_, err = users.UpdateTarget("user-123", "target-id",
users.WithUpdateTargetName("Ada 备用邮箱"))
_, err = users.DeleteTarget("user-123", "target-id")
_, _ = target, targets
_ = onecurl -sS -X POST "$APPBASE_ENDPOINT/users/user-123/targets" -H 'Content-Type: application/json' -H "X-Appwrite-Project: $APPBASE_PROJECT_ID" -H "X-Appwrite-Key: $APPBASE_API_KEY" -d '{"targetId":"push-target-1","providerType":"email","identifier":"user@example.com","providerId":"sendgrid","name":"Ada 主邮箱"}'
# Returns 201; list via GET /users/{userId}/targets; single target via GET/PATCH/DELETE /users/{userId}/targets/{targetId}Audit and memberships
User-level operation logs (login, authentication changes and other events) are used for security auditing; memberships are a read-only view of that user's presence across all teams; for the same data on the team side, see teams.mdx.
- Node.js (Server)
- Java
- Python
- Go
- REST (curl)
const logs = await users.listLogs({ userId: '<userId>' }); // Activity logs such as logins and auth changes
const memberships = await users.listMemberships({ userId: '<userId>' }); // Memberships across all teamsvar logs = users.listLogs("<userId>", null, null); // queries / total; activity logs for logins, authentication changes, etc.
var memberships = users.listMemberships("<userId>", null, null, null); // queries / search / total; memberships across all teamslogs = users.list_logs(user_id='<user_id>') # Activity logs such as logins and auth changes
memberships = users.list_memberships(user_id='<user_id>') # Memberships across all teamslogs, err := users.ListLogs("user-123") // Activity logs such as logins and auth changes
memberships, err := users.ListMemberships("user-123") // Memberships across all teams
_, _ = logs, membershipscurl -sS "$APPBASE_ENDPOINT/users/user-123/logs" -H "X-Appwrite-Project: $APPBASE_PROJECT_ID" -H "X-Appwrite-Key: $APPBASE_API_KEY"
# Read-only view of memberships: GET /users/{userId}/membershipsExample Guide
Per-language usage is centralized in the language tree
examples/; for complete sequences combining user creation / sessions / Teams, seeskills/ob-agentbase/references/server-sdks/nodejs.md,skills/ob-agentbase/references/server-sdks/java.md,skills/ob-agentbase/references/server-sdks/python.md.