ART19 Content API

About this Cloud Hub Solution:

‍

The ART19 Content API is a RESTful API that enables developers to access and manage podcast content from ART19, a prominent podcast hosting and distribution platform. This API provides programmatic access to essential podcast data, including metadata, episodes, and audio files.

‍

By leveraging the ART19 Content API, developers can build custom applications, integrations, and workflows that interact with ART19's vast library of podcast content. The API supports a range of features, including:

• Episode retrieval: Access and retrieve specific podcast episodes
• Metadata management: Update and manage podcast metadata, such as titles, descriptions, and tags
• Analytics data access: Gain insights into podcast performance and engagement metrics

‍

API Specifications

The ART19 Content API is designed to conform to the JSON:API specification, ensuring a standardized and intuitive API experience.

‍

To use the API, developers must include the following HTTP Accept header in their requests:

Accept: application/vnd.api+json

‍

This header specifies the expected format of the API responses, ensuring seamless communication between the client and server.

‍

Authorization

To use the ART19 Content API, all requests must be authenticated using the HTTP Authorization header.

The format for the Authorization header is as follows:

Token token="your-token", credential="your-credential"

‍

General Notes

Some query parameters may use unencoded [ and ] characters for readability, and defaults, examples, and possible values are rendered in double quotes for clarity.

However, in practice, query parameters should not have quotes around the values (e.g., foo=bar is valid, not foo="bar")).

Both query parameter keys and values must be percent-encoded, as per the requirements in RFC 3986 § 3.4.

‍

Rate Limiting

To ensure fair distribution of available resources, the API is subject to rate limits.

If the number of API calls per minute exceeds the limit granted to your credential, a 429 Too Many Requests error response will be returned.

In this case, a Retry-After header may be included in the response, indicating the number of seconds after which a request can be retried.

If you experience a high number of 429 errors, please contact ART19 Support to adjust your rate limit.

‍

Example

HTTP/1.1 429 Too Many RequestsContent-Type: text/htmlRetry-After: 21

Pagination Requests to collection endpoints should provide pagination parameters. Some endpoints require pagination parameters to be provided.

Whenever pagination is provided, it must be valid. Failing to provide pagination when it is required or providing wrong or incomplete pagination always results in a 400 Bad Request error response.

The page numbering starts with 1 and the maximum page size is 100. Pagination must not be specified if requesting a list of IDs.

Providing invalid values for page number or page size, as well as providing only a page number or only a page size, is considered an error.

Pagination is provided like this: page[number]=1&page[size]=25

Responses conform to the JSON:API specification's pagination section by including pagination links. Your requested page size will be carried into the pagination links.

Sorting Requests to collection endpoints usually accept a sort parameter. Please refer to the JSON:API specification's sorting section for further details.

Relationship Linking Currently, resources return all of their relationships, in no particular order, pursuant to how relationships should be returned according to the JSON:API specification.

Consumers of this API must not make assumptions about the order of these collections. Even though this data is not currently paginated, consumers must support paginating relationships per the JSON:API specification if this data is important for their application.

‍