This guide walks you through running SolSQL API locally, authenticating as a user, and fetching your first list of places. By the end you will have a working base URL, a valid login response, and a list of place summaries returned from the API.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/jparra-amell/api_solsql/llms.txt
Use this file to discover all available pages before exploring further.
Start the API server
Run the API using Docker (see Deployment) or the .NET CLI. Once running, the server listens on port 8080.Verify the server is up by opening the Swagger UI in your browser:You should see the interactive API documentation listing all available endpoints.
Authenticate with the login endpoint
All protected operations require a valid user. Call A successful response returns the authenticated user object with the If the email is not found, the role does not match, or the password is incorrect, the API returns
POST /api/LoginRequest/login with your email, password, and role number.Password field set to null:401 Unauthorized with a descriptive message.Passwords are stored as BCrypt hashes. Always send the plain-text password in the request body — the API handles verification internally.
Fetch a summary list of places
Once you have confirmed the API is reachable and authentication works, call The response is a JSON array where each entry contains general information about a place of interest:
GET /api/Places/info_rapida to retrieve a summary list of all active places:Next steps
Deploy with Docker
Build and run the API as a Docker container with your MySQL connection.
Authentication concepts
Understand how roles and BCrypt hashing work in the login flow.
Places API reference
Full endpoint documentation for place CRUD, search, and detail views.
API reference
Complete reference for every resource and endpoint in SolSQL API.