MMoovlis Routing API
GET /healthz
Interactive API documentation

Routing API

Self-hosted OSRM routing for Texas. Explore the available endpoints or try a route request directly from this page.

Base URL

Available profiles

Separate MLD graphs optimized for each travel mode.

driving · cycling · walking

Authentication

Route operations require a bearer token. Health and documentation remain public.

Authorization: Bearer …

Try a route

Coordinates use longitude, latitude order, as required by OSRM.

GET /route/v1/{profile}/{coordinates} Route between two coordinates

Enter two points and the API will calculate a route using the selected profile. The example defaults to two points in Austin, Texas.

profilepath parameter
startlongitude, latitude
destinationlongitude, latitude
Request URL will appear here.
Response

        

      

    


    
Operations
All endpoints accept the profile-specific paths shown below.

    

      
GET/healthz
Returns the routing service health status.

      
GET/route/v1/{profile}/{coordinates}
Calculate the fastest route between coordinate pairs.

      
GET/nearest/v1/{profile}/{coordinates}
Find the nearest routable point for each coordinate.

      
GET/table/v1/{profile}/{coordinates}
Return a duration and distance matrix between coordinates.

      
GET/match/v1/{profile}/{coordinates}
Snap a sequence of coordinates to the road network.

    


    
Coordinate order matters: use longitude,latitude, not latitude first. For example: -97.7431,30.2672;-97.7266,30.2711.