Skip to content
Changelog

Report a bug

Graphhopper integration: operations for AI agents

Graphhopper connects to Type.com as an integration. This page lists the 20 operations documented for Claude and Codex in Type.com: 9 read, 10 write, 1 destructive.

About Graphhopper

GraphHopper Directions API provides enterprise-grade routing services, including route planning, optimization, geocoding, and more, for various vehicle types.

Categories: Developer Tools & IT

How to connect Graphhopper to Type.com

Access
Organization connection: one shared account for the workspace.

To add the connection, follow the steps in Space connections.

Documented operations

20 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.

Routing

  • Read

    Calculate a route

    For the GET request you specify the parameters in the URL and can try it directly in every browser. However, it has some disadvantages when using many points (URL length limit) and the custommodel Feature cannot be used.

  • Write

    Calculate a route

    This POST endpoint accepts routing requests as JSON and returns the computed route as JSON. It offers a high degree of customization through the custom model to account for vehicle constraints such as height or weight, avoidance or exclusion of specific areas.

Isochrones

  • Read

    Compute an isochrone

    GET /isochrone

Matrices

  • Read

    Compute a matrix

    For N origins and M destinations, compute routes from all origins to all destinations and output the result as a matrix of travel times and/or distances. This includes the common cases of routes from one origin to many destinations, or from many origins to one destination.

  • Read

    Retrieve result of a matrix computation job

    GET /matrix/solution/{jobId}

  • Write

    Compute a matrix

    Calculate a matrix of travel times and/or distances between N origins and M destinations. This includes the common cases of routes from one origin to many destinations, or from many origins to one destination.

  • Write

    Submit a matrix computation job

    An alternate endpoint for computing a large matrix asynchronously, where a request against the regular endpoint would result in a timeout.

Map Matching

  • Write

    Map-match a GPX file

    To get a match response you send a GPX file in the body of an HTTP POST request and specify request parameters like the key and profile in the URL. See below for more supported parameters.

Geocoding

  • Read

    Geocoding Endpoint

    GET /geocode

Route Optimization

  • Read

    Retrieve solution of a route optimization job

    Take the job id and fetch the solution for the vehicle routing problem from this URL: https://graphhopper.com/api/1/vrp/solution/ ?key= You get the job id by sending a vehicle routing problem to the batch mode URL.

  • Write

    Solve a route optimization problem

    Start by reading the introduction to the Route Optimization API. To solve a new vehicle routing problem, make a HTTP POST to this URL https://graphhopper.com/api/1/vrp?key= It returns the solution to this problem in the JSON response.

  • Write

    Submit a route optimization job

    To solve a vehicle routing problem, perform the following steps: 1.) Make a HTTP POST to this URL https://graphhopper.com/api/1/vrp/optimize?key= It returns a job id (jobid).

Clustering

  • Read

    Retrieve solution of a clustering job

    This endpoint returns the solution of the clustering problems submitted to the Batch Cluster endpoint. You can fetch it with the jobid, you have been sent.

  • Write

    Solve a clustering problem

    The Cluster endpoint is used with a POST request towards https://graphhopper.com/api/1/cluster?key= . The solution will be provided in the JSON response. Please note that for problems that take longer than 10 seconds a bad request error is returned.

  • Write

    Submit a clustering job

    Prefer the synchronous endpoint and use this Batch Cluster endpoint for long running problems only. The work flow is asynchronous: - send a POST request towards https://graphhopper.com/api/1/cluster/calculate?key= and fetch the jobid.

Custom Profiles

  • Read

    List your custom routing profiles

    GET /profiles

  • Read

    Retrieve result of a profile creation job

    GET /profiles/solution/{jobId}

  • Write

    Create a custom routing profile

    POST /profiles

  • Write

    Submit a profile creation job

    An alternate endpoint for computing a profile for a large boundary asynchronously, where a request against the regular endpoint would result in a timeout.

  • Destructive

    Delete a custom routing profile

    DELETE /profiles/{profileId}

See How connections work for access and permissions, or browse all integrations.