This collection tests the Smart Campus REST API (api/v1), a backend service for managing IoT infrastructure across a smart campus environment. It covers the full lifecycle of campus resources including rooms, sensors, and sensor readings.
Rooms – Create, retrieve, and delete campus rooms
\nSensors – Register and filter sensors by type (Temperature, CO2, Occupancy)
\nSensor Readings – Post and retrieve time-series readings per sensor
\nCRUD operations across all resource types
\nError handling – duplicate entries, missing fields, invalid IDs, content-type mismatches, and 500-level errors
\nEdge cases – empty collections, maintenance-state sensors, non-existent resources, and filtered queries with no matches
\nOrganized into 5 sequential parts: Discovery → Rooms → Sensors → Sensor Readings → Errors, reflecting a logical API exploration and validation workflow.
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"CSA Smart Campus API","slug":"csa-smart-campus-api"}],"owner":"54114927","collectionId":"1df62209-1fa9-4e45-a63c-9981fb6bcbfc","publishedId":"2sBXqDsiQo","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2026-04-23T13:44:11.000Z"},"item":[{"name":"Part 1 - Discovery","item":[{"name":"Discovery Request","id":"5a151c07-72d1-4f1b-87e1-dffdcc6ef9f7","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"http://localhost:8080/Smart_Campus_API/api/v1/","description":"Sends a GET request to the root endpoint GET /api/v1/ to verify that the Smart Campus API is reachable and operational. This serves as the entry point for the API, confirming the service is running and returning a valid response before any further operations are performed.
This folder tests the API's root discovery endpoint, which serves as the entry point for the Smart Campus API. It includes a single GET /api/v1/ request to verify that the API is reachable and returns the expected top-level resource or metadata. This is typically used to confirm the API is live and to explore available endpoints or versioning information.
Sends a GET request to GET /api/v1/rooms before any rooms have been created. Verifies that the API correctly returns an empty list (or appropriate empty-state response) when no room resources exist in the system.
Sends a POST request to POST /api/v1/rooms to create a new room with ID R101, named \"Lab Room\", with a capacity of 30. Verifies that the API successfully registers the room and returns the expected created resource.
Sends a POST request to POST /api/v1/rooms to create a second room with ID R102. Verifies that the API can register multiple rooms independently and returns the correct response for the newly created resource.
Sends a POST request to POST /api/v1/rooms to create a third room with ID R103, named \"Library Quiet Study\", with a capacity of 50. Verifies successful room creation and is also used as the target room for subsequent duplicate and deletion tests.
Sends a POST request to POST /api/v1/rooms attempting to create a room with ID R103, which already exists in the system. Verifies that the API correctly rejects the duplicate and returns an appropriate error response (e.g., 409 Conflict).
Sends a POST request to POST /api/v1/rooms with a body that omits the required id field, providing only name and capacity. Verifies that the API enforces field validation and returns an appropriate error response (e.g., 400 Bad Request) when a required field is missing.
Sends a GET request to GET /api/v1/rooms after multiple rooms have been created. Verifies that the API returns a complete list of all registered rooms, confirming that room data is persisted and retrievable correctly.
Sends a GET request to GET /api/v1/rooms/R101 to retrieve a specific room by its ID. Verifies that the API returns the correct room details for the given identifier, confirming individual resource lookup works as expected.
Sends a GET request to GET /api/v1/rooms/R1Fake using an ID that does not correspond to any registered room. Verifies that the API returns an appropriate error response (e.g., 404 Not Found) when a requested resource does not exist.
Sends a POST request to POST /api/v1/rooms with the Content-Type header set to text/plain and a plain-text body instead of JSON. Verifies that the API correctly rejects requests with an unsupported or mismatched content type and returns an appropriate error response (e.g., 415 Unsupported Media Type or 400 Bad Request).
Sends a DELETE request to DELETE /api/v1/rooms/R103 to remove a room that has no sensors assigned to it. Verifies that the API successfully deletes an unoccupied room and returns the appropriate success response.
This folder tests the full lifecycle of room management via the /api/v1/rooms endpoints, covering creation, retrieval, and deletion operations. Key scenarios include creating multiple rooms (R101, R102, R103), fetching all rooms and a specific room by ID, and deleting both empty rooms and rooms that have sensors attached. Notable edge cases include attempting to create a duplicate room, creating a room without an ID, retrieving a non-existent room, and sending a request with a Content-Type mismatch to validate error handling.
Sends a POST request to POST /api/v1/sensors to register a new Temperature sensor with ID TEMP-001, assigned to room R101, with an ACTIVE status and an initial value of 22.5. Verifies that the API successfully creates the sensor and returns the expected resource.
Sends a POST request to POST /api/v1/sensors to register a CO2 sensor with ID CO2-001, assigned to room R101, with an ACTIVE status and an initial value of 400.0. Verifies that the API supports multiple sensor types and correctly persists the new sensor.
Sends a POST request to POST /api/v1/sensors to register an Occupancy sensor with ID OCC-001, assigned to room R101, with a MAINTENANCE status and an initial value of 0.0. Verifies that the API correctly handles sensors in non-active states and persists the resource accordingly.
Sends a POST request to POST /api/v1/sensors attempting to register a sensor assigned to a non-existent room (FAKE-ROOM). Verifies that the API enforces referential integrity by rejecting the registration and returning an appropriate error response (e.g., 404 Not Found or 400 Bad Request).
Sends a POST request to POST /api/v1/sensors attempting to register a sensor with ID TEMP-001, which already exists in the system. Verifies that the API correctly rejects the duplicate registration and returns an appropriate error response (e.g., 409 Conflict).
Sends a GET request to GET /api/v1/sensors to retrieve the full list of registered sensors. Verifies that all previously created sensors are returned correctly, confirming that sensor data is persisted and the list endpoint functions as expected.
Sends a GET request to GET /api/v1/sensors?type=Temperature to retrieve only sensors of type Temperature. Verifies that the API correctly applies the type filter and returns only matching sensors from the registered list.
Sends a GET request to GET /api/v1/sensors?type=CO2 to retrieve only sensors of type CO2. Verifies that the type filter works correctly for a different sensor type and returns only the matching sensor(s).
Sends a GET request to GET /api/v1/sensors?type=Humidity to filter sensors by a type that has no registered sensors. Verifies that the API returns an empty list (or appropriate empty-state response) when no sensors match the specified filter.
Sends a DELETE request to DELETE /api/v1/rooms/R101 to attempt deletion of a room that has active sensors registered to it. Verifies that the API enforces referential integrity by rejecting the deletion and returning an appropriate error response (e.g., 409 Conflict or 400 Bad Request).
This folder tests sensor registration and retrieval operations via the /api/v1/sensors endpoints. It covers registering sensors of different types (Temperature, CO2, and an Occupancy sensor in MAINTENANCE status), fetching all sensors, and filtering sensors by type — including a filter that returns no matches. Edge cases include attempting to register a duplicate sensor and registering a sensor with an invalid ID format to verify proper validation and error responses.
Sends a POST request to POST /api/v1/sensors/TEMP-001/readings to submit the first sensor reading (value: 24.5) for the active Temperature sensor TEMP-001. Verifies that the API accepts and persists the reading for an active sensor.
Sends a POST request to POST /api/v1/sensors/TEMP-001/readings to submit a second sensor reading for TEMP-001. Verifies that the API correctly appends multiple readings to the same sensor's history.
Sends a POST request to POST /api/v1/sensors/TEMP-001/readings to submit a third sensor reading for TEMP-001. Verifies continued accumulation of readings and that the sensor's reading history grows as expected.
Sends a GET request to GET /api/v1/sensors/TEMP-001/readings to retrieve the full reading history for sensor TEMP-001. Verifies that all previously posted readings are returned correctly and that the readings endpoint reflects the accumulated data.
Sends a GET request to GET /api/v1/sensors/TEMP-999/readings using a sensor ID that does not exist in the system. Verifies that the API returns an appropriate error response (e.g., 404 Not Found) when attempting to retrieve readings for an unregistered sensor.
Sends a GET request to GET /api/v1/sensors/TEMP-001 to retrieve the current state of sensor TEMP-001 after multiple readings have been posted. Verifies that the sensor's currentValue field has been updated to reflect the most recent reading, confirming that the API correctly maintains live sensor state.
Sends a GET request to GET /api/v1/sensors/OCC-001/readings to retrieve readings for sensor OCC-001, which has had no readings posted. Verifies that the API returns an empty list (or appropriate empty-state response) when a sensor exists but has no reading history.
Sends a POST request to POST /api/v1/sensors/OCC-001/readings attempting to post a reading (value: 500.0) to sensor OCC-001, which is in MAINTENANCE status. Verifies that the API correctly rejects readings for non-active sensors and returns an appropriate error response.
This folder tests posting and retrieving sensor readings via the /api/v1/sensors/{sensorId}/readings endpoints. It includes posting multiple readings to an active sensor (TEMP-001) and verifying that the sensor's currentValue is updated accordingly. Notable edge cases include posting a reading to a sensor in MAINTENANCE status (OCC-001), retrieving readings for a sensor with no history, and fetching readings for a non-existent sensor to validate appropriate error responses.
Sends a POST request to POST /api/v1/rooms with a deliberately malformed JSON body (missing the closing brace) to trigger a server-side parsing failure. Verifies that the API returns a 500 Internal Server Error under this error condition, testing the API's handling of unexpected server-side failures.
This folder tests the API's handling of server-side error conditions, specifically targeting scenarios that trigger a 500 Internal Server Error. It contains a single POST /api/v1/rooms request crafted to provoke an unexpected server failure, verifying that the API returns a proper error response rather than crashing silently. This is useful for confirming that error handling and logging are functioning correctly under fault conditions.