The service map API gives you a programmatic interface to the dependency graph that underlies your infrastructure. By registering services and their relationships, you enable the platform to calculate blast radius when an incident occurs, surface downstream impact for any given service, and render an accurate topology view for your team. Changes made through the API are reflected in the visual service map immediately. All requests require a Bearer token in theDocumentation Index
Fetch the complete documentation index at: https://docs.scrubbe.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorization header.
Get full topology
GET https://your-api-domain.com/api/v1/service-map/topology
Returns the entire service dependency graph as a list of nodes and directed edges. Useful for rendering a complete topology visualization.
Response fields
All registered services.
Directed dependency relationships between services.
List all services
GET https://your-api-domain.com/api/v1/service-map
Returns a flat list of all registered services without edge data.
Response fields
Array of service objects.
Get a service
GET https://your-api-domain.com/api/v1/service-map/:id
Retrieves the full record for a single service.
Path parameters
The unique identifier of the service.
Get downstream impact
GET https://your-api-domain.com/api/v1/service-map/:id/downstream-impact
Returns all services that directly or transitively depend on the specified service. Use this before making changes to understand blast radius.
Path parameters
The unique identifier of the upstream service to analyze.
Response fields
Services that would be affected if the target service degrades or goes offline.
Create a service
POST https://your-api-domain.com/api/v1/service-map
Registers a new service in the service map. After creation, add dependencies with POST /dependencies.
Request body
A unique, human-readable name for the service.
A short description of the service’s role.
The team slug responsible for this service.
Response fields
Server-assigned unique identifier for the new service.
The service name.
ISO 8601 creation timestamp.
Add a dependency
POST https://your-api-domain.com/api/v1/service-map/dependencies
Declares a dependency relationship between two registered services. The sourceId service depends on the targetId service.
Request body
The ID of the downstream (dependent) service.
The ID of the upstream (depended-upon) service.
Response fields
Unique identifier for the new dependency record.
The dependent service ID.
The upstream service ID.
Update a service
PATCH https://your-api-domain.com/api/v1/service-map/:id
Partially updates a service record. Only fields included in the request body are modified.
Path parameters
The unique identifier of the service to update.
Request body
New name for the service.
Updated description.
Updated owning team slug.
Delete a service
DELETE https://your-api-domain.com/api/v1/service-map/:id
Removes a service and all of its dependency relationships from the service map.
Path parameters
The unique identifier of the service to delete.
Delete a dependency
DELETE https://your-api-domain.com/api/v1/service-map/dependencies/:depId
Removes a single dependency relationship. The services themselves are not affected.
Path parameters
The unique identifier of the dependency to remove.