> ## Documentation Index
> Fetch the complete documentation index at: https://docs.appsignal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List site edges

For how action and site edges differ, see [Querying traces](https://docs.appsignal.com/api/v2/traces.md#service-dependency-edges).

```yaml POST /api/v2/tracing/site_edges theme={null}
openapi: 3.1.0
info:
  title: AppSignal V2 API
  description: >-
    REST API for metrics, traces, logs, Kubernetes monitoring, and deployment
    tracking.
  license:
    name: ''
  version: 0.1.0
paths:
  /api/v2/tracing/site_edges:
    post:
      tags:
        - Tracing
      summary: List site edges
      operationId: site_edges
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SiteEdgesApiQuery'
            example:
              site_id: abc123
              from: '2024-01-01T00:00:00Z'
              to: '2024-01-01T01:00:00Z'
        required: true
      responses:
        '200':
          description: The site's service edges, grouped by direction.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SiteEdgesResponse'
              example:
                upstream: []
                downstream:
                  - site_id: def456
                    site_name: Billing
                    site_environment: production
                    service: Billing
                    count: 800
                    error_count: 2
                    mean: 35.2
                    p_90: 70
                    p_95: 95.3
                internal: []
        '400':
          description: Malformed request, or input the server cannot process.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BadRequestResponse'
        '401':
          description: Missing or invalid authentication token.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Route or resource not found.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '429':
          description: External query concurrency limit exceeded; retry shortly.
          headers:
            Retry-After:
              schema:
                type: integer
              description: Seconds to wait before retrying.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TooManyRequestsResponse'
        '500':
          description: Unhandled server-side failure.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - bearer_auth: []
        - token_query: []
components:
  schemas:
    BadRequestResponse:
      type: object
      description: >-
        Standard body for HTTP 400 Bad Request responses. Branch on the stable
        `error` slug, display `message` as-is, and read per-error structured
        data from `details`.
      required:
        - error
        - message
      properties:
        error:
          type: string
          description: Stable, machine-readable slug identifying the specific error case.
        message:
          type: string
          description: Human-readable message. Safe to log or display to end users.
        details:
          description: >-
            Per-error structured payload. Shape varies by
            [`error`](Self::error).
    ErrorResponse:
      type: object
      description: Error body returned for 401, 404 and 500 responses.
      required:
        - error
      properties:
        error:
          type: string
          description: Human-readable error message.
    SiteEdge:
      type: object
      description: |-
        A single service-level edge for the site dependency map. Unlike
        `ActionEdge`, this is aggregated across all actions in a service and
        carries no namespace or action name.
      required:
        - service
        - count
        - error_count
        - mean
        - p_90
        - p_95
      properties:
        site_id:
          type:
            - string
            - 'null'
          description: Site ID of the peer service if accessible to the user, else `None`.
        site_name:
          type:
            - string
            - 'null'
          description: Current display name of the peer site, if accessible to the user.
        site_environment:
          type:
            - string
            - 'null'
          description: >-
            Environment of the peer site (e.g. "production"), if accessible to
            the user.
        service:
          type: string
          description: Peer service name (app name on the other end of the edge).
        count:
          type: integer
          format: u-int64
          description: Total request count over the time range.
          minimum: 0
        error_count:
          type: integer
          format: u-int64
          description: Total error count over the time range.
          minimum: 0
        mean:
          type: number
          format: double
          description: Mean duration in milliseconds (count-weighted across the range).
        p_90:
          type: number
          format: double
          description: >-
            90th percentile duration in milliseconds. Approximation:
            traffic-weighted

            average of per-minute pre-computed p_90 values (sum(p_90 * count) /
            sum(count)).
        p_95:
          type: number
          format: double
          description: >-
            95th percentile duration in milliseconds. Approximation:
            traffic-weighted

            average of per-minute pre-computed p_95 values (sum(p_95 * count) /
            sum(count)).
    SiteEdgesApiQuery:
      type: object
      description: Query parameters for listing site-level service dependency edges.
      required:
        - site_id
        - from
        - to
      properties:
        site_id:
          type: string
          description: Site ID that anchors the query.
        from:
          type: string
          format: date-time
          description: Start of the time range (inclusive).
        to:
          type: string
          format: date-time
          description: End of the time range (exclusive).
    SiteEdgesResponse:
      type: object
      description: Response shape for the site edges endpoint.
      required:
        - upstream
        - downstream
        - internal
      properties:
        upstream:
          type: array
          items:
            $ref: '#/components/schemas/SiteEdge'
          description: External services calling into this site (upstream).
        downstream:
          type: array
          items:
            $ref: '#/components/schemas/SiteEdge'
          description: External services this site calls (downstream).
        internal:
          type: array
          items:
            $ref: '#/components/schemas/SiteEdge'
          description: >-
            Internal services this site calls within itself (both sides share
            the focused site_id).
    TooManyRequestsResponse:
      type: object
      description: Error body returned for 429 responses.
      required:
        - error
      properties:
        error:
          type: string
          description: Human-readable error message.
        suggestion:
          type:
            - string
            - 'null'
          description: >-
            A cheaper way to write the request's filter. Only the trace list

            endpoints set it, and only for a filter with a known indexed
            rewrite.
  securitySchemes:
    bearer_auth:
      type: http
      scheme: bearer
      description: '`Authorization: Bearer <token>`'
    token_query:
      type: apiKey
      in: query
      name: token
      description: >-
        Alternative to the Authorization header: pass the token as a
        `?token=<token>` query parameter.
```


## API Specification

The full API specification for this endpoint is available in the [documentation index](https://docs.appsignal.com/llms.txt).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.