2) Approve the authorization access

Once you are successfully logged in, you will be presented with this confirmation page.

On Authorization the API will redirect to the defined redirect_uri with the parameter code = yourauthorizationcode

3) Request the Bearer token

On Authorization Now that we have the authorization code, we can request the access token by sending this code to https://api.libsyn.com/oauth URI, passing the client_id, the client_secret, and the redirect_uri as shown below:

									
									POST /oauth HTTP/1.1
									Accept: application/json
									Content-Type:
										application/json
									{
									"redirect_uri":
										"http://yourredirecturi.com/blah",
									"client_id":
										"testclient",
									"client_secret":
										"testpass",
									"code":
										"a4dd64ffb43e6bfe16d47acfab1e68d9c7a28381",
									"grant_type"
										: "authorization_code"
									}
									
								

The Libsyn Oauth2 server will reply with the token using a JSON structure like that:

									
									HTTP/1.1 200 OK
									Content-Type:
										application/json
									{
									"access_token":
										"907c762e069589c2cd2a229cdae7b8778caa9f07",
									"expires_in":
										3600,
									"refresh_token":
										"43018382188f462f6b0e5784dd44c36f476ccce6",
									"scope":
										null,
									"token_type": "Bearer"
									}
									
								

Note: You will have 30 seconds to request the access_token

Finally, you can access the API using the Bearer token in the Authorization header of the HTTP request. The following request demonstrates sending the token:

									
									GET /oauth/resource HTTP/1.1
								Accept:
									application/json
								Authorization: Bearer
									907c762e069589c2cd2a229cdae7b8778caa9f07

								

Refresh Token

Libsyn OAuth2 protocol gives you the possibility to refresh the access token, generating a new one with a new lifetime. This action can be performed using the refresh_token that the Libsyn API server provides in the response during the authentication step. You can perform a refresh token using the following command:

Note: You will have 30 seconds to request the access_token

								POST /oauth HTTP/1.1
								Accept: application/json
								Content-Type:
									application/json
								{
								"grant_type":
									"refresh_token",
								"refresh_token":
									"the-refresh-token",
								"client_id":
									"your-client-id",
								"client_secret":
									"your-client-secret"
								}

								

The response will be something like:

								HTTP/1.1 200 OK
								Content-Type:
									application/json
								{
								"access_token":
									"470d9f3c6b0371ff2a88d0c554cbee9cad495e8d",
								"expires_in":
									3600,
								"scope": null,
								"token_type":
									"Bearer"
								}

								

By default, refresh_token has a lifetime of 28 days and will renew the expiration every time a Libsyn Oauth2 server grant_type : refresh_token is completed; as noted above access_token will expire in 3600 seconds.

2) Retrieve Show List

Unless your application is designed to work with only one show (i.e. the show_id is hard-coded into the application), you will have to be mindful of users that have multiple Libsyn shows. Your application should retrieve a list of the user's shows via the user-shows endpoint.

You should receive a response that looks something like the following:

{
	"_links": {
		"self": {
			"href": "/user-shows"
		}
	},
	"_embedded": {
		"user-shows": [
			{
				"show_id": "(int) - Represents a valid Libsyn show ID (numeric or string) (may also be known as show slug)."
				"user_id": "(int) - Represents the user id associated with the developer account."
				"show_slug": "(string) - Show slug of the retrieved show."
				"show_title": "(string) - Show title of the retrieved show."
				"show_description": "(string) - Show description of the retrieved show."
				"is_live": "(boolean) - Specifies if the retrieved show is active."
				"in_directory": "(boolean) - Specifies if the retrieved show is in the Libsyn directory."
				"image_content_id": "(int) - Represents the image content id of the show artwork of the retrieved show."
				"image_url": "(string) - Image URL of the show artwork of the retrieved show."
				"storage": "(string) - User-show storage quota and usage."
				"copyright": "(string) - 	Copyright of the retrieved show."
				"website_url": "(string) - Website url of the retrieved show."
				"contact_email": "(string) - Contact email of the retrieved show."
				"apple_podcasts_store_url": "(string) - Apple podcasts store url of the retrieved show."
				"apple_podcasts_store_id": "(int) - Apple podcasts store id of the retrieved show."
				"is_premium": "(boolean) - 	Specifies if the retrieved show is premium."
			}
		]
	},
	"total_items": "(int)	- The total number of items returned in the search request."
}
													

You can reference our User-Shows reference page for more information on the user-show endpoint.

3) Choose Show

If the user does have more than one show, allow the user to select which show they want to publish to and use the show_id in subsequent steps.

4) Publish Episode

Once the proper show is selected, the end-user will be able to publish episodes to it via the Create Post endpoint.

For more information on how to publish episodes to a show via the Libsyn API, please reference our How to Publish Episodes guide.

2) Set Body

Add the episode information to the form data of your API request. Be sure that the required fields are included in the request which are as follows:

• show_id
• item_title
• item_slug
• is_draft
• release_date

Additional properties can be set for the body of your post request. For a full list, please reference our Post page.

3) Adding Primary Content

Adding Primary Content to an episode is not required. If an episode does not have primary content attached to it, the episode is considered a text-only post.

If you are adding primary content to the episode, reference the Primary Content section in our Posts page of the API documentation for the methods available to you for doing so.

4) Response

Upon successful execution of your request, you will receive a response that will resemble the following:

{
	"status": "(string)		- Represents the status of the post you are attempting to upload.",
	"post": {
		(post field information of your successfully uploaded episode)
	}
}