Core Platform Guide
The Core Platform API provides foundational services that underpin all SensorUp operations. It includes authentication (su-auth), user management (su-user), core infrastructure (su-backend), geospatial services (su-maps), data catalogs (su-catalog), and event streaming (su-eventhub).
Overview
The Core Platform enables:- Authentication: Session management, API keys, and federated sign-in
- User Management: User profiles, permissions, and device tracking
- Geospatial Services: Maps, location queries, and spatial operations
- Data Catalogs: Schema registry and metadata management
- Event Streaming: Real-time event subscriptions and notifications
- Core Infrastructure: Configuration, health checks, and system operations
Authentication (su-auth)
For comprehensive authentication documentation, see the Authentication Guide.Quick Reference
Session-based Authentication:Session Lifetimes
| Client Type | Hard Expiry | Soft Expiry (Idle) |
|---|---|---|
| Explorer (Web) | 30 days | 7 days |
| SensorHub Android | 365 days | 60 days |
| SensorHub iOS | 365 days | 60 days |
| API Key | 365 days | 60 days |
Authentication Methods
- Cookie:
sensorup_sessionid(auto-set in browser) - Header:
x-sensorup-sessionid(for API clients and M2M)
User Management (su-user)
Query User Profile
Update User Profile
Query User Permissions
List Users in Group
Device Management
Geospatial Services (su-maps)
Query Map Configuration
Get Map Tiles
Geocoding
Reverse Geocoding
Spatial Queries
GeoJSON Support
The platform supports full GeoJSON geometry types:Data Catalogs (su-catalog)
Query Catalog Entries
Get Specific Catalog Entry
Create Catalog Entry
Query by Category
Event Streaming (su-eventhub)
Subscribe to Events
Publish Event
Query Event History
Event Types
Common system event types:| Event Type | Description |
|---|---|
ASSET_CREATED | New asset created |
ASSET_UPDATED | Asset modified |
ASSET_DELETED | Asset removed |
ISSUE_CREATED | New issue opened |
ISSUE_UPDATED | Issue modified |
ISSUE_CLOSED | Issue resolved and closed |
DETECTION_CREATED | New detection recorded |
FORM_SUBMITTED | XForm response submitted |
USER_SIGNED_IN | User authentication |
API_KEY_CREATED | New API key generated |
Core Infrastructure (su-backend)
System Configuration
Health Check
Feature Flags
System Metrics
Common Patterns
Authentication Flow
Geospatial Queries
Event Streaming
Catalog-Driven Forms
Best Practices
1. Session Management
Monitor session expiration and refresh proactively:2. Geospatial Performance
Use appropriate zoom levels and bounds for map tiles:3. Event Filtering
Subscribe only to needed event types:4. Catalog Validation
Leverage catalog schemas for data validation:5. Permission Checks
Always verify user permissions before restricted operations:Error Handling
Platform mutations return consistent error formats:AUTHENTICATION_FAILED: Invalid credentialsAUTHORIZATION_FAILED: Insufficient permissionsVALIDATION_ERROR: Input validation failedNOT_FOUND: Resource does not existDUPLICATE: Resource already existsRATE_LIMIT_EXCEEDED: Too many requests
Related Resources
- Authentication Guide - Comprehensive auth documentation
- Auth Subgraph Reference - Complete auth schema
- User Subgraph Reference - User management schema
- Maps Subgraph Reference - Geospatial schema
- Catalog Subgraph Reference - Catalog schema
- EventHub Subgraph Reference - Event streaming schema
- Backend Subgraph Reference - Core infrastructure schema
- Common Patterns - Pagination, filtering, and error handling