Device App Access Points
The Device App Access Points API provides endpoints for managing and retrieving access points within your organization's device management system. This endpoint allows you to query access points with filtering capabilities and paginated results, making it essential for building dashboards, monitoring systems, and location-based device management applications.
Base URL: https://gate.zequenze.com/api/v1
Authentication: All endpoints require a Bearer token:
Authorization: Bearer <your-api-token>
Overview
The Device App Access Points API is designed for managing physical or logical access points within your organization's infrastructure. Access points represent locations, entry points, or network nodes where devices can connect or be monitored. This API is particularly useful for:
- Facility Management: Track access points across multiple buildings, floors, or zones
- Network Infrastructure: Monitor Wi-Fi access points, network nodes, and connectivity hubs
- Security Systems: Manage entry points for access control and monitoring
- IoT Device Deployment: Organize and locate devices based on their associated access points
Each access point contains comprehensive location data including geographical coordinates, address information, and organizational metadata. The API supports filtering by modification date and provides paginated results for efficient data handling in large deployments.
The endpoints work together to provide a complete view of your access point infrastructure, enabling you to build location-aware applications and maintain accurate records of your physical and digital access points.
Endpoints
GET /device_app_access_points/
Description: Retrieves a paginated list of all access points in your organization. This endpoint is the primary way to fetch access point data and supports filtering by last modification date, making it ideal for synchronization processes and building real-time dashboards.
Use Cases:
- Building a facility management dashboard showing all access points
- Synchronizing access point data with external systems
- Creating location-based reports and analytics
- Monitoring access point status across your organization
Full URL Example:
https://gate.zequenze.com/api/v1/device_app_access_points/?limit=50&offset=0&last_change__gte=2024-01-01T00:00:00Z
Parameters:
| Parameter | Type | In | Required | Description |
|---|---|---|---|---|
| last_change__gte | string | query | No | Filter results to only include access points modified on or after this date/time (ISO 8601 format) |
| limit | integer | query | No | Number of results to return per page (default pagination applies if not specified) |
| offset | integer | query | No | The initial index from which to return results (used for pagination) |
cURL Example:
curl -X GET "https://gate.zequenze.com/api/v1/device_app_access_points/?limit=25&offset=0&last_change__gte=2024-01-15T00:00:00Z" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json"
Example Response:
{
"count": 156,
"next": "https://gate.zequenze.com/api/v1/device_app_access_points/?limit=25&offset=25",
"previous": null,
"results": [
{
"id": 1,
"name": "Main Building Lobby WiFi",
"short_name": "main-lobby-wifi",
"is_active": true,
"description": "Primary WiFi access point for main building lobby area with high-speed internet access",
"organization_id": "org_12345",
"thumbnail": "https://gate.zequenze.com/media/thumbnails/access_point_1.jpg",
"address": "123 Business Park Drive",
"reference": "AP-001-LOBBY",
"city": "San Francisco",
"postal_code": "94105",
"state": "California",
"region": "West Coast",
"country_code": "US",
"latitude": "37.7749",
"longitude": "-122.4194",
"created": "2024-01-10T08:30:00Z",
"last_change": "2024-01-20T14:45:00Z"
},
{
"id": 2,
"name": "Conference Room Alpha Access Point",
"short_name": "conf-alpha-ap",
"is_active": true,
"description": "Dedicated access point for Conference Room Alpha supporting up to 50 concurrent devices",
"organization_id": "org_12345",
"thumbnail": "https://gate.zequenze.com/media/thumbnails/access_point_2.jpg",
"address": "123 Business Park Drive",
"reference": "AP-002-CONF-A",
"city": "San Francisco",
"postal_code": "94105",
"state": "California",
"region": "West Coast",
"country_code": "US",
"latitude": "37.7749",
"longitude": "-122.4194",
"created": "2024-01-12T10:15:00Z",
"last_change": "2024-01-18T16:20:00Z"
}
]
}
Response Codes:
| Status | Description |
|---|---|
| 200 | Success - Returns paginated list of access points |
| 401 | Unauthorized - Invalid or missing API token |
| 403 | Forbidden - Insufficient permissions to access access points |
| 500 | Internal Server Error - Server-side error occurred |
Common Use Cases
Use Case 1: Building a Real-time Access Point Dashboard
Fetch all active access points and display their status, location, and connection information on a monitoring dashboard. Use the is_active field to filter and highlight operational status.
Use Case 2: Synchronizing Access Point Data
Use the last_change__gte parameter to implement incremental synchronization with external facility management systems, only fetching access points that have been modified since your last sync.
Use Case 3: Location-Based Device Management
Combine access point geographical data (latitude/longitude) with address information to create location-aware applications that can route technicians to specific access points or generate service reports by region.
Use Case 4: Inventory and Asset Tracking
Utilize the reference codes and descriptions to maintain accurate inventory records of network infrastructure, tracking access point deployment across multiple facilities and locations.
Use Case 5: Reporting and Analytics
Generate comprehensive reports on access point distribution using the city, state, and region fields, helping with capacity planning and infrastructure investment decisions.
Best Practices
-
Pagination Management: Always implement proper pagination when dealing with large numbers of access points. Start with reasonable page sizes (25-100 items) and implement client-side pagination controls.
-
Incremental Synchronization: Use the
last_change__gteparameter for efficient data synchronization. Store the timestamp of your last successful sync and use it to fetch only modified records. -
Geographic Data Handling: When working with latitude and longitude coordinates, ensure your application properly handles decimal precision and validates coordinate ranges before using them in mapping applications.
-
Reference Code Standardization: Establish consistent naming conventions for the
short_nameandreferencefields to enable better searching, sorting, and integration with other systems. -
Error Handling: Implement robust error handling for network timeouts and API rate limits. Consider implementing exponential backoff for retry logic when dealing with temporary service unavailability.
-
Caching Strategy: Cache access point data appropriately since this information typically doesn't change frequently. Use the
last_changetimestamps to implement intelligent cache invalidation.