Enquiry API for Practice Projects
The Enquiry API catalogue brings together the documented REST operations for this practice project. It is a starting point for developers who want to connect a frontend to an existing HTTP service instead of building every backend operation first. The method and path list below comes from the bundled provider specification; review the live documentation before depending on a field or sending a write request.
Build a enquiry practice project
Start by reading the available endpoint names and identifying a small user journey supported by the catalogue. Design a list screen, a detail screen and any forms that the documented operations require. Make the loading state visible, show an empty state when a collection has no items and explain request failures in plain language. A useful portfolio demonstration includes these states as well as the successful response.
Keep the first version small. Map returned fields to a view model, validate form inputs and confirm which values belong in the URL, query string or JSON body. Use synthetic records for demonstration and avoid entering personal information. Shared practice services can change or become unavailable, so keep fixtures for development and handle an unexpected response gracefully.
Documented endpoints
| Method | Path | Description |
|---|---|---|
| POST | /api/Enquiry/filter-enquiries | /api/Enquiry/filter-enquiries |
| GET | /api/Enquiry/get-enquiries | /api/Enquiry/get-enquiries |
| GET | /api/Enquiry/get-enquiry/{id} | /api/Enquiry/get-enquiry/{id} |
| POST | /api/Enquiry/create-enquiry | /api/Enquiry/create-enquiry |
| PUT | /api/Enquiry/update-enquiry/{id} | /api/Enquiry/update-enquiry/{id} |
| DELETE | /api/Enquiry/delete-enquiry/{id} | /api/Enquiry/delete-enquiry/{id} |
| GET | /api/Enquiry/get-categories | /api/Enquiry/get-categories |
| POST | /api/Enquiry/create-category | /api/Enquiry/create-category |
| PUT | /api/Enquiry/update-category/{id} | /api/Enquiry/update-category/{id} |
| DELETE | /api/Enquiry/delete-category/{id} | /api/Enquiry/delete-category/{id} |
| GET | /api/Enquiry/get-statuses | /api/Enquiry/get-statuses |
| POST | /api/Enquiry/create-status | /api/Enquiry/create-status |
| PUT | /api/Enquiry/update-status/{id} | /api/Enquiry/update-status/{id} |
| DELETE | /api/Enquiry/delete-status/{id} | /api/Enquiry/delete-status/{id} |
Sample request and response
This example uses a documented GET operation. Replace any path placeholders and supply required query values or authentication headers listed by the provider. It is a request example, not a guarantee that the service will return the same data.
curl -X GET 'https://api.freeprojectapi.com/api/Enquiry/get-enquiries' -H 'Accept: application/json'No successful response example is supplied for this operation in the bundled specification. Run a request in the API hub and inspect its status, content type and body before choosing a response model.
Use with Angular, React or JavaScript
In Angular, put HTTP integration in a service and expose request state to a component. In React, keep fetching and error handling separate from presentation components. With JavaScript, use an HTTP client and check the response status before parsing JSON. Each approach should encode parameters, handle cancellation where appropriate and respect provider access rules. Browser requests also depend on CORS support.
Before testing
Check the provider base URL and current specification, particularly when the bundled snapshot is older than the running service. Authentication, rate limits and persistence are provider-specific. Never ship private credentials in frontend code. Test read operations first and understand the effect of a create, update or delete operation on shared records.
Test Enquiry API requests in the hub