다음 몇 가지 사항을 아직 진행하지 않았다면 처음 Cloud Billing 예산 애플리케이션의 코딩을 시작하기 전에 진행해야 합니다.
Google Cloud 콘솔에서 Cloud Billing 기능을 사용해 보세요.
이 API 문서에서는 사용자가 Google Cloud를 사용해 봤으며 Google Cloud 콘솔의 Cloud Billing 기능과 개념에 익숙하다고 가정합니다. Cloud Billing 계정, Google Cloud 프로젝트, Google Cloud제품, Cloud Billing 예산 및 알림에 익숙하지 않다면 코딩을 시작하기 전에 다음을 읽어보세요.
Cloud Billing 계정당 한 번에 예산 수천 개산를 연결할 수 있습니다. 현재 한도와 추가 정보는 할당량 및 한도를 참조하세요.
예산은 한 번에 하나씩만 Cloud Billing 계정에 연결됩니다.
단일 Cloud Billing 계정은 하나 이상의Google Cloud 프로젝트에 연결되고, 비용을 지불합니다.
Google Cloud 프로젝트는 한 번에 하나씩만 Cloud Billing 계정에 연결됩니다.
예산을 만들어서 전체 Cloud Billing 계정의 비용을 모니터링할 수 있으며, 여기에는 이 결제 계정으로 지불되는 모든 Google Cloud 프로젝트가 포함됩니다. 또한 세부적인 예산 필터를 사용해서 비용의 특정 부분을 모니터링하도록 예산 범위를 정의할 수 있습니다.
필터에는 Google Cloud 프로젝트, 서비스, 예산 기간, Cloud Billing 계정에 적용할 수 있는 기타 필터가 포함됩니다.
REST는 데이터 요청 및 수정에 대한 간편하고 일관성 있는 접근 방식을 제공하는 소프트웨어 아키텍처 스타일입니다.
REST는 'Representational State Transfer'의 줄임말로, Google API의 맥락에서 REST는 HTTP 동사를 사용하여 Google이 저장한 데이터 표현을 검색 및 수정하는 방법을 의미합니다.
RESTful 시스템에서는 리소스가 데이터 저장소에 저장되고, 클라이언트는 서버에서 특정 작업(리소스 생성, 검색, 업데이트, 삭제 등)을 수행하라는 요청을 전송하며, 서버는 작업을 수행하고 응답을 전송합니다. 이 응답은 지정된 리소스 표현의 형식을 취하는 경우가 많습니다.
Google의 RESTful API에서는 클라이언트가 POST, GET, PUT 또는 DELETE 등의 HTTP 동사를 사용하여 작업을 지정합니다. 다음과 같은 형식의 전역적으로 고유한 URI를 사용하여 리소스를 지정합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-04-21(UTC)"],[[["\u003cp\u003eFamiliarity with Google Cloud console, Cloud Billing features, and concepts like Cloud Billing accounts, projects, products, and budgets is essential before coding a Cloud Billing budget application.\u003c/p\u003e\n"],["\u003cp\u003eCloud Billing accounts can have thousands of budgets, each linked to one account, and one account can link to multiple Google Cloud projects.\u003c/p\u003e\n"],["\u003cp\u003eYou can monitor costs for an entire Cloud Billing account or specific slices of costs using granular budget filters such as projects and services.\u003c/p\u003e\n"],["\u003cp\u003eThe Cloud Billing Budget API can be invoked via HTTP requests or client libraries, with the API employing RESTful architecture, utilizing HTTP verbs like \u003ccode\u003ePOST\u003c/code\u003e, \u003ccode\u003eGET\u003c/code\u003e, \u003ccode\u003ePUT\u003c/code\u003e, and \u003ccode\u003eDELETE\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe Cloud Billing Budget API uses JSON, a language-independent data format, to return data, providing a simple text representation of arbitrary data structures.\u003c/p\u003e\n"]]],[],null,["# Cloud Billing Budget API Prerequisites\n\n\u003cbr /\u003e\n\nBefore you start coding your first Cloud Billing budget application, there\nare a few things you need to do, if you haven't done them already.\n\nTry out the Cloud Billing features in the Google Cloud console\n--------------------------------------------------------------\n\nThis API documentation assumes that you've used Google Cloud, and\nthat you're familiar with the Cloud Billing features and concepts in\nthe Google Cloud console. If you're not already familiar with concepts like\nCloud Billing accounts, Google Cloud projects, Google Cloud\nproducts, and Cloud Billing budgets and alerts, read the following\nbefore starting to code:\n\n- [Overview of Cloud Billing concepts](/billing/docs/concepts)\n- [Manage your Cloud Billing account](/billing/docs/how-to/manage-billing-account)\n- [View the projects linked to a Cloud Billing account](/billing/docs/how-to/view-linked)\n- [Budgets and budget alert rules](/billing/docs/how-to/budgets)\n- [Access control for the Cloud Billing Budget API](/billing/docs/access-control)\n\nAfter you are familiar with the Cloud Billing features and concepts, try out\nthe [Google Cloud console user interface](https://console.cloud.google.com/).\n\nKey Cloud Billing concepts\n--------------------------\n\n- Each individual Cloud Billing account can have [several thousand budgets](/billing/quotas) associated with it at a time. See [Quotas and limits](/billing/quotas) for the current limits and additional information.\n- A budget is linked to only one Cloud Billing account at a time.\n- A single Cloud Billing account is linked to, and pays for, one or more Google Cloud projects.\n- A Google Cloud project is linked to only one Cloud Billing account at a time.\n- You can create a budget to monitor your costs for an entire Cloud Billing account, including all the Google Cloud projects paid for by that billing account. You can also define the scope of the budget using **granular budget filters** to monitor specific slices of your costs. Filters include Google Cloud projects, services, the budget's time period, and other filters applicable to your Cloud Billing account.\n\nLearn REST basics\n-----------------\n\nThere are two ways to invoke the Cloud Billing Budget API:\n\n- Sending HTTP requests and parsing the responses.\n- Using [client libraries](/billing/docs/reference/budget/libraries) (recommended).\n\nIf you decide not to use client libraries, you'll need to understand the basics\nof REST.\n\nREST is a style of software architecture that provides a convenient and consistent approach to requesting and modifying data.\n\nThe term REST is short for \"[Representational State Transfer](https://en.wikipedia.org/wiki/Representational_state_transfer).\" In the context of Google APIs, it refers to using HTTP verbs to retrieve and modify representations of data stored by Google.\n\nIn a RESTful system, resources are stored in a data store; a client sends a request that the server perform a particular action (such as creating, retrieving, updating, or deleting a resource), and the server performs the action and sends a response, often in the form of a representation of the specified resource.\n\nIn Google's RESTful APIs, the client specifies an action using an HTTP verb such as `POST`, `GET`, `PUT`, or `DELETE`. It specifies a resource by a globally-unique URI of the following form: \n\n```\nhttps://www.googleapis.com/apiName/apiVersion/resourcePath?parameters\n```\n\nBecause all API resources have unique HTTP-accessible URIs, REST enables data caching and is optimized to work with the web's distributed infrastructure.\n\nYou may find the [method definitions](https://tools.ietf.org/html/rfc7231#section-4.3) in the HTTP 1.1 standards documentation useful; they include specifications for `GET`, `POST`, `PUT`, and `DELETE`.\n\n### REST in the Cloud Billing Budget API\n\nThe Cloud Billing Budget API operations map directly to REST HTTP verbs.\n\nThe specific formats for Cloud Billing Budget API URIs are: \n\n```\nhttps://billingbudgets.googleapis.com/v1/resourcePath?parameters\n```\n\nThe full set of URIs used for each supported operation in the API is summarized\nin the Cloud Billing Budget API reference documents\n([REST](/billing/docs/reference/budget/rest),\n[RPC](/billing/docs/reference/budget/rpc)).\n\nLearn JSON basics\n-----------------\n\nThe Cloud Billing Budget API returns data in JSON format.\n\n[JSON](http://en.wikipedia.org/wiki/JSON) (JavaScript Object Notation) is a common, language-independent data format that provides a simple text representation of arbitrary data structures. For more information, see [json.org](http://www.json.org/)."]]
