MAPSS Integration Hub
API & Webhook Docs

Provider setup, staff testing, and API reference

This page brings together the live OpenAPI contract, provider-facing webhook instructions, and the same step-by-step testing flow used in the MAPSS platform. It is meant to help staff set up feeds cleanly and help providers send data to the right place the first time.
0Documented routes
0API groups
0Starter templates
0Supported technology groups

Webhook feeds

Give providers the MAPSS intake URL for the feed. Most feeds use x-api-key, some use Authorization: Bearer, and selected feeds can be deliberately public.

/ingest/{integrationId} /standard/observations/{integrationId} /standard/events/{integrationId}

Poll-based feeds

MAPSS fetches the provider API itself. Run a source fetch first, confirm the sample payload, then preview normalization, enrichments, and the outbound ArcGIS feature before you switch writes on.

/api/source/test-fetch /api/test-normalize /api/mapping/preview-feature

TRBOnet radio agents

TRBOnet and compatible radio agents POST to the Hub provider-key path. The provider key stays in the URL path and the bearer token is the feed intake key.

/api/v1.0/{providerKey} Authorization: Bearer

Common provider examples

Use these as starting points when a provider asks what to send to MAPSS.
Loading examples...

Quick endpoint guide

Loading live route summary...
Live Swagger Reference
Use Authorize for admin routes after MAPSS staff login. Provider-facing webhook routes use feed-level intake credentials instead.
Try it out enabled Uses /api/openapi.json
Loading the Swagger reference...