> For the complete documentation index, see [llms.txt](https://docs.umbcheckout.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbcheckout.net/v17/payment-providers/payment-providers/stripe/services/stripe-shipping-rate-apiservice.md).

# Stripe Shipping Rate ApiService

A service which handles getting the Stripe Shipping Rates from the Stripe API

The Stripe Shipping Rate API service is what handles the retrieval of the Shipping Rates from the Stripe API.

You can access the API service by injecting `IStripeShippingRateApiService` which can be found within the namespace `UmbCheckout.Stripe.Interfaces`

{% hint style="info" %}
Every method also has an overload that takes a `CancellationToken` as its last parameter. See [Cancellation Tokens](/v17/core-services/cancellation-tokens.md).
{% endhint %}

#### GetShippingRates

Gets the Shipping Rates from the Stripe API

```csharp
Task<StripeList<ShippingRate>> GetShippingRates();
```

#### GetShippingRate

Gets a Shipping Rate from the Stripe API

Parameters:

| Name | Detail                         |
| ---- | ------------------------------ |
| id   | Id of the Stripe Shipping Rate |

```csharp
Task<ShippingRate> GetShippingRate(string id);
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbcheckout.net/v17/payment-providers/payment-providers/stripe/services/stripe-shipping-rate-apiservice.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.