/gcp/skus

POST /api/gcp/skus

Price: 1 credit

Look up one Google Cloud SKU by its id and return the description Google publishes for it, the product it belongs to, every region it is priced for, and its price with the currency and billing unit.

How to use it

The id is the dashed hexadecimal form Google prints on a billing line, `5987-A5DB-E43D`; a service or product id is a different thing and will be rejected. Take the id from gcp/skus/search. A SKU covers every region listed in `regions` at one price, so there is no per-region variant to choose between.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• sku_id string required — Google Cloud SKU id, three groups of four hexadecimal characters (examples: "5987-A5DB-E43D"; minLength: 1)
• currency string — Currency the price is converted to before it is returned (default: "USD"; one of: "AUD", "BRL", "CAD", "CHF", "CLP", "COP", "CZK", "DKK", "EUR", "GBP", "HKD", "IDR", "ILS", "INR", "JPY", "KRW", "MXN", "MYR", "NOK", "NZD", "PLN", "SEK", "SGD", "THB", "TRY", "TWD", "USD", "VND", "ZAR")

Response

• @type string (default: "GcpSku")
• id string required
• description string nullable
• service_code string nullable
• service_name string nullable
• regions array (default: [])
• price number nullable
• currency string nullable
• unit string nullable
• price_text string nullable
• additional_price_texts array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No SKU carries that id. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.