Pricing and Availability
Endpoints for app price schedules and territories.
Endpoints
POST /v1/appPriceSchedules
Summary: No summary provided.
GET /v1/appPriceSchedules/{id}
Summary: No summary provided.
Parameters:
fields[appPriceSchedules] (query, optional): the fields to include for returned resources of type appPriceSchedulesfields[apps] (query, optional): the fields to include for returned resources of type appsfields[territories] (query, optional): the fields to include for returned resources of type territoriesfields[appPrices] (query, optional): the fields to include for returned resources of type appPricesinclude (query, optional): comma-separated list of relationships to includelimit[automaticPrices] (query, optional): maximum number of related automaticPrices returned (when they are included)limit[manualPrices] (query, optional): maximum number of related manualPrices returned (when they are included)
GET /v1/territories
Summary: No summary provided.
Parameters:
fields[territories] (query, optional): the fields to include for returned resources of type territorieslimit (query, optional): maximum resources per page
GET /v1/appPriceSchedules/{id}/relationships/automaticPrices
Summary: No summary provided.
Parameters:
limit (query, optional): maximum resources per page
GET /v1/appPriceSchedules/{id}/automaticPrices
Summary: No summary provided.
Parameters:
filter[startDate] (query, optional): filter by attribute 'startDate'filter[endDate] (query, optional): filter by attribute 'endDate'filter[territory] (query, optional): filter by id(s) of related 'territory'fields[appPrices] (query, optional): the fields to include for returned resources of type appPricesfields[appPricePoints] (query, optional): the fields to include for returned resources of type appPricePointsfields[territories] (query, optional): the fields to include for returned resources of type territorieslimit (query, optional): maximum resources per pageinclude (query, optional): comma-separated list of relationships to include
GET /v1/appPriceSchedules/{id}/relationships/baseTerritory
Summary: No summary provided.
GET /v1/appPriceSchedules/{id}/baseTerritory
Summary: No summary provided.
Parameters:
fields[territories] (query, optional): the fields to include for returned resources of type territories
GET /v1/appPriceSchedules/{id}/relationships/manualPrices
Summary: No summary provided.
Parameters:
limit (query, optional): maximum resources per page
GET /v1/appPriceSchedules/{id}/manualPrices
Summary: No summary provided.
Parameters:
filter[startDate] (query, optional): filter by attribute 'startDate'filter[endDate] (query, optional): filter by attribute 'endDate'filter[territory] (query, optional): filter by id(s) of related 'territory'fields[appPrices] (query, optional): the fields to include for returned resources of type appPricesfields[appPricePoints] (query, optional): the fields to include for returned resources of type appPricePointsfields[territories] (query, optional): the fields to include for returned resources of type territorieslimit (query, optional): maximum resources per pageinclude (query, optional): comma-separated list of relationships to include
Typical Workflows
Use these endpoints to automate pricing and availability tasks within Apple Store Connect.
Best Practices
- Always authenticate requests using your Apple Store Connect API key (JWT token).
- Handle rate limiting gracefully, as the Apple Store Connect API enforces quotas.
- When writing integrations, refer back to the exact schemas for precise payload construction.
1---2name: pricing-and-availability3description: Endpoints for app price schedules and territories.4---56# Pricing and Availability7Endpoints for app price schedules and territories.89## Endpoints1011### `POST /v1/appPriceSchedules`12**Summary**: No summary provided.1314### `GET /v1/appPriceSchedules/{id}`15**Summary**: No summary provided.1617**Parameters**:18- `fields[appPriceSchedules]` (query, optional): the fields to include for returned resources of type appPriceSchedules19- `fields[apps]` (query, optional): the fields to include for returned resources of type apps20- `fields[territories]` (query, optional): the fields to include for returned resources of type territories21- `fields[appPrices]` (query, optional): the fields to include for returned resources of type appPrices22- `include` (query, optional): comma-separated list of relationships to include23- `limit[automaticPrices]` (query, optional): maximum number of related automaticPrices returned (when they are included)24- `limit[manualPrices]` (query, optional): maximum number of related manualPrices returned (when they are included)2526### `GET /v1/territories`27**Summary**: No summary provided.2829**Parameters**:30- `fields[territories]` (query, optional): the fields to include for returned resources of type territories31- `limit` (query, optional): maximum resources per page3233### `GET /v1/appPriceSchedules/{id}/relationships/automaticPrices`34**Summary**: No summary provided.3536**Parameters**:37- `limit` (query, optional): maximum resources per page3839### `GET /v1/appPriceSchedules/{id}/automaticPrices`40**Summary**: No summary provided.4142**Parameters**:43- `filter[startDate]` (query, optional): filter by attribute 'startDate'44- `filter[endDate]` (query, optional): filter by attribute 'endDate'45- `filter[territory]` (query, optional): filter by id(s) of related 'territory'46- `fields[appPrices]` (query, optional): the fields to include for returned resources of type appPrices47- `fields[appPricePoints]` (query, optional): the fields to include for returned resources of type appPricePoints48- `fields[territories]` (query, optional): the fields to include for returned resources of type territories49- `limit` (query, optional): maximum resources per page50- `include` (query, optional): comma-separated list of relationships to include5152### `GET /v1/appPriceSchedules/{id}/relationships/baseTerritory`53**Summary**: No summary provided.5455### `GET /v1/appPriceSchedules/{id}/baseTerritory`56**Summary**: No summary provided.5758**Parameters**:59- `fields[territories]` (query, optional): the fields to include for returned resources of type territories6061### `GET /v1/appPriceSchedules/{id}/relationships/manualPrices`62**Summary**: No summary provided.6364**Parameters**:65- `limit` (query, optional): maximum resources per page6667### `GET /v1/appPriceSchedules/{id}/manualPrices`68**Summary**: No summary provided.6970**Parameters**:71- `filter[startDate]` (query, optional): filter by attribute 'startDate'72- `filter[endDate]` (query, optional): filter by attribute 'endDate'73- `filter[territory]` (query, optional): filter by id(s) of related 'territory'74- `fields[appPrices]` (query, optional): the fields to include for returned resources of type appPrices75- `fields[appPricePoints]` (query, optional): the fields to include for returned resources of type appPricePoints76- `fields[territories]` (query, optional): the fields to include for returned resources of type territories77- `limit` (query, optional): maximum resources per page78- `include` (query, optional): comma-separated list of relationships to include7980## Typical Workflows81Use these endpoints to automate pricing and availability tasks within Apple Store Connect.8283## Best Practices84- Always authenticate requests using your Apple Store Connect API key (JWT token).85- Handle rate limiting gracefully, as the Apple Store Connect API enforces quotas.86- When writing integrations, refer back to the exact schemas for precise payload construction.
Andersonlimahw