NOT IMPLEMENTED: The MedicoController is empty in the source code. These endpoints are architectural documentation only and will return 404 errors if called. Only the Especialidad endpoints are currently functional.
The Médicos (Doctors) resource is architecturally designed to provide CRUD operations for managing doctor profiles. The data model is defined, but the controller endpoints are not yet implemented.
Response: 200 OKReturns the doctor object (same structure as above).Response: 404 Not FoundReturned when the doctor with the specified ID doesn’t exist.Example Request:
curl -X GET "https://localhost:5001/api/Medico/1" \ -H "Content-Type: application/json"
Doctor’s phone number (optional, must be valid phone format)
When creating a doctor, you must assign them to an existing specialty using the especialidadId. However, the CreateMedicoDto doesn’t include this field - the specialty assignment may be handled separately or through a different mechanism.
Response: 201 CreatedReturns the created doctor object with the assigned ID.Response: 400 Bad RequestReturned when validation fails.Response: 409 ConflictReturned when a doctor with the same license number already exists.Example Request:
Doctor’s phone number (optional, must be valid phone format)
Response: 200 OKReturns the updated doctor object.Response: 404 Not FoundReturned when the doctor with the specified ID doesn’t exist.Response: 400 Bad RequestReturned when validation fails.Response: 409 ConflictReturned when the updated license number conflicts with another existing doctor.Example Request:
Response: 204 No ContentReturned when the doctor is successfully deleted.Response: 404 Not FoundReturned when the doctor with the specified ID doesn’t exist.Example Request: