---
title: "Get Binding For Path"
method: GET
path: "/datamate-project-bindings/by-path"
tags: ["DatamateProjectBindings"]
---

# Get Binding For Path

`GET /datamate-project-bindings/by-path`

Path-identified lookup — symmetric to ``GET /by-remote``.

Path-only bindings are per-user (m1), so this lookup is naturally scoped
to the caller's own row: a coincidentally-identical absolute path belonging
to another user simply 404s. The M1 visibility check still applies (the
lookup could still hit a public workspace bound by someone else via
path-only) — kept for defense-in-depth even though the scoping already
excludes cross-user hits.

## Query parameters

- `project_path` string, required — Absolute project directory path

## Response `200`

Successful Response

- GetBindingResponse — Response for GET /datamate-project-bindings/by-remote.
  - `binding` BindingModel, required — Wire shape returned to the CLI for a single binding row. Either ``repo_remote`` or ``project_path`` is present (at least one; the row's CHECK constraint enforces this). Projects with a git remote use ``repo_remote``; projects without one (materialized sample scaffolds, fresh scratch dirs) use ``project_path`` as the fallback identifier.
    - `id` integer, required
    - `datamate_id` integer, required
    - `datamate_name` string, required
    - `repo_remote` string, nullable
    - `project_path` string, nullable
    - `created_at` string, date-time, nullable
  - `datamate` DatamateRef, required — Minimal datamate reference embedded in binding responses.
    - `id` integer, required
    - `name` string, required

## Other responses

- `400` — Invalid request
- `404` — No workspace linked to this path
- `422` — Validation Error

---

[API](https://skmtc.net/myaltimate/apis/fastapi.md) · [All operations](https://skmtc.net/myaltimate/apis/fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/myaltimate/fastapi/revisions/b9cc757ca795/schema)