Read-only request-cost reporting: minimum scopes, USD availability, and Get Key response shape #1712
Replies: 4 comments
|
Thanks for asking your question. Please be sure to reply with as much detail as possible so the community can assist you efficiently. |
|
Hey there! It looks like you haven't connected your GitHub account to your Deepgram account. You can do this at https://community.deepgram.com - being verified through this process will allow our team to help you in a much more streamlined fashion. |
|
It looks like we're missing some important information to help debug your issue. Would you mind providing us with the following details in a reply?
|
|
Thanks! Here is the additional context:
We have kept private request IDs and account information out of this public thread. A specific request ID would only be relevant if an engineer needs to investigate account-specific behavior; please let us know whether that is necessary and which private support channel to use. The remaining questions are whether a custom key with exactly We are keeping GitHub account linking separate for now and would appreciate guidance here on these general API questions. Thank you! |
Uh oh!
There was an error while loading. Please reload this page.
We’re building a prerecorded transcription integration and want a separate, read-only credential for per-request cost reporting. I checked the existing discussions and current reference, but have three remaining API-contract questions:
Minimum reporting scopes. The answer in #240 explains that Member keys omit billing information and Admin/Owner keys include it. The roles/scopes documentation also shows
billing:readoutside the Member bundle. ForGET /v1/projects/{project_id}/requests/{request_id}, is a key with exactlyusage:readandbilling:readsufficient to retrieve the request record’sresponse.details.usd? Is any additional scope required, such asproject:read, without granting the full Admin role?USD availability after success. The explanation in #1212 and the log-state documentation explain delayed usage recording. For a successful prerecorded request, is there a documented expected or maximum delay specifically for
usdto become available? Is there a response field/status that distinguishes accounting still pending from permission-based omission? We want bounded polling and to keep a missing amount distinct from a genuine zero.Get-key response envelope. For
GET /v1/projects/{project_id}/keys/{key_id}, the current reference showsitem.member.api_key. A direct HTTP read of existing-key metadata returned root-levelapi_keywith a siblingmember, consistent with the Python SDK v3.11.0 response type. Is this a documentation mismatch, or should direct clients support both envelopes? Which is the supported contract going forward?This is a general integration question; no account-specific billing investigation is needed. Thanks for helping us keep permissions narrow and handle incomplete reporting correctly.
All reactions