The Restaurants API lets an authenticated restaurant owner read and update the core details of their establishment. Both endpoints are scoped to the requesting user — the server resolves the restaurant by primary key and verifies thatDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/lffiesco-svg/gastromovil/llms.txt
Use this file to discover all available pages before exploring further.
propietario == request.user, so one owner can never read or modify another owner’s restaurant. Restaurant images are stored on Cloudinary; the image field is managed separately from the core detail fields on the edit endpoint.
Both endpoints require authentication via JWT Bearer token or an active Django session. Requests that arrive without credentials receive
401 Unauthorized. A valid token for a user who does not own the specified restaurant returns 404 Not Found.Retrieve Restaurant Details
Returns the core fields of a single restaurant identified by its primary key.GET /api/restaurantes/<pk>/
Path Parameters
Primary key of the restaurant to retrieve. The authenticated user must be the owner of this restaurant.
Example Request
Response
200 OK
Unique database identifier of the restaurant.
Display name of the restaurant.
Street address of the restaurant.
Contact phone number (up to 15 characters).
Whether the restaurant is currently accepting orders.
true means the restaurant appears in the public listing.404 Not Found — restaurant does not exist or belongs to another user.
Update Restaurant Details
Performs a partial update on a restaurant’s core fields. Only the fields included in the request body are changed; omitted fields retain their current values.PUT /api/restaurantes/<pk>/editar/
Path Parameters
Primary key of the restaurant to update. The authenticated user must be the owner.
Request Body
All body fields are optional — send only what you want to change.New display name for the restaurant (max 200 characters).
Updated street address (max 200 characters).
Updated contact phone number (max 15 characters).
Set to
false to take the restaurant offline and stop it appearing in the public restaurant listing.Example Request
Responses
200 OK — fields updated successfully.
404 Not Found — restaurant does not exist or belongs to another user.
401 Unauthorized — missing or expired token.