User view
Botyard REST API endpoints for user view.
3 endpoints in this group. Every request authenticates with an API key; see the API reference for the other groups.
- Reply User View:
POST /v1/orgs/{org_id}/conversations/{conversation_id}/user-view/{request_id} - Accept User View Act:
POST /v1/orgs/{org_id}/conversations/{conversation_id}/user-view-actions/{request_id}/accept - Report User View Act:
POST /v1/orgs/{org_id}/conversations/{conversation_id}/user-view-actions/{request_id}/result
Get Usage History
Return per-meter quantity time-series for the requested window. Count-meter quantities are pulled from the billing provider, filtered by ``external_customer_id = org_id`` (set on each customer at checkout) so two orgs that share an email can never see each other's usage. Resource-overage series are computed from the allocation ledger so the chart can show the included baseline alongside the overage. Empty ``series`` is normal for orgs without a subscription, for orgs whose customer was created before the ``external_id`` backfill ran, or in local dev where the metering client isn't configured.
Reply User View
Answer a bot's ``get_user_view`` request with the open page's outline. Only the user the request names may answer, only while it is pending, and only once: the first reply wins.