Mapulus integration: operations for AI agents
Mapulus connects to Type.com as an integration. This page lists the 33 operations documented for Claude and Codex in Type.com: 26 read, 5 write, 2 destructive.
About Mapulus
Mapulus is a platform that enables users to create, manage, and analyze interactive maps, integrating with various applications to automate tasks and leverage location insights.
Categories: Developer Tools & IT
How to connect Mapulus to Type.com
- Access
- Organization connection: one shared account for the workspace.
To add the connection, follow the steps in Space connections.
Documented operations
33 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
33 operations listed.
Health
- Read
Service health check
Returns the current health status and version of the API. This endpoint does not require authentication. When the sync daemon is enabled, includes per-source sync health in the response.
- Read
Sync source health
Returns sync daemon health, optionally filtered to a single source. Use ?source=qldtraffic to get a single source's status — ideal for keyword monitoring (match "status":"ok"). Omit the parameter to get all sources with a top-level aggregate status.
Boundaries
- Read
Lookup boundaries by coordinates
Resolve a latitude/longitude point to its containing statistical boundaries. Returns all boundary types (SA1-SA4, LGA, postcode, suburb, etc.) that contain the given point, along with H3 hexagonal grid indices at resolutions 3-9 and any matching planning regions.
- Read
List available boundary types
List all available boundary types grouped by country. Returns type codes, human-readable labels, and country codes for all supported boundary geographies (20 Australian + 20 US types).
- Read
List boundaries of a type
List all boundaries of a given type. Use containedby to answer spatial questions like "what SA1s are in postcode 2000?" Examples: - GET /v1/data/boundaries/sa2 — list all SA2s - GET /v1/data/boundaries/sa1?containedby=poa:2000 — SA1s in postcode 2000 - GET /v1/data/boundaries/sa…
- Read
Export all boundaries of a type as GeoJSON
Download all boundaries of a type as a streamed GeoJSON FeatureCollection. Uses server-side streaming to handle large result sets (e.g. ~62K SA1 boundaries) without loading all features into memory.
- Read
Get a single boundary
Get metadata for a single boundary by type and code.
- Read
Export a single boundary as GeoJSON
Download a single boundary as a GeoJSON Feature with full geometry. Default simplification is full (no simplification) for single boundaries.
- Write
Batch lookup boundaries
Resolve multiple locations to their containing boundaries in a single request. Accepts up to 100 locations. Each location is resolved independently.
- Write
Batch export boundaries as GeoJSON
Export specific boundaries by ID as a GeoJSON FeatureCollection. Accepts up to 500 boundary IDs. Returns a streamed GeoJSON FeatureCollection with geometry, bbox, centroid, and properties for each boundary.
Demographics
- Read
List demographic topics
List all available demographic topics. Topics group related census fields into categories like age, income, housing, etc. Use topic IDs with the ?topics= parameter on the demographics data endpoint to request all fields in a topic at once.
- Read
List derived percentage fields
List all available derived percentage fields. Derived fields are computed at query time from raw census data. Use them with ?fields=derived.pctindigenous on the demographics endpoint. 63 static fields, always available, no extra params needed.
- Read
Get field metadata
Get detailed metadata for a single field, including related fields. Field types: - Count fields (unit: "count") — raw census counts (e.g. summary.population.persons). Use directly with ?fields= on the demographics endpoint.
- Read
Search demographic fields
Browse and search the demographic field catalog. Use topic to filter by category, search for free-text matching. The catalog contains 13,498 fields across 25 topics. Common workflows: 1. Discover what's available: GET /v1/data/demographics/fields?topic=income 2.
- Read
Query demographics
Unified demographics endpoint. Combine parameters to express what you want.
- Read
Query demographics for a polygon
Query demographic data for boundaries intersecting a GeoJSON polygon. Draw a polygon on a map and get demographics for the area. Returns either individual boundary results (with overlapfraction) or area-weighted aggregated statistics (aggregate: true).
Enrich
- Write
Enrich locations with boundary and datapack data
Batch-enrich locations with boundary resolution and datapack data. For each location, resolves the containing boundaries and attaches enrichment data from the requested datapacks. Datapacks available: demographics, fundraising. Limits: Up to 100 locations per request.
Incidents
- Read
List incidents
List and filter real-time incidents. Supports hierarchical filtering: type (incident category), eventtype (specific event category), eventsubtype (granular subtype), plus status, state, severity, source, boundary intersection, radius search, and time range.
- Read
List incident sources
List all available incident data sources. Each source represents a government or utility data feed (e.g. QLD Traffic, QFD Fire, Energex/Ergon Outages, BOM Weather). Includes sync status information.
- Read
Incident summary counts
Get aggregated incident counts by type hierarchy. Returns counts grouped by incidenttype → eventtype → eventsubtype. Supports the same filters as the list endpoint (type, status, severity, spatial, time range) but without pagination — the response is a single summary object.
- Read
Get incident detail
Get full detail for a single incident. Includes geometry, raw source data, structured location fields (locality, roadname, locationdetail), and full description with impact details.
- Read
Search incidents by polygon
Search for incidents intersecting a GeoJSON geometry. Send a GeoJSON Polygon or MultiPolygon in the request body. Optionally filter by incident type, status, and severity. Both type and status accept comma-separated values (e.g. "status": "active,upcoming").
Targeting
- Read
Generate Meta Ads targeting circles
Generate Meta Ads targeting circles from boundary polygons. Decomposes one or more statistical boundaries into a set of inclusion (positive) and exclusion (negative) circles that approximate the boundary shape for use with Meta Ads Manager custom location targeting.
- Read
Poll targeting job status
Poll the status of a targeting job. Returns the job status, and the result when completed. Jobs are account-scoped — you can only access jobs created by your account.
- Write
Create async targeting job
Create an async targeting job (explicit async path). Always creates a background job regardless of boundary size. If the result is already cached, returns 200 with the completed result.
Tiles
- Read
Vector tile for a boundary layer
Serve MVT vector tiles for any boundary type. URL template: /v1/tiles/{layer}/{z}/{x}/{y}.pbf?apikey=YOURKEY Returns a protobuf-encoded Mapbox Vector Tile containing boundary polygons that intersect the requested tile.
Maps
- Read
List maps
This endpoint returns all maps in the account. You can expand the results to include layer details with expand["layer"]. Results paginated.
- Read
Retrieve a map
This endpoint returns a single locations on a map when provided a valid map id. You can expand the results to include layer details with expand["layer"].
Locations
- Read
List locations
This endpoint returns all locations in the account. The results can be filtered by: Map ID Layer ID External ID Nearest: Returns up to the 24 closest locations from a provided latitude and longitude or address and travel profile ("driving", "cycling", "walking").
- Read
Retrieve a location
This endpoint returns a single location on a map when provided a valid location id. Example Request: curl --location 'https://api.mapulus.com/api/v1/locations/ ' \ --header 'Authorization: Bearer ' \
- Write
Create a location.
This endpoint creates a single location when provided a valid layerid in the JSON body. Locations must also have either a valid address or latitude and longitude.
- Destructive
Update a location.
This endpoint updates a location. Locations must also have either a valid address or lat and lon.
- Destructive
Delete a location.
This endpoint delete a single location. Example request: curl --location --request DELETE 'https://api.mapulus.com/api/v1/locations/ ' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer ' \
No operations match.
See How connections work for access and permissions, or browse all integrations.