canonical: https://jentic.com/apis/swaggerhub.jgutierrez1457/api-enrollment-bunkey

# Jgutierrez1457 API Enrollment Bunkey

Documentación de API Enrollment Bunkey JG. The API exposes 24 endpoints secured with bearer authentication.

## For AI agents

Programmatically post-auth-signup, post-auth-signin. Covers 24 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for ai and machine learning only.

## Capabilities

- post-auth-signup
- post-auth-signin
- patch-users-by-iduser-edit-name
- patch-users-by-iduser-edit-email
- patch-users-by-iduser-edit-password
- delete-users-by-iduser
- post-students

## Use cases

### AI and Machine Learning Operations

Use the API Enrollment Bunkey to perform ai ml operations programmatically. The API provides 24 endpoints covering core functionality including post-auth-signup, post-auth-signin, patch-users-by-iduser-edit-name.

Example prompt: Call POST `/auth/signup` to post-auth-signup

### Automated Authentication Management

Automate authentication operations by combining multiple API Enrollment Bunkey endpoints. Agents can post-auth-signin and then patch-users-by-iduser-edit-name in a single workflow.

Example prompt: Call POST `/auth/signin` to post-auth-signin, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Enrollment Bunkey 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 bearer tokens manually.

Example prompt: Search Jentic for 'post-auth-signup', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/signup` | post-auth-signup |
| POST | `/auth/signin` | post-auth-signin |
| PATCH | `/users/{iduser}/edit/name` | patch-users-by-iduser-edit-name |
| PATCH | `/users/{iduser}/edit/email` | patch-users-by-iduser-edit-email |
| PATCH | `/users/{iduser}/edit/password` | patch-users-by-iduser-edit-password |
| DELETE | `/users/{iduser}` | delete-users-by-iduser |
| POST | `/students` | post-students |
| GET | `/students` | get-students |

## Key resources

- **Authentication** — Operations related to Authentication
- **Consultas** — Operations related to Consultas
- **Courses** — Operations related to Courses
- **Enrollments** — Operations related to Enrollments
- **Students** — Operations related to Students

## Why Jentic

- **Setup:** Wiring the API Enrollment Bunkey by hand means implementing its JWT bearer flow, pointing at the Heroku host, and writing your own retry handling around the users, students, courses, and enrollments calls. Through Jentic you install once, import API Enrollment Bunkey from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** This API puts the resource id in the URL path (`/users/{iduser}`, `/students/{idstudent}`, `/courses/{idcourse}`, `/enrollments/{idenrollment}`), so a rule can pin your agent to one course or enrollment and the operations around it. You choose the operations it may call, so destructive ones like deleting a user or removing a student from an enrollment are not included unless you add them.
- **Credential handling:** Your API Enrollment Bunkey bearer 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 'enroll a student in a course' or 'look up an enrollment', and Jentic returns the matching API Enrollment Bunkey operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Openai** — Alternative ai ml API
- **Anthropic** — Alternative ai ml API
- **Cohere** — Complementary ai ml API
- **Huggingface** — Complementary ai ml API

## FAQ

### What authentication does the API Enrollment Bunkey use?

The API Enrollment Bunkey uses a Bearer token 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 post-auth-signup with the API Enrollment Bunkey?

Yes. Use the POST `/auth/signup` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the API Enrollment Bunkey?

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 post-auth-signup through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'post-auth-signup'. Jentic returns the matching API Enrollment Bunkey operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API Enrollment Bunkey have?

The API Enrollment Bunkey exposes 24 endpoints covering authentication, consultas, courses operations.

### Can I limit what my agent is allowed to do with the API Enrollment Bunkey?

Yes. Because you run Jentic One yourself, your own rules decide which API Enrollment Bunkey operations and credentials the agent may use, so you can grant read-only calls like listing students or looking up an enrollment while withholding destructive ones such as deleting a user or removing a student from an enrollment. Since this API carries the resource id in the URL path, for example `/users/{iduser}`, `/students/{idstudent}`, `/courses/{idcourse}`, and `/enrollments/{idenrollment}`, you can pin the agent to a single course or enrollment and just the operations around it. Any operation you do not add stays off limits.