> ## Documentation Index
> Fetch the complete documentation index at: https://docs.supercycle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Admin API

> Read and update your Supercycle cycles, items, charges, products, and customers over REST

The Supercycle Admin API gives you programmatic access to your rental, subscription, membership, and resale operations. Use it to connect Supercycle to your existing systems, automate workflows, and build tools for your team.

To use the Admin API you need three things:

* **API access.** The Admin API is available on the Superest plan and on custom plans. Contact support from the app to request it.
* **An API key.** Create keys under <Icon icon="shopify" iconType="solid" /> **[Integrations](https://admin.shopify.com/apps/supercycle/settings/integrations)**. See [Authentication](/api-reference/admin/authentication).
* **The base URL.** Every request goes to `https://app.supercycle.com/api/v1`.

***

## API structure

The Admin API follows REST conventions:

* Resources are accessed with the standard HTTP methods `GET`, `POST`, `PUT`, and `DELETE`.
* Requests and responses are JSON.
* Responses use standard HTTP status codes.
* List endpoints are [paginated](/api-reference/admin/pagination).

***

## Cycles

List, fetch, and update cycles at [`/cycles`](/api-reference/admin/cycles/list-all-cycles) and [`/cycles/{cycleId}`](/api-reference/admin/cycles/update-a-cycle). These are the canonical paths.

The `/rentals` paths remain available as deprecated aliases with identical behavior. In API v1, request and response bodies still use the `Rental` schema and rental-named properties such as `rentalStart`, `rentalEnd`, and `reallocateConflictingRentals`. A schema rename is planned for API v2.

***

## Rate limits

Requests are rate limited to keep the platform stable. When you exceed the limit, the API returns `429 Too Many Requests`. Back off and retry. If your integration needs a higher limit, contact support from the app and describe the use case.
