# HILLS API > Integrate your catalog, delivery and royalty data with the HILLS distribution platform. The HILLS API gives partners programmatic access to the same platform our workspace runs on — so labels, distributors and catalog owners can connect HILLS to their own systems instead of working only in the browser. > **Early access.** Reference pages are published as each part of v1 opens. [Request access](https://hillsmusic.com/api/) to join. ## What you'll be able to build - **Catalog sync** — create and update releases and tracks from your own catalog or rights system. - **Asset upload** — send audio and artwork directly, without the workspace. - **Delivery tracking** — follow each release's status per store and react to changes. - **Reporting** — pull streams, revenue and statements into your BI or accounting tools. - **White-label integration** — run client onboarding and releases on your own front end. ## How access works API access is part of an API plan agreed with your partner manager. Once enabled, the account owner creates API keys in the workspace and manages them per environment. Continue with [Early access](https://hillsmusic.com/docs/overview/early-access/). Source: https://hillsmusic.com/docs/overview/introduction/ --- # Early access > How API early access works and what to expect. ## Requesting access Submit the [API access request](https://hillsmusic.com/apply/?type=api). Tell us what you want to integrate and roughly how many releases and requests you expect. We get back to you within 1–3 business days. ## What you get - A **sandbox** environment with test data, separate from your live catalog. - **API keys** managed by your account owner in the workspace. - Access to reference pages as each area of v1 is published. - A direct line to our engineering team for feedback during early access. ## Changes during early access Endpoints in early access can still change. We announce changes in advance to every early-access partner, and stable versions are versioned so integrations don't break. Source: https://hillsmusic.com/docs/overview/early-access/ --- # Authentication > How requests are authenticated with API keys. **Status:** coming in API v1. This page describes what the section will cover; the full reference is published when it opens. Covers: creating and rotating API keys in the workspace, sandbox and production keys, sending the key with each request, and key permissions. Source: https://hillsmusic.com/docs/guides/authentication/ --- # Making requests > Base URL, request format and versioning. **Status:** coming in API v1. This page describes what the section will cover; the full reference is published when it opens. Covers: the base URL for each environment, JSON request and response format, API versioning, and request IDs for support. Source: https://hillsmusic.com/docs/guides/making-requests/ --- # Errors > Error format and status codes. **Status:** coming in API v1. This page describes what the section will cover; the full reference is published when it opens. Covers: the error response format, HTTP status codes used by the API, and how to handle validation errors. Source: https://hillsmusic.com/docs/guides/errors/ --- # Rate limits > Request limits per plan and how to handle them. **Status:** coming in API v1. This page describes what the section will cover; the full reference is published when it opens. Covers: limits per API plan, rate-limit headers, and retrying with backoff. Source: https://hillsmusic.com/docs/guides/rate-limits/ --- # Pagination > Paging through lists of releases, tracks and statements. **Status:** coming in API v1. This page describes what the section will cover; the full reference is published when it opens. Covers: cursor-based pagination, page sizes and ordering. Source: https://hillsmusic.com/docs/guides/pagination/ --- # Webhooks > Receive events when releases, deliveries or statements change. **Status:** coming in API v1. This page describes what the section will cover; the full reference is published when it opens. Covers: subscribing to events, payload format, signature verification and retries. Source: https://hillsmusic.com/docs/guides/webhooks/ --- # Releases > Create, update and read releases. **Status:** coming in API v1. This page describes what the section will cover; the full reference is published when it opens. Covers: release objects, creating and updating releases, release metadata and submitting a release for review. Source: https://hillsmusic.com/docs/reference/releases/ --- # Tracks > Tracks, ISRCs and track-level credits. **Status:** coming in API v1. This page describes what the section will cover; the full reference is published when it opens. Covers: track objects, credits on recordings, ISRCs and ordering tracks on a release. Source: https://hillsmusic.com/docs/reference/tracks/ --- # Assets > Uploading audio and artwork. **Status:** coming in API v1. This page describes what the section will cover; the full reference is published when it opens. Covers: upload flow for audio and artwork, accepted formats and validation results. Source: https://hillsmusic.com/docs/reference/assets/ --- # Deliveries > Delivery status per store, takedowns and redeliveries. **Status:** coming in API v1. This page describes what the section will cover; the full reference is published when it opens. Covers: delivery status per store, takedown and redelivery requests, and delivery events. Source: https://hillsmusic.com/docs/reference/deliveries/ --- # Analytics > Streams and revenue trends. **Status:** coming in API v1. This page describes what the section will cover; the full reference is published when it opens. Covers: daily streams and revenue by store, territory, release and track. Source: https://hillsmusic.com/docs/reference/analytics/ --- # Royalties > Statements, statement lines and payouts. **Status:** coming in API v1. This page describes what the section will cover; the full reference is published when it opens. Covers: statements by period, statement lines matched to recordings, splits and payout history. Source: https://hillsmusic.com/docs/reference/royalties/