Skip to content

API Tara: delivery ​

Projects section on the Portal (delivery metrics read from Ryoma, filtered by organization)

This page is generated from openapi.yaml by npm run gen, so do not edit it by hand. Authentication is described on the overview page.

GET/v1/delivery/projects

Projects in my scope, with delivery health from Ryoma

Tara reads Ryoma (/v1/orgs/{org}/projects, /v1/orgs/{org}/delivery/health) on behalf of the caller, with a short-lived read-only delegation token bound to the caller and the current organization. Ryoma only returns that organization's projects, so every role of the organization sees them all and platform staff get no implicit access to a customer organization. The result is cached briefly (45 seconds) per organization on the Tara side. Repos not linked to a project are not in the list.

Responses ​

CodeDescriptionType
200List of projectsapplication/json · object
401Not signed inapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "syncedAt": "2026-11-01T00:00:00Z",
  "items": [
    {
      "key": "string",
      "name": "string",
      "org": "string",
      "repos": [],
      "todo": 0,
      "inProgress": 0,
      "review": 0,
      "rejected": 0,
      "done": 0,
      "tasks": 0,
      "approved": 0,
      "tested": 0,
      "rejections": 0,
      "costUsd": 0,
      "riskCount": 0
    }
  ]
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/projects" \
  -H "Authorization: Bearer $TARA_TOKEN"
GET/v1/delivery/projects/{key}

Details of a project (delivery health and at-risk tasks)

Returns 404 both when the project does not exist and when it is outside the caller's scope (existence is not revealed).

Parameters ​

NameInTypeRequiredDescription
keypathstringyes

Responses ​

CodeDescriptionType
200Project detailsapplication/json · object + object
401Not signed inapplication/problem+json · object
404This project is not in your scopeapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "key": "string",
  "name": "string",
  "org": "string",
  "repos": [
    {
      "url": "string",
      "fullName": "string",
      "bandumUrl": "string"
    }
  ],
  "todo": 0,
  "inProgress": 0,
  "review": 0,
  "rejected": 0,
  "done": 0,
  "tasks": 0,
  "approved": 0,
  "tested": 0,
  "rejections": 0,
  "costUsd": 0,
  "riskCount": 0,
  "syncedAt": "2026-11-01T00:00:00Z",
  "risks": [
    {
      "repo": "string",
      "key": "string",
      "title": "string",
      "url": "string",
      "status": "string",
      "level": "string",
      "kind": "string",
      "detail": "string",
      "costUsd": 0
    }
  ]
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/projects/<key>" \
  -H "Authorization: Bearer $TARA_TOKEN"
GET/v1/delivery/projects/{key}/quality

Data quality warnings of a project, each with how to fix it

Why the Flow numbers of this project may be wrong: tasks closed without type: (coverage below 70%) or without level:, repos outside the GitHub App installation, repos missing the standard labels, and machines that sent no telemetry in the last 7 days. Taken from Ryoma /v1/projects/{key}/quality with the caller's delegation token, so the names of people (items of telemetry_silent) are only present for owners and admins; other roles get the count. Not cached. ph ryoma report --project <key> prints the same warnings. A warning disappears at the next sync after the cause is fixed. Same scope as the project details: 404 when the project does not exist or is outside the scope.

Parameters ​

NameInTypeRequiredDescription
keypathstringyes

Responses ​

CodeDescriptionType
200Warnings (empty list when the data is in good shape)application/json · object
401Not signed inapplication/problem+json · object
404This project is not in your scopeapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "project": "string",
  "checkedAt": "2026-11-01T00:00:00Z",
  "warnings": [
    {
      "code": "type_coverage_low",
      "message": "string",
      "count": 0,
      "total": 0,
      "fix": {}
    }
  ]
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/projects/<key>/quality" \
  -H "Authorization: Bearer $TARA_TOKEN"
GET/v1/delivery/projects/{key}/releases

Releases of a project with release wait time and AI cost per release

Taken from Ryoma /v1/projects/{key}/releases with the caller's delegation token. Release wait time (waitHours) is the time from the moment the release candidate was ready (the latest Approved or closing time of its tasks) to the moment the tag was created; it is one segment of the Flow time of those tasks, not the DORA "lead time for changes". AI cost per release (costUsd) is the sum of the AI cost of the release's tasks. Both are per release, never per person. Releases made outside Bandum have no approval record and show note: no_record without numbers. An empty list also means the repository's source-control kit has no release group yet. Same scope as the project details: 404 when the project does not exist or is outside the scope. ph insights releases --project <key> prints the same data.

Parameters ​

NameInTypeRequiredDescription
keypathstringyes
limitqueryintegerNewest releases to return (default 20, at most 100)

Responses ​

CodeDescriptionType
200Releases, newest firstapplication/json · object
400Invalid limitapplication/problem+json · object
401Not signed inapplication/problem+json · object
404This project is not in your scopeapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "project": "string",
  "total": 0,
  "waitMedianHours": 0,
  "waitP85Hours": 0,
  "items": [
    {
      "repo": "string",
      "tag": "v1.4.0",
      "version": "1.4.0",
      "sha": "string",
      "at": "2026-11-01T00:00:00Z",
      "tasks": 0,
      "missingTasks": 0,
      "lateTasks": 0,
      "tasksWithAi": 0
    }
  ]
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/projects/<key>/releases" \
  -H "Authorization: Bearer $TARA_TOKEN"
GET/v1/delivery/projects/{key}/flow

Flow Framework of a project (velocity, flow time, efficiency, load, distribution)

Weekly Flow report of the project, taken from Ryoma /v1/flow. Same scope as the project details: returns 404 both when the project does not exist and when it is outside the scope. Tara calls Ryoma on behalf of the caller (delegation token), caches briefly (45 seconds) per (project, weeks) and returns Ryoma's structure unchanged.

Parameters ​

NameInTypeRequiredDescription
keypathstringyes
weeksqueryintegerMost recent weeks, including the current week

Responses ​

CodeDescriptionType
200Reportapplication/json · object
400weeks outside 1..52application/problem+json · object
401Not signed inapplication/problem+json · object
404This project is not in your scopeapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "syncedAt": "2026-11-01T00:00:00Z",
  "from": "2026-11-01T00:00:00Z",
  "to": "2026-11-01T00:00:00Z",
  "weeks": [
    {
      "velocity": 0,
      "flowTimeMedianHours": 0,
      "flowTimeP85Hours": 0,
      "flowEfficiency": 0,
      "byType": {},
      "week": "string",
      "distribution": {}
    }
  ],
  "total": {
    "velocity": 0,
    "flowTimeMedianHours": 0,
    "flowTimeP85Hours": 0,
    "flowEfficiency": 0,
    "byType": {}
  },
  "wip": {
    "total": 0,
    "byType": {}
  }
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/projects/<key>/flow" \
  -H "Authorization: Bearer $TARA_TOKEN"
GET/v1/delivery/projects/{key}/ai

AI measurement framework of a project (Utilization, Impact, Cost, trends)

AI report of the project, taken from Ryoma /v1/ai. AI impact is correlation, not causation. Same scope as the project details: returns 404 both when the project does not exist and when it is outside the scope. Tara calls Ryoma on behalf of the caller (delegation token), caches briefly (45 seconds) per (project, weeks) and returns Ryoma's structure unchanged.

Parameters ​

NameInTypeRequiredDescription
keypathstringyes
weeksqueryintegerMost recent weeks, including the current week

Responses ​

CodeDescriptionType
200Reportapplication/json · object
400weeks outside 1..52application/problem+json · object
401Not signed inapplication/problem+json · object
404This project is not in your scopeapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "syncedAt": "2026-11-01T00:00:00Z",
  "project": "string",
  "org": "string",
  "from": "2026-11-01T00:00:00Z",
  "to": "2026-11-01T00:00:00Z",
  "weeks": [
    {
      "activeAiUsers": 0,
      "doneItems": 0,
      "itemsWithAi": 0,
      "itemsWithAiShare": 0,
      "costUsd": 0,
      "reworkCostUsd": 0,
      "week": "string"
    }
  ],
  "utilization": {
    "activeAiUsers": 0,
    "doneItems": 0,
    "itemsWithAi": 0,
    "itemsWithAiShare": 0,
    "costUsd": 0,
    "reworkCostUsd": 0
  },
  "impact": {
    "minGroupSize": 0,
    "total": {
      "withAi": {},
      "withoutAi": {}
    },
    "byType": {}
  },
  "trend": [
    {
      "month": "string",
      "doneItems": 0,
      "itemsWithAiShare": 0,
      "flowTimeMedianHours": 0
    }
  ],
  "cost": {
    "attributedUsd": 0,
    "reworkCostUsd": 0,
    "reworkShare": 0,
    "costBeforeFirstRejection": 0,
    "costAfterFirstRejection": 0,
    "perDoneItem": {
      "doneItems": 0,
      "costUsd": 0,
      "costPerDoneItem": 0
    }
  }
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/projects/<key>/ai" \
  -H "Authorization: Bearer $TARA_TOKEN"
GET/v1/delivery/projects/{key}/baseline

Flow before and after the project started using AI

Compares the Flow numbers (velocity per week, flow time p50 and p85, flow efficiency, flow load) and the first-pass and rework rates of the N weeks before the project's adoption date with the N weeks after it, from the synced task history. The adoption date is, by default, the first day Ryoma received telemetry for the project's repos; an organization owner or admin can set it (PUT). before and after are absent while there is no adoption date. warnings say when the comparison is not reliable (before_sample_small: fewer than minSample = 10 finished tasks before). Taken from Ryoma /v1/projects/{key}/baseline on behalf of the caller, cached briefly (45 seconds), same scope as the project details. A correlation, not causation; measured per project, never per person. ph insights flow --compare prints the same.

Parameters ​

NameInTypeRequiredDescription
keypathstringyes
weeksqueryintegerLength of each period in weeks (the period before and the same length after the adoption date)

Responses ​

CodeDescriptionType
200Adoption date and comparisonapplication/json · object
400Invalid parametersapplication/problem+json · object
401Not signed inapplication/problem+json · object
404This project is not in your organizationapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "project": "string",
  "name": "string",
  "weeks": 0,
  "adoptedAt": "string",
  "source": "telemetry",
  "minSample": 0,
  "warnings": [
    {
      "code": "no_adoption_date",
      "message": "string"
    }
  ]
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/projects/<key>/baseline" \
  -H "Authorization: Bearer $TARA_TOKEN"
PUT/v1/delivery/projects/{key}/baseline

Set the date the project started using AI (organization owner and admin)

Overrides the default (first telemetry). Only the calendar date is kept. Returns the comparison with the new date. ph project adoption <key> --set YYYY-MM-DD does the same.

Parameters ​

NameInTypeRequiredDescription
keypathstringyes

Body (application/json) ​

FieldTypeRequiredDescription
adoptedAtstring (date)yesDate the project started using AI (YYYY-MM-DD), from 2020-01-01

Responses ​

CodeDescriptionType
200Savedapplication/json · object
400Invalid parametersapplication/problem+json · object
401Not signed inapplication/problem+json · object
403Not allowedapplication/problem+json · object
404This project is not in your organizationapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "project": "string",
  "name": "string",
  "weeks": 0,
  "adoptedAt": "string",
  "source": "telemetry",
  "minSample": 0,
  "warnings": [
    {
      "code": "no_adoption_date",
      "message": "string"
    }
  ]
}

Call with curl ​

bash
curl -X PUT "https://tara.phillipcli.cloud/v1/delivery/projects/<key>/baseline" \
  -H "Authorization: Bearer $TARA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"adoptedAt":"string"}'
DELETE/v1/delivery/projects/{key}/baseline

Go back to the default adoption date, the first telemetry (organization owner and admin)

ph project adoption <key> --reset does the same.

Parameters ​

NameInTypeRequiredDescription
keypathstringyes

Responses ​

CodeDescriptionType
200Resetapplication/json · object
401Not signed inapplication/problem+json · object
403Not allowedapplication/problem+json · object
404This project is not in your organizationapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "project": "string",
  "name": "string",
  "weeks": 0,
  "adoptedAt": "string",
  "source": "telemetry",
  "minSample": 0,
  "warnings": [
    {
      "code": "no_adoption_date",
      "message": "string"
    }
  ]
}

Call with curl ​

bash
curl -X DELETE "https://tara.phillipcli.cloud/v1/delivery/projects/<key>/baseline" \
  -H "Authorization: Bearer $TARA_TOKEN"
GET/v1/delivery/report

Monthly report of the organization or of one project, as JSON, CSV or a one-page PDF

The exportable monthly report: AI cost per approved task, first-time approval rate, rework, flow time and velocity of the month, compared with the weeks before the adoption date, plus data-quality caveats and a plain-language summary (PDF). Every role of the organization can read it. No per-person numbers. format=json (default) returns the figures; format=csv returns the weekly data (one row per project and Monday week touching the month; UTF-8 with a byte order mark); format=pdf returns a one-page A4 PDF generated by Tara from the same figures (embedded font with Vietnamese diacritics, generation date, period, data-quality notes), in English or Vietnamese (lang). The current month is partial (up to today). Taken from Ryoma /v1/insights/report on behalf of the caller. ph insights report --month 2026-12 --format pdf does the same.

Parameters ​

NameInTypeRequiredDescription
monthquerystringyesMonth as YYYY-MM; not in the future
projectquerystringProject key; leave empty for the whole organization
weeksqueryintegerLength of the period before AI, in weeks
formatqueryjson | csv | pdf
langqueryen | viLanguage of the PDF (labels, the "In short" summary and the data notes); numbers are the same. Tara does not store the Portal language, so the Portal and ph insights report --lang send it; absent means en. Ignored for json and csv (column names stay machine-readable).

Responses ​

CodeDescriptionType
200The report in the requested formatapplication/json · object
400Invalid parametersapplication/problem+json · object
401Not signed inapplication/problem+json · object
403Not allowedapplication/problem+json · object
404This project is not in your organizationapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "month": "string",
  "from": "string",
  "to": "string",
  "partial": false,
  "org": "string",
  "baselineWeeks": 0,
  "minSample": 0,
  "summary": {
    "from": "string",
    "to": "string",
    "days": 0,
    "done": 0,
    "tested": 0
  },
  "projects": [
    {
      "project": "string",
      "name": "string",
      "adoptedAt": "string",
      "source": "telemetry",
      "month": {},
      "weeks": []
    }
  ],
  "caveats": [
    {
      "project": "string",
      "code": "string",
      "message": "string"
    }
  ]
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/report?month=string" \
  -H "Authorization: Bearer $TARA_TOKEN"
GET/v1/delivery/insights/overview

Organization overview - one row per project with the main Flow and AI numbers of a period

Dashboards in the Portal ("Insights"). Taken from Ryoma /v1/insights/overview on behalf of the caller (delegation token bound to the caller and the current organization), so only the organization's data is returned. Every role of the organization can read it. Cached briefly (45 seconds) per organization and query. The period is weeks (default 8) or from..to (dates, rounded to whole weeks starting Monday; at most 51 weeks).

Parameters ​

NameInTypeRequiredDescription
projectquerystringProject key; leave empty for the whole organization
weeksqueryintegerMost recent weeks, including the current week (ignored when from is set)
fromquerystring (date)First day of the range (YYYY-MM-DD)
toquerystring (date)Last day of the range (YYYY-MM-DD, included); default today. Only used with from.

Responses ​

CodeDescriptionType
200Overviewapplication/json · object
400Invalid rangeapplication/problem+json · object
401Not signed inapplication/problem+json · object
403Not a member of an organizationapplication/problem+json · object
404This project is not in your organizationapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "syncedAt": "2026-11-01T00:00:00Z",
  "from": "2026-11-01T00:00:00Z",
  "to": "2026-11-01T00:00:00Z",
  "projects": [
    {
      "project": "string",
      "name": "string",
      "velocity": 0,
      "wip": 0,
      "aiCostUsd": 0,
      "activeAiUsers": 0,
      "risks": 0
    }
  ]
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/insights/overview" \
  -H "Authorization: Bearer $TARA_TOKEN"
GET/v1/delivery/insights/flow

Flow Framework of the organization or of one project (velocity, flow time, efficiency, load, distribution)

Same report as /v1/delivery/projects/{key}/flow but for all projects of the organization when project is empty, over a range of weeks or dates. Taken from Ryoma /v1/flow.

Parameters ​

NameInTypeRequiredDescription
projectquerystringProject key; leave empty for the whole organization
weeksqueryintegerMost recent weeks, including the current week (ignored when from is set)
fromquerystring (date)First day of the range (YYYY-MM-DD)
toquerystring (date)Last day of the range (YYYY-MM-DD, included); default today. Only used with from.

Responses ​

CodeDescriptionType
200Reportapplication/json · object
400Invalid rangeapplication/problem+json · object
401Not signed inapplication/problem+json · object
403Not a member of an organizationapplication/problem+json · object
404This project is not in your organizationapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "syncedAt": "2026-11-01T00:00:00Z",
  "from": "2026-11-01T00:00:00Z",
  "to": "2026-11-01T00:00:00Z",
  "weeks": [
    {
      "velocity": 0,
      "flowTimeMedianHours": 0,
      "flowTimeP85Hours": 0,
      "flowEfficiency": 0,
      "byType": {},
      "week": "string",
      "distribution": {}
    }
  ],
  "total": {
    "velocity": 0,
    "flowTimeMedianHours": 0,
    "flowTimeP85Hours": 0,
    "flowEfficiency": 0,
    "byType": {}
  },
  "wip": {
    "total": 0,
    "byType": {}
  }
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/insights/flow" \
  -H "Authorization: Bearer $TARA_TOKEN"
GET/v1/delivery/insights/ai

AI measurement framework of the organization or of one project (Utilization, Impact, Cost, trend)

Same report as /v1/delivery/projects/{key}/ai but for all projects of the organization together when project is empty. Taken from Ryoma /v1/ai. AI impact is correlation, not causation. Default 12 weeks.

Parameters ​

NameInTypeRequiredDescription
projectquerystringProject key; leave empty for the whole organization
weeksqueryintegerMost recent weeks, including the current week (ignored when from is set)
fromquerystring (date)First day of the range (YYYY-MM-DD)
toquerystring (date)Last day of the range (YYYY-MM-DD, included); default today. Only used with from.

Responses ​

CodeDescriptionType
200Reportapplication/json · object
400Invalid rangeapplication/problem+json · object
401Not signed inapplication/problem+json · object
403Not a member of an organizationapplication/problem+json · object
404This project is not in your organizationapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "syncedAt": "2026-11-01T00:00:00Z",
  "project": "string",
  "org": "string",
  "from": "2026-11-01T00:00:00Z",
  "to": "2026-11-01T00:00:00Z",
  "weeks": [
    {
      "activeAiUsers": 0,
      "doneItems": 0,
      "itemsWithAi": 0,
      "itemsWithAiShare": 0,
      "costUsd": 0,
      "reworkCostUsd": 0,
      "week": "string"
    }
  ],
  "utilization": {
    "activeAiUsers": 0,
    "doneItems": 0,
    "itemsWithAi": 0,
    "itemsWithAiShare": 0,
    "costUsd": 0,
    "reworkCostUsd": 0
  },
  "impact": {
    "minGroupSize": 0,
    "total": {
      "withAi": {},
      "withoutAi": {}
    },
    "byType": {}
  },
  "trend": [
    {
      "month": "string",
      "doneItems": 0,
      "itemsWithAiShare": 0,
      "flowTimeMedianHours": 0
    }
  ],
  "cost": {
    "attributedUsd": 0,
    "reworkCostUsd": 0,
    "reworkShare": 0,
    "costBeforeFirstRejection": 0,
    "costAfterFirstRejection": 0,
    "perDoneItem": {
      "doneItems": 0,
      "costUsd": 0,
      "costPerDoneItem": 0
    }
  }
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/insights/ai" \
  -H "Authorization: Bearer $TARA_TOKEN"
GET/v1/delivery/insights/health

Delivery health by project and at-risk tasks

Task counts by status, first-pass approval, rework, time in each status and the at-risk tasks of every project (and of repos not linked to a project, with an empty project). Not tied to a period: it describes the work as it is now. Taken from Ryoma /v1/delivery/health.

Parameters ​

NameInTypeRequiredDescription
projectquerystringProject key; leave empty for the whole organization

Responses ​

CodeDescriptionType
200Healthapplication/json · object
400Invalid rangeapplication/problem+json · object
401Not signed inapplication/problem+json · object
403Not a member of an organizationapplication/problem+json · object
404This project is not in your organizationapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "syncedAt": "2026-11-01T00:00:00Z",
  "projects": [
    {
      "project": "string",
      "name": "string",
      "tasks": 0,
      "todo": 0,
      "inProgress": 0,
      "review": 0,
      "rejected": 0,
      "done": 0,
      "approved": 0,
      "tested": 0,
      "rejections": 0,
      "costUsd": 0,
      "risks": []
    }
  ]
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/insights/health" \
  -H "Authorization: Bearer $TARA_TOKEN"
GET/v1/delivery/insights/guardrails

What Guardrails blocked, asked about and masked, by project and rule (counts, never names)

Taken from Ryoma /v1/guardrails. Every role of the organization can read it. The period is from..to (dates, included) or the last days days (default 30).

Parameters ​

NameInTypeRequiredDescription
projectquerystringProject key; leave empty for the whole organization
daysqueryinteger
fromquerystring (date)First day of the range (YYYY-MM-DD)
toquerystring (date)Last day of the range (YYYY-MM-DD, included); default today. Only used with from.

Responses ​

CodeDescriptionType
200Reportapplication/json · object
400Invalid rangeapplication/problem+json · object
401Not signed inapplication/problem+json · object
403Not a member of an organizationapplication/problem+json · object
404This project is not in your organizationapplication/problem+json · object
502Ryoma failed or rejected the delegation tokenapplication/problem+json · object
503Tara is not connected to Ryoma (TARA_RYOMA_URL)application/problem+json · object

Example response ​

json
{
  "from": "2026-11-01T00:00:00Z",
  "to": "2026-11-01T00:00:00Z",
  "rows": [
    {
      "project": "string",
      "rule": "string",
      "decision": "string",
      "count": 0,
      "users": 0
    }
  ]
}

Call with curl ​

bash
curl "https://tara.phillipcli.cloud/v1/delivery/insights/guardrails" \
  -H "Authorization: Bearer $TARA_TOKEN"