Skip to main content

Hostspot Access Points

Retrieve information about hotspot access points and their locations.

Base URL: https://gate.zequenze.com/api/v1

Authentication: All endpoints require a Bearer token:

Authorization: Bearer <your-api-token>

Endpoints

GET /hostspot_access_points/

Retrieves a paginated list of hotspot access points with optional filtering capabilities. Use this endpoint to get information about wireless access points, their locations, and configuration details.

Parameters:

Parameter Type In Required Description
last_change__gte string query No Filter by last change date (greater than or equal). Accepts ISO format: 2000-01-01, 2000-01-01 00:01:00, or 2000-01-01 00:01:00+00:00
limit integer query No Number of results to return per page (default pagination limit applies)
offset integer query No The initial index from which to return the results
have_coordinates boolean query No When true, only returns access points that have GPS coordinates set

Example Request:

GET /api/v1/hostspot_access_points/?limit=50&have_coordinates=true&last_change__gte=2024-01-01

Example Response:

{
  "count": 125,
  "next": "https://gate.zequenze.com/api/v1/hostspot_access_points/?limit=50&offset=50",
  "previous": null,
  "results": [
    {
      "id": 1,
      "name": "AP-Main-Lobby",
      "mac_address": "00:1B:44:11:3A:B7",
      "ip_address": "192.168.1.100",
      "location": {
        "name": "Main Building Lobby",
        "latitude": 40.7128,
        "longitude": -74.0060,
        "floor": "Ground Floor"
      },
      "status": "active",
      "signal_strength": -45,
      "connected_clients": 12,
      "last_change": "2024-01-15T10:30:00Z",
      "model": "Cisco AIR-AP2802I",
      "firmware_version": "8.10.185.0"
    },
    {
      "id": 2,
      "name": "AP-Conference-Room-A",
      "mac_address": "00:1B:44:22:4B:C8",
      "ip_address": "192.168.1.101",
      "location": {
        "name": "Conference Room A",
        "latitude": 40.7130,
        "longitude": -74.0058,
        "floor": "2nd Floor"
      },
      "status": "active",
      "signal_strength": -38,
      "connected_clients": 5,
      "last_change": "2024-01-14T16:45:00Z",
      "model": "Cisco AIR-AP2802I",
      "firmware_version": "8.10.185.0"
    }
  ]
}

Response Status Codes:

Status Description
200 Successfully retrieved access points list
400 Bad request - invalid parameters
401 Unauthorized - invalid or missing Bearer token
403 Forbidden - insufficient permissions
500 Internal server error

Best Practices

  • Pagination: Use limit and offset parameters to handle large datasets efficiently. Start with smaller page sizes (e.g., 50-100) to test response times
  • Date Filtering: When using last_change__gte, include timezone information in ISO format for accurate filtering across different time zones
  • Location Filtering: Use have_coordinates=true when you need access points with precise location data for mapping or GPS-based applications
  • Rate Limiting: Implement appropriate delays between requests to avoid overwhelming the API, especially when retrieving large datasets
  • Error Handling: Always check the HTTP status code and handle pagination end conditions by monitoring the next field in responses
  • Caching: Consider caching results for access points that don't change frequently, using the last_change field to determine when to refresh cached data
Back to top