The Concept3D Interactive Map API lets you use map data from your CMS in custom websites, apps, and campus systems. It exposes the same location, category, search, and wayfinding data that powers your public map.
The API is private. Access must be granted, and there is an additional cost. Reach out to your Partner Success Manager to get started.
API Policy
All API usage must align with Concept3D's API Policy.
What are common use cases?
Clients have used the API to:
- Website search: Integrate map locations into a website search bar so visitors can find campus places more easily.
- Backups and data sync: Extract location and category data from the CMS for regular backups or other systems.
- Class schedule links: Generate links that take students from a schedule to the right classroom or building on the map.
- Enterprise search: Combine map data with campus search tools.
- Custom apps: Build custom map experiences for web or iOS/Android, including Locations, Search, and Wayfinding.
The API is a good fit when you have custom development needs or want more flexibility than the standard map interface. Reach out to your Partner Success Manager to explore how it can support your project.
FAQs
Q: Is Concept3D’s API complete?
A: Yes. Concept3D has a complete API for creative, flexible customizations. The API is private, and access must be granted. It exposes data created in the CMS and is the same API that powers the Front End Map.
Q: Is API documentation available to view?
A: Yes. Contact your Partner Success Manager to request access to the API documentation.
Q: What do I need to interact with the API?
A: For publicly available maps, you need a Map ID and an API Key from Concept3D support. For Front End Authenticated Maps, additional documentation is available for obtaining an authentication token.
Q: Is there an extra cost?
A: Yes. There is an additional cost to access the Concept3D API. For pricing details, contact your Account Executive or Partner Success Manager.
Q: Can I restrict a location request or search query to a particular category?
A: Yes. Toggle the non-visible or private settings on a category in the CMS. Locations under those categories are not returned by the API.
Q: Does the API include building footprints, parking areas, and other campus geometry?
A: Yes. The API can return the locations managed in your CMS, including buildings, parking areas, and other published campus features. Where a location has a polygon or polyline on the map, the API includes that geometry along with coordinates.
The data is returned as JSON. A GIS team can convert that JSON into GeoJSON, shapefile, or another format if needed.
A few things to know:
- The API is built for custom applications, search, and data sync. It is not a hosted GIS service.
- We do not currently offer shapefile, File Geodatabase, or ArcGIS feature-service exports.
- Campus artwork and overlay layers are image tiles, not vector GIS layers.
- Locations in private or non-visible categories are not returned.
If JSON from the API would not meet your GIS needs, contact your Partner Success Manager. Other data export formats may be possible to explore.
Q: What data is returned from wayfinding results?
A: The wayfinding API calculates the shortest distance between two points. Give it two points, and it returns the route as an array of coordinates. You can use that to display the route in a custom implementation.
Q: I get a 400 Bad Request error when pulling wayfinding data. What should I do?
A: Confirm that wayfinding has been added to your map. If the map is still in production, wayfinding nodes may not be available until after the second round of revisions. If wayfinding is active and the issue persists, contact Concept3D support.