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

# Get a building slice

> What a local building’s node pulls to run it: pipeline, policy, project and office ids.


## OpenAPI

```yaml openapi.json get /v1/companies/{campus}/buildings/{building}/slice
openapi: 3.1.0
info:
  title: Ocean One API
  version: 2.4.0
servers:
  - url: https://api.plungeai.com
paths:
  /v1/companies/{campus}/buildings/{building}/slice:
    get:
      operationId: get-v1-companies-campus-buildings-building-slice
      tags:
        - Companies
      summary: A local building’s slice
      description: "The compiled pipeline, policy, project and office ids of one `location: local` building: what its node pulls to run it."
      security:
        - ozkBearer: []
      parameters:
        - name: campus
          in: path
          required: true
          schema:
            type: string
          description: The company’s slug (`plunge`), never a row id
        - name: building
          in: path
          required: true
          schema:
            type: string
          description: The building’s slug
        - name: format
          in: query
          schema:
            type: string
            enum:
              - json
              - yaml
              - markdown
              - text
          description: Response format; overrides Accept (an unknown value is 400 invalid_format)
      responses:
        "200":
          description: The slice Response format negotiates via the `format` field, an Accept header (application/json, text/yaml, text/markdown, text/plain), or the request Content-Type mirror; default JSON.
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
            text/yaml:
              schema:
                type: string
            text/markdown:
              schema:
                type: string
            text/plain:
              schema:
                type: string
        "400":
          description: invalid_format — format must be one of json, yaml, markdown, text
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "401":
          description: unauthorized — missing, invalid or revoked ozk_ key
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "404":
          description: "company_not_found — no company with that slug for this account (a foreign slug answers the same); or no such building in this company; not_found — no route for this method on this path: every other method answers it"
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "502":
          description: upstream_error — the company service is unavailable; retry
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "503":
          description: not_enabled — the company service is not deployed on this tier
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
components:
  schemas:
    Error:
      type: object
      description: Standard error envelope. Every error response also carries an `X-Error-Code` response header equal to error.code, so a client branches on the header regardless of the negotiated body format (json | yaml | markdown | text). When the request created an execution, the `X-Execution-Id` response header is also set. Errors follow the negotiated format like success bodies.
      properties:
        error:
          type: object
          properties:
            code:
              type: string
            message:
              type: string
            connect:
              type: object
              description: "On a 424 connection_required / credential_required: where the missing connection is made."
              properties:
                provider:
                  type: string
                method:
                  type: string
                  enum:
                    - oauth
                    - api_key
                    - wallet
                link:
                  type: string
                  example: POST /v1/connections/stripe/link
          required:
            - code
            - message
          additionalProperties: true
      required:
        - error
  securitySchemes:
    ozkBearer:
      type: http
      scheme: bearer
      description: "ozk_ platform API key (Authorization: Bearer ozk_…)"
```