Fullscreen Direct API V1

Use the Fullscreen Direct API to develop custom, standalone integrations with Fullscreen Direct.

Under Development

The API is actively evolving - please check back here for updates and changes.

Updates

2017-02-15

All urls have been updated to use singular resource names. Any plural endpoints will continue to work as they are now aliased to the singular version for backward compatibility.

Endpoints between content items, such as Photos, Events, Audio, etc, have been updated to be more consistent with having the same abilities on each endpoint, such as updating or creating, and sub-resource lists now have the same features.

Store Item Creation endpoint now treats the 'store_item' as an optional namespacer, making it behave like other REST endpoints.

Fork us on GitHub!

All of Fullscreen Direct's documentation is up on GitHub for you to fork, modify, and improve. Join us over there to request features, add suggestions, and report bugs. What are you waiting for? Git to it!

General Information

The root URL of the API is https://api.fullscreendirect.com/v1/. It can generally be assumed that writing endpoints use POST requests and reading endpoints use GET requests.

Authorization

Connecting with the Fullscreen Direct API uses the OAuth 2.0 standard. You must first create a Fullscreen Direct account and then register your application in the Fullscreen Direct backend to receive a client ID and secret that will allow users to connect with your application. To do this, click on your account at the top of the page and then "Account Settings" followed by "Developer Center".

Requests can be be made with just a client_id parameter, but this is restricted to reading (listing) endpoints. In order to make use of any writing (editing) endpoints, an access token (i.e. validated user) must be present.

Responses

All dates returned are in GMT / UTC (+0000) unless otherwise specified. The format of these dates follows PHP date() function function and is Y-m-d H:i:s (i.e. 2014-01-01 12:00:00).

Responses are returned as JSON. To receive a JSONP response, include a GET parameter named jsonp specifying the name of your callback method.

Often times, large objects will be returned with just their ID instead of the whole object if they are nested within the main response. To have these objects expanded, just pass a GET parameter named expand with the comma separated string of the keys you want to expand. For instance, passing expand=user would then return the JSON for an entire user as opposed to just the ID of that user.

There are a lot of different model objects represented in the API. If you pass expand=kind with your requests, each object type will have a unique kind key in the JSON with a value of the object that the JSON structure represents. This can be useful for knowing what type of object to parse that JSON into if you're using native objects in your language as opposed to just arrays.

The general structure of a success response can be seen below. The data key will contain the actual response data whereas the metadata key will contain informational content about the request.

Authentication

Fullscreen Direct uses the OAuth2 authentication process to get an access token from a request token. The access token is then used to make all subsequent requests.

Access tokens can be revoked on a per-application basis at any point in time by the user in their settings area in the Fullscreen Direct backend.

Depending on the endpoint, differing levels of authentication exist. Some endpoints require that the authenticated user be a fan while other require that they be an admin of the account. For those that require being an admin, some require a specific level of admin privileges, such as an editor or an author. Appropriate error messages will be shown if you try to access an endpoint you don't have access to.

A client_id must usually be passed with each request depending on the authentication level of that endpoint. However, if the request is made on behalf of an authenticated user, a client_id is not necessary.

Once an access token is received, it should be passed with the request as an HTTP header: Authorization: OAuth <access token here>

Account content:

requests without authentication or with non-fans will receive only non-exclusive content, except audio and store item list endpoints which return all content.
requests identifying a fanclub member (with the honor_exclusivity query string parameter) will receive content exclusive to their fanclub tier as well as non-exclusive content.
requests identifying an account administrator will receive all content regardless of its exclusivity.

Request Token

[POST] /oauth2

This endpoint is used to get a request token.

username (required)

the email or username of the user trying to authenticate

password (required)

the password of the user trying to authenticate

response_type (required)

the response type you'd like to receive
possible value is code

client_id (required)

the ID of the application this user is connecting to (applications can be created in the backend of Fullscreen Direct)
possible values are any client ID that matches a registered application

redirect_uri (required)

the redirect URI tied to the application you're connecting the user to
possible values are the URI that matches the application being used

Example Response

Applications

These endpoints revolved around the application requests are being made on behalf of.

Enable User Push Token

[POST] /application/push/token

Allows an application to give Fullscreen Direct a push notification for a user so that they can be messaged via push notifications from the Fullscreen Direct backend.
Note: For iOS development, you'll need to upload your Apple Push Notification Certificate so we can authenticate push notifications with your tokens. Please contact us to handle this.

if the user is an admin, this will be what type of admin they are (owner, editor, author, read_only, or fan_club_moderator)

Create

[POST] /account

Creates a new account and makes the currently authenticated user an admin for that account

POST Parameters

name(required)

stagebloc_url(required)

the URL of the account on Fullscreen Direct (i.e. www.fullscreendirect.com/fsd_url)

description

image

an image file to use for the account's image

List

[GET] /account

Gets a listing of various types of accounts for a user

GET Parameters

order_by

what to order the accounts by (possible values include created, modified, and accountName)

admin

whether or not to include accounts the user is an admin of (defaults to true)

following

whether or not to include accounts the user is follow (defaults to true)

Retrieve

[GET] /account/{accountId}

Gets an account's information from its ID.

Update

[POST] /account/{accountId}

Updates an account by its ID. Only admins of the account can use this endpoint.

POST Parameters

name

description

stagebloc_url

User Follow

[POST] /account/{accountId}/follow

This endpoint allows a user to follow an account.

Note: If the tier the user is trying to follow is a paid tier, that functionality is not possible through the API.

User Unfollow

[DELETE] /account/{accountId}/follow

This will have a user unfollow an account regardless of the tier they are on

POST Parameters

tier(required)

the tier the user wants to follow this account on
must be either 1, 2, or 3

expiration

an expiration date to use for this membership
must be a valid datetime string
by default the system will determine a time to use for the expiration based on the tier's settings, but you can use this to override that

List - Content

GET Parameters

a comma separated list of content types to include
in the returned stream of events.
accepted values are audio, audio_playlists, blog,
events, photos, photo_albums, statuses, store, videos,
and video_playlists
defaults to blog, statuses, photos, videos

limit

the number of items to limit the response to
accepted values are any positive number
defaults to 20

offset

how much to offset the returned items by
accepted values are any number greater than or equal to zero
defaults to 0

List - Fans

[GET] /account/{accountId}/fans

Gets a list of fans for the account.

GET Parameters

limit

the number of items to limit the response to
accepted values are any positive number
defaults to 50

offset

how much to offset the returned items by
accepted values are any number greater than or equal to zero
defaults to 0

order_by

how to order the returned results
accepted values are created, name, email, and username
defaults to created

direction

which order to return the results in
accepted values are ASC or DESC
defaults to DESC

List - Child Accounts

[GET] /account/{accountId}/children/{type}

Gets the children accounts of a parent account. The {type} is optional and omitting it will return children accounts of all types. Otherwise, simply take the type of children accounts you are looking for, replace the spaces with dashes, and use that as the {type}.

In the response, child_account_types will show all of the types regardless of the {type} requested.

GET Parameters

limit

the number of items to limit the response to
accepted values are any positive number
defaults to 50

offset

how much to offset the returned items by
accepted values are any number greater than or equal to zero
defaults to 0

Example Response

Response Explanation

An array of strings of the different types of children accounts the parent account has setup

child_accounts

An array of account objects (see account listing endpoint for structure). It will also add a child_account_type key to each account specifying the type it is

Users

These endpoints revolve around Fullscreen Direct users and their data. A user on Fullscreen Direct can be an admin for any number of accounts, and their login is tied to their email address. A user can also be a fan of any number of accounts. These endpoints allow for management of both admin and fan relationships between users and their accounts.

this is only included for the currently authenticated user (i.e. won't show up for users other than the authenticated one)

email

this is only included for the currently authenticated user (i.e. won't show up for users other than the authenticated one)

phone_number

this is only included for the currently authenticated user (i.e. won't show up for users other than the authenticated one)

photo

the user's photo
the width and height are the dimensions of the originally uploaded photo

access_token & scope

Only returned when creating user.

Create

[POST] /user

Creates a new user on Fullscreen Direct.

POST Parameters

email(required)
The email address to use for the user

password(required)

birthday(required)

source_account_id
An account ID for an account to follow / join the Fan Club of during signup, this will then send a Fan Club welcome email instead of the generic Fullscreen Direct signup email

name

username
The username for this user, it must be unique across all of Fullscreen Direct and only accepts letters, numbers, and underscores.

gender
Accepts male or female

Retrieve - Current User

[GET] /user/me

Gets the currently authenticated user's information.

Update - Current User

[POST] /user/me

Updates the currently authenticated user's information.

POST Parameters

bio

birthday

email

username

name

gender

Retrieve

[GET] /user/{userId}

Gets a user by their user ID

List - Content

[GET] /user/{userId}/content/updates

This returns a listing of content that this user has created across any account they are a part of. Each content object returned in this response will have its kind value automatically expanded, and the structure of the content type will match it as if you were loading that single object via its own endpoint. Looking at the structure of a audio response, for example, will show you what an audio object in the array of content returned here will be formatted like.

GET Parameters

filter(required)
A comma separated string for the type(s) of content to be returned. Allowed values are audio, blog, event, photo, status, store, and video.

List - Like

[GET] /user/{userId}/content/like

This returns a listing of content that this user has liked across Fullscreen Direct. Each content object returned in this response will have its kind value automatically expanded, and the structure of the content type will match it as if you were loading that single object via its own endpoint. Looking at the structure of a audio response, for example, will show you what an audio object in the array of content returned here will be formatted like.

GET Parameters

filter(required)
A comma separated string for the type(s) of content to be returned. Allowed values are audio, blog, event, photo, status, store, and video.

Fan Clubs

Users on Fullscreen Direct can join Fan Clubs associated with accounts. By default an account doesn’t have a Fan Club set up, but creating one adds extra functionality such as having three different membership tiers and requiring payment for joining the Fan Club.

Overview Dashboard

[GET] /account/{accountId}/fanclub/dashboard

This endpoint will return various stats and information about the account's fan club (similar to the data shown on the fan club dashboard in the Fullscreen Direct backend)

together these represent how long the membership lasts
the unit can be once, year, or month

discount

the discount (in percentage points) that this tier gives fans off of store items for this account

allowed_content_sections

the types of content fans are able to submit to this Fan Club

List

[GET] /account/fanclub/{type}

This endpoint retrieves a listing of Fan Clubs on Fullscreen Direct. The accepted values for type are following, featured, or recent with featured being the default. Note that for featured Fan Clubs, limit and offset are ignored as it will return all featured Fan Clubs at the time.

GET Parameters

limit

the number of items to limit the response to
accepted values are any positive number
defaults to 20

offset

how much to offset the returned items by
accepted values are any number greater than or equal to zero
defaults to 0

Retrieve

[GET] /account/{accountId}/fanclub

This will return the details about the Fan Club.

Update

[POST] /account/{accountId}/fanclub

This will create or update a Fan Club that belongs to the account with the given accountId.

POST Parameters

title

The title of the Fan Club as a whole (as opposed to any tier)

description

The description of the Fan Club as a whole (as opposed to any tier)

moderation_queue

Whether or not to have the moderation queue on for this Fan Club.

tier_info(required)

An array structured similar to the return data for each array in the response below used to setup each tier. If one of the tier keys is missing from this array, that tier will be removed from the Fan Club. Instead of the two returned membership values, pass a membership_length parameter as a value in seconds that must match either zero, one month, three months, six months, or a year using number of seconds in a day (86,400) multiplied by the days in that interval (months are assumed to be 30 days in length).

Audio

These endpoints revolve around the ability to upload and stream audio through Fullscreen Direct. Audio consists of both individual tracks and those tracks being organized into various playlists.

Fullscreen Direct has audio playlist widgets for playlists that you can use by embedding this code on an HTML page if you so choose

artist

admins can add a special artist to a playlist if it something different than the name of the account

audio

the number of tracks in the playlist, or an array of audio objects if you pass specify to expand audio as a parameter

custom_field_data

if you have custom data set on events for your account, the slugs will show up as keys here with their values

List

[GET] /account/{accountId}/audio

This endpoint can used to list all the audio for a certain account.

GET Parameters

honor_exclusivity

whether to restrict content exclusive to a specific tier based on the active user's permissions
accepted values are 0 to show all content and 1 to restrict to only exclusive content visible to the user.
defaults to 0

playlist_id

an audio playlist ID to limit the audio results to
accepted values are an ID of any playlist that belongs to the same account
defaults to none

limit

the number of items to limit the response to
accepted values are any positive number
defaults to 50

offset

how much to offset the returned items by
accepted values are any number greater than or equal to zero
defaults to 0

order_by

how to order the returned items
accepted values are created, modified, and recordedDate
if playlist_id is provided this can also be accountAudioSortOrder
defaults to created

direction

what direction to order the returned items
accepted values are ASC and DESC
defaults to DESC

Create

[POST] /account/{accountId}/audio

This endpoint can be used to create a single audio track for an account. It currently only allows actual uploads as opposed to also allowing SoundCloud or other third party source URLs.

POST Parameters

audio(required)

the contents of the audio file itself

title(required)

the title of the track

description

the description of the track

public

whether or not this audio track should be public (defaults to true)

exclusive(deprecated)

whether or not this audio track should be exclusive

exclusive_tiers[]{array}

what fan club tier(s) the audio track is exclusive to
Can be included multiple times to specify multiple tiers

Retrieve

[GET] /account/{accountId}/audio/{audioId}

This endpoint can be used to get a single audio track from an account.

Update

[POST] /account/{accountId}/audio/{audioId}

Delete

[DELETE] /account/{accountId}/audio/{audioId}

List Playlists

[GET] /account/{accountId}/audio/playlists

This endpoint can be used to list audio playlists that are available for an account.

GET Parameters

honor_exclusivity

whether to include content exclusive to a specific tier based on the active user's permissions
accepted values are 0 to only show public content and 1 to also include exclusive content.
defaults to 0

limit

the number of items to limit the response to
accepted values are any positive number
defaults to 50

offset

how much to offset the returned items by
accepted values are any number greater than or equal to zero
defaults to 0

order_by

how to order the returned items
accepted values are created and modified
defaults to created

direction

what direction to order the returned items
accepted values are ASC and DESC
defaults to DESC

the number of photos this photo album has
if you specify to expand the photos key, it will be an array of the photos for this album (structured the same as the photo listing endpoint)

List

[GET] /account/{accountId}/photo

Lists photos from an account.

GET Parameters

honor_exclusivity

whether to include content exclusive to a specific tier based on the active user's permissions
accepted values are 0 to only show public content and 1 to also include exclusive content.
defaults to 0

limit

the number of items to limit the response to
accepted values are any positive number
defaults to 50

offset

how much to offset the returned items by
accepted values are any number greater than or equal to zero
defaults to 0

order_by

how to order the returned items
accepted values are created and modified
defaults to created

direction

what direction to order the returned items
accepted values are ASC and DESC
defaults to DESC

Create

[POST] /account/{accountId}/photo

Uploads a photo to an account.

POST Parameters

photo(optional)
The photo file itself, if photo_url is not passed this parameter is required

photo_url(optional)
A url for a photo, if photo is not passed this parameter is required

title(required)
The title to use for the photo

description
A longer description of the photo

fan_content
If the photo is being posted by an admin as a fan photo, this can be set to true

Retrieve

[GET] /account/{accountId}/photo/{photoId}

This endpoint can be used to get a single photo from an account. Note that if the photo is fan submitted or exclusive, it will require that the request be made by a logged in user who has access to that account as a fan or admin.

Update

[POST] /account/{accountId}/photo/{photoId}

This endpoint can be used to update the descriptive data of a single photo from an account. Note that if the photo is fan submitted or exclusive, it will require that the request be made by a logged in user who has access to that account as a fan or admin.

title

description

exclusive_tiers / exclusive

Delete

[DELETE] /account/{accountId}/photo/{photoId}

This endpoint can be used to delete a single photo from an account. Note that if the photo is fan submitted or exclusive, it will require that the request be made by a logged in user who has access to that account as a fan or admin.

List Albums

[GET] /account/{accountId}/photo/album

Lists photos albums from an account.

GET Parameters

honor_exclusivity

whether to include content exclusive to a specific tier based on the active user's permissions
accepted values are 0 to only show public content and 1 to also include exclusive content.
defaults to 0

limit

the number of items to limit the response to
accepted values are any positive number
defaults to 50

offset

how much to offset the returned items by
accepted values are any number greater than or equal to zero
defaults to 0

order_by

how to order the returned items
accepted values are created and modified
defaults to created

direction

what direction to order the returned items
accepted values are ASC and DESC
defaults to DESC

Retrieve Album

[GET] /account/{accountId}/photo/album/{albumId}

This endpoint can be used to get a single photo album from an account.

Add Photos to Album

[POST] /account/{accountId}/photo/album/{albumId}/photo

This endpoint can be used to add an existing photo to a photo album.

POST Parameters

photo_ids(required)

an array of photo IDs to be added to the album

Statuses

Statuses on Fullscreen Direct are shorter text updates that account's are able to schedule and post to both Fullscreen Direct itself and their connected social networks.

List

whether to include content exclusive to a specific tier based on the active user's permissions
accepted values are 0 to only show public content and 1 to also include exclusive content.
defaults to 0

order_by

how to order the returned items
accepted values are created, modified, and price
defaults to created

direction

what direction to order the returned items
accepted values are ASC and DESC
defaults to DESC

limit

the number of items to limit the response to
accepted values are any positive number
defaults to 50

offset

how much to offset the returned items by
accepted values are any number greater than or equal to zero
defaults to 0

Create

[POST] /account/{accountId}/status

This endpoint can be used to post a status to Fullscreen Direct.

POST Parameters

text(required)
The text of the status to post

latitude
The latitude of the user posting the status to tie a location to it

longitude
The longitude of the user posting the status to tie a location to it

Retrieve

[GET] /account/{accountId}/status/{statusId}

This endpoint can be used to get a single status post on Fullscreen Direct.

Delete

[DELETE] /account/{accountId}/status/{statusId}

This endpoint can be used to delete a single status post on Fullscreen Direct. Only admins of the account with the right admin level or the original fan who posted the status are capable of deleting it.

Likers

[GET] /account/{accountId}/status/{statusId}/liker

This endpoint can be used to list the users who have liked this status on Fullscreen Direct.

The response data will be an array of User objects.

Store and Commerce

These endpoints revolve around Fullscreen Direct store and commerce data in the backend. They can be used for tasks including retrieving store items and orders, updating orders, or getting analytics from a store.

Overview Dashboard

[GET] /account/{accountId}/store/dashboard

This endpoint is used to get stats and data regarding commerce and sales (very similar to the data shown on the Store dashboard in the Fullscreen Direct backend). It will provide all time, overall stats regarding your store and its revenue as well as results per country you've had at least one order in.

the type of store item this is
possible values are physical, experience, digital, or bundle

shipping_providers

the available shipping methods for this store item, only shows up for items of type physical

options

the various SKUs available for this product and their related data

bundled_items

the store items that are in this bundle, only shows up for items of type bundle
other store items, audio tracks, or audio playlists can be bundled and will be listed under their respective section in this array

photos

the number of photos this store item has
if you specify to expand the photos key, it will be an array of the photos for this item

album_id

the ID for the photo album associated with this store item
only returned if a photo_url is passed and is successfully processed
this ID can be used to add additional photos for this store item via /photo/album/{albumId}/photo

List - Store Item

[GET] /account/{accountId}/store/item

This endpoint is used to get a listing of store items belonging to an account.

GET Parameters

honor_exclusivity

whether to restrict content exclusive to a specific tier based on the active user's permissions
accepted values are 0 to show all content and 1 to restrict to only exclusive content visible to the user.
defaults to 0

order_by

how to order the returned items
accepted values are created, modified, and price
defaults to created

direction

what direction to order the returned items
accepted values are ASC and DESC
defaults to DESC

limit

the number of items to limit the response to
accepted values are any positive number
defaults to 50

offset

how much to offset the returned items by
accepted values are any number greater than or equal to zero
defaults to 0

Create - Store Item

[POST] /account/{accountId}/store/item

This endpoint is used to create a new store item and, if relevant, its options. In the case of a physical store item it also configures the shipping price handlers for this new store item.

POST Parameters

a string indicating the type of store item to create
accepted values are PHYSICAL or EXPERIENCE

price(required)

a decimal number indicating the base price for this store item

title(required)

a string (up to 150 characters) representing the title of the store item

description

a string representing the description of the store item (HTML supported)

category

a string representing a category in which to group this store item

status

a string representing the status of the store item
accepted values are OKAY or PRIVATE
defaults to OKAY

exclusive

a boolean, true if this should only be presented to users who are following the account
defaults to false

exclusive_tiers

an integer occurring 1 to 3 times specifying which fan club tier(s) an item is exclusive to
should be used instead of [exclusive] above.
defaults to none

featured

a boolean, true if this should be considered a featured item

fulfiller_id(required for type set to PHYSICAL)

an integer ID for a fulfiller already configured in Fullscreen Direct which is associated with this account

options(required for type set to PHYSICAL or EXPERIENCE)

an array of objects representing each option (for a T-shirt each option may represent a size, a color, or a combination of the two, etc)
See Options below for field information

shipping_price_handlers(required for type set to PHYSICAL)

an array of objects representing each shipping price handler to be offered to a user attempting to purchase this item. The object may include additional handling fees and options depending on the type of handler indicated.
See Shipping Price Handlers below for field information

Options

each element in this array may contain the following fields:

name(required)

the name to display when there are multiple options under the store item

sku

an identifier used to distinguish between this option and other options under the same store item
defaults to an auto-generated alphanumeric SKU

upc

an identifier used to submit download / sales information to SoundScan or Buzz Angle

quantity

null for unlimited or a non-negative integer representing how much stock is currently on hand
defaults to null

additional_price

a non-negative integer representing the additional price to charge if this option is selected by the user (useful if an XXL t-shirt is more expensive than other variations, for example)
defaults to no additional price

weight(required for type set to PHYSICAL)

a non-negative decimal number indicating the weight in ounces of this option (used for shipping price calculation)

height(required for type set to PHYSICAL)

a non-negative decimal number indicating the height in inches of this option (used for shipping price calculation)

width(required for type set to PHYSICAL)

a non-negative decimal number indicating the width in inches of this option (used for shipping price calculation)

length(required for type set to PHYSICAL)

a non-negative decimal number indicating the length in inches of this option (used for shipping price calculation)

status

a string representing the status for this option
accepted values are NORMAL or DISABLED
defaults to NORMAL

List - Fulfiller

This endpoint is use to get a listing of all fulfillers belonging to an account

Create - Fulfiller

[POST] /account/{accountId}/store/fulfiller

This endpoint is used to create a new fulfiller. Many of the data requirements are specific to the type of fulfiller being created.

POST Parameters

name(required)

a name for this fulfiller

type(required)

the type of fulfiller to create, one of: STAGEBLOC

international_shipping_agreement

a plain text string to which the user must agree if they are requesting shipment to a country which does not match the country for this fulfiller's private address

private_address(required)

Private addresses are used in all location if no public address is set. If a public address is set the private address only appears on Purchase Orders.
See Address below for fields

public_address(optional)

See Address below for fields

Address

name

a string the name for the address

street_address

the street address

street_address_2

a second street address

city

the city

country

the 2 character country code as specified by ISO-3361-alpha 2

postal_code

the postal code appropriate to the country. If country is US the 5 digit zip code for the private address. If country is CA then you must provide a 6 character postal code (you may provide this with an additional space separator). For all other countries please use an appropriate postal code.

state

The region identifier appropriate for the country indicated. For US state codes please use the 2 character United States Postal Service abbreviations. For CA provinces please use the 2 character postal abbreviation for the province or territory. For all other countries please use a region identifier of your choice.

Retrieve - Fulfiller

[GET] /account/{accountId}/store/fulfiller/{fulfillerId}

This endpoint is use to get information about a single fulfiller belonging to an account

only relevant to videos not uploaded directly to StageBloc, this would be the link to the video on the third party site

embed_code

the embed code of the video to include in HTML

List

[GET] /account/{accountId}/video

GET Parameters

honor_exclusivity

whether to include content exclusive to a specific tier based on the active user's permissions
accepted values are 0 to only show public content and 1 to also include exclusive content.
defaults to 0

Create

[POST] /account/{accountId}/video

This endpoint can be used to upload a video to an account. Once uploaded, there will be a slight delay before it can play while it converts. This request must be made by a logged in fan or admin of the account. Depending on the access level of the logged in user, it will become fan content or official content.

POST Parameters

video(required)

the contents of the video file itself

title(required)

the title of the video

fan_content

whether to force this content to be submitted as fan content (versus official content, only applies if the logged in user is an admin of the account)

description

the description of the video

exclusive

whether or not this video should be exclusive

exclusive_tiers

what fan club tier(s) the video is exclusive to

Retrieve

[GET] /account/{accountId}/video/{videoId}

Update

[POST] /account/{accountId}/video/{videoId}

Delete

[DELETE] /account/{accountId}/video/{videoId}

List - Playlist

[GET] /account/{accountId}/video/playlist

GET Parameters

honor_exclusivity

whether to include content exclusive to a specific tier based on the active user's permissions
accepted values are 0 to only show public content and 1 to also include exclusive content.
defaults to 0

order_by

how to order the returned items
accepted values are created, modified, and price
defaults to created

direction

what direction to order the returned items
accepted values are ASC and DESC
defaults to DESC

limit

the number of items to limit the response to
accepted values are any positive number
defaults to 50

offset

how much to offset the returned items by
accepted values are any number greater than or equal to zero
defaults to 0

Create - Playlist

[POST] /account/{accountId}/video/playlist

Retrieve - Playlist

[GET] /account/{accountId}/video/playlist/{playlistId}

Update - Playlist

[POST] /account/{accountId}/video/playlist/{playlistId}

Delete - Playlist

[DELETE] /account/{accountId}/video/playlist/{playlistId}

Comments

Comments can be made on almost all types of content in Fullscreen Direct.