canonical: https://jentic.com/apis/swaggerhub.romankubasov/api-welbex-service-users # Romankubasov API Welbex Service Users Welbex Test Assignment. The API exposes 7 endpoints secured with apiKey authentication. ## For AI agents Programmatically check validity of token and return user, login user. Covers 7 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for education only. ## Capabilities - check validity of token and return User - login user - logout user (authorized users only) - register new user - get all users (ADMIN only) - edit user email (ADMIN only) - delete user (ADMIN only) ## Use cases ### Education Operations Use the API Welbex Service Users to perform education operations programmatically. The API provides 7 endpoints covering core functionality including check validity of token and return user, login user, logout user (authorized users only). Example prompt: Call POST /auth to check validity of token and return user ### Automated Auth Management Automate auth operations by combining multiple API Welbex Service Users endpoints. Agents can login user and then logout user (authorized users only) in a single workflow. Example prompt: Call POST /login to login user, then verify the result ### AI Agent Integration via Jentic AI agents discover and call API Welbex Service Users endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually. Example prompt: Search Jentic for 'check validity of token and return user', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /auth | check validity of token and return User | | POST | /login | login user | | POST | /logout | logout user (authorized users only) | | POST | /register | register new user | | GET | /users | get all users (ADMIN only) | | PUT | /users | edit user email (ADMIN only) | | DELETE | /users | delete user (ADMIN only) | ## Key resources - **Auth** — Operations for auth - **Login** — Operations for login - **Logout** — Operations for logout - **Register** — Operations for register - **Users** — Operations for users ## Why Jentic - **Setup:** Wiring API Welbex Service Users by hand means learning its JWT-in-Authorization-header scheme, wiring the header on every call, and handling requests and retries yourself. Through Jentic you install once, import API Welbex Service Users from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The user target travels in the request body rather than the URL path, so scope the agent by operation: limit it to the operations it needs, such as login or checking a token. Writes like register, update, or delete stay out of the allowed set unless you add them. - **Credential handling:** Your API Welbex Service Users token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'validate a token and return the user' or 'log a user in', and Jentic returns the matching API Welbex Service Users operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Schoology** — Alternative education API - **Stripe** — Complementary API for broader integration workflows - **Twilio** — Complementary API for broader integration workflows ## FAQ ### What authentication does the API Welbex Service Users use? The API Welbex Service Users uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I check validity of token and return user with the API Welbex Service Users? Yes. Use the POST /auth endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the API Welbex Service Users? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I check validity of token and return user through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check validity of token and return user'. Jentic returns the matching API Welbex Service Users operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the API Welbex Service Users have? The API Welbex Service Users exposes 7 endpoints covering auth, login, logout operations. ### Can I limit what my agent is allowed to do with the API Welbex Service Users? Yes. Because you run Jentic One yourself, your own rules decide which API Welbex Service Users operations and credentials the agent may use. Since the user target travels in the request body rather than the URL path, you scope by operation: allow only what the agent needs, such as POST /login or the POST /auth token check, and keep write operations like register, edit user email, and delete user out of the allowed set unless you add them. The stored token is injected at execution time under those limits, so the agent can call only the operations you permit.