Skip to main content

List Services belonging to a Project

GET/projects/{projectId}/services/
v2
GET
container-list-services

Request

  • projectIdstring (uuid)
    required

    ID of the Project to list Services for.

Responses

application/json

OK

  • Array[
  • *object
    • deployedStateobject
      required

      The actual state of the container that is currently deployed.

      • commandarray of string

        The container command (equivalent to the Docker cmd). When omitted, this defaults to the command defined in the image.

        • Array[
        • *string
        • ]
    • entrypointarray of string

      The container entrypoint (equivalent to the Docker entrypoint). When omitted, this defaults to the entrypoint defined in the image.

      • Array[
      • *string
      • ]
  • envsobject

    Key-value map of environment variables that should be passed into the container.

    • *string
  • imagestring
    required

    The image to run, in the usual format also used by docker run and docker compose. When the image is pulled from a private registry, make sure to create it first, using the container-create-registry endpoint. The appropriate registry is matched by hostname.

  • portsarray of string

    Exposed ports. Follows the format <public-port>:<container-port>/<protocol>. Exposed ports can be accessed from other containers (or managed apps) within the same project. To expose a port publicly, connect it with an ingress resource.

    • Array[
    • *string
    • ]
  • volumesarray of string

    Volume mounts for this container. These items always follow the format <volume>:<mountpoint>. The <volume> may either be a named volume, or a file path in the (always present) project file system (which is shared among containers and managed apps within a project).

    • Array[
    • *string
    • ]
  • descriptionstring
    required
  • idstring (uuid)
    required
  • pendingStateobject
    required

    The desired state that is waiting to be reconciled.

    • commandarray of string

      The container command (equivalent to the Docker cmd). When omitted, this defaults to the command defined in the image.

      • Array[
      • *string
      • ]
  • entrypointarray of string

    The container entrypoint (equivalent to the Docker entrypoint). When omitted, this defaults to the entrypoint defined in the image.

    • Array[
    • *string
    • ]
  • envsobject

    Key-value map of environment variables that should be passed into the container.

    • *string
  • imagestring
    required

    The image to run, in the usual format also used by docker run and docker compose. When the image is pulled from a private registry, make sure to create it first, using the container-create-registry endpoint. The appropriate registry is matched by hostname.

  • portsarray of string

    Exposed ports. Follows the format <public-port>:<container-port>/<protocol>. Exposed ports can be accessed from other containers (or managed apps) within the same project. To expose a port publicly, connect it with an ingress resource.

    • Array[
    • *string
    • ]
  • volumesarray of string

    Volume mounts for this container. These items always follow the format <volume>:<mountpoint>. The <volume> may either be a named volume, or a file path in the (always present) project file system (which is shared among containers and managed apps within a project).

    • Array[
    • *string
    • ]
  • projectIdstring (uuid)
    required
  • serviceNamestring
    required
  • stackIdstring (uuid)
    required
  • statusstring (one of: running, stopped, restarting, error, creating, starting)
    required
  • ]

    Usage examples

    $ curl \
    --fail \
    --location \
    -H "Authorization: Bearer $MITTWALD_API_TOKEN" \
    https://api.mittwald.de/v2/projects/f0f86186-0a5a-45b2-aa33-502777496347/services?stackId=f0f86186-0a5a-45b2-aa33-502777496347