The body of the call should contain the channel title optionally it can
contain channel description and tags.HTTPリクエストのContent-Typeにはapplication/x-www-form-urlencodedと設定するようにしてください。
503 Service Unavailable: サーバ側で一時的なエラーが発生していたため、リクエストを処理できませんでした。
Creating a channel
Create a new channel for the current account.
Prerequisites
The caller must have an access token capable initializing channel
creation. To obtain a token , the client must request one from the
authorization server.
Clients can acquire tokens without expiration by asking for
"offline" scope. By using this scope the token will never
expire.
Example initialization of a web-server token-acquiring flow:
The body of the call should contain the channel title optionally it can
contain channel description and tags. The Content-Type of the request
should be application/x-www-form-urlencoded.
Array of RTMP URLs (strings) where the client can broadcast.
Client should fall-back to the second/third one if it provided
and the previous element seems failing. Provided only in case
of client explicitly asks for with a "broadcaster" detail_level
query parameter.
Shortened web URL of the channel
(http://ustre.am/
...) - suitable for sharing on Twitter / Facebook
status
string
Possible values: "online" or "offline". "online" means that
the stream is viewable on the Ustream website.
broadcast_urls
array of string
Array of RTMP URLs (strings) where the client can broadcast.
Client should fall-back to the second/third one if it provided
and the previous element seems failing. Provided only in case
of client explicitly asks for with a "broadcaster" detail_level
query parameter.
default
boolean, optional
True if this is the default channel for the user. False or
missing if it is not the default channel.
live_thumbnail
string
Listed when the channel is online.
The paging information can be found inside the "paging" element. Example:
Use third party authentication on viewing Ustream video content (live or recorded video). Technically it is a handshake mechanism between your service and the Ustream infrastructure.
On success a response with HTTP status 201 Created is returned when new
hash lock was inserted for the channel.
On success a response with HTTP status 204 No Content is returned when an
old hash lock was updated for the channel.
Specific error codes
error value
HTTP response code
Error conditions
invalid_request
400 Bad Request
When one or more required parameters are missing or the user
has no access to hash lock
On success a response with HTTP status 201 Created is returned when new
hash lock was inserted for the channel.
On success a response with HTTP status 204 No Content is returned when an
old hash lock was updated for the channel.
Specific error codes
error value
HTTP response code
Error conditions
invalid_request
400 Bad Request
When one or more required parameters are missing or the user
has no access to hash lock
By default all Ustream channels can be embedded anywhere across the internet. By restricting the embed URLs, you can control the viewing experience and limit distribution to your own preferred partners.
With co-branding, you can display your brand prominently in the player. With full branding, you can even remove the default Ustream watermark.
No-branding allows removing the Ustream watermark and go with no watermark at all.
Your channel and videos will not be found anywhere on ustream.tv. Viewers will only be able to watch embedded players on external websites.
If you want the channel to appear only on your own website, make sure to restrict URL embeds to your site as well.
This feature enables a user (the master) to add managers to their channels with administrative rights.
The activated managers receive benefits of managed channels, independently from their current plans.
A managed channel can have at most 500 managers, but only 3 managers can be activated simultaneously by default.
Possible values: disabled, private, public. If the value is disabled,
no auto-recorded video gets created for the channel when broadcasting.
If the value is private, then the new auto-record will be
private by default. In case of public the created auto-records will be
public by default.
Response
On success a response with HTTP status 200 OK is returned.
Error codes
error value
HTTP response code
Error conditions
invalid_value
400 Bad Request
The specified value is invalid or unsupported.
payment_required
402 Payment Required
The user does not have access to control autorecord settings
Hooks can be registered for different channel events. When a channel event is fired, a HTTP POST request is sent to the registered hook recipient URL.
You can use to these endpoints with Client Credentials.
A newly registered hook is inactive by default. In order to make it active,
a basic handshake must be implemented at the recipient URL before the
hook registration.
After the hook was registered a POST request is sent to the recipient URL
with a X-Hook-Secret HTTP header.
Recipients must reply to this request with the same secret string in their
X-Hook-Secret response header to make sure that the registered recipient
URL is owned by the API user. This handshake request will also contain
an "event" and "channelId" in the body (JSON encoded) property with the
corresponding values of your freshly registered hook. Using these values
you can re-use the same hook to handle multiple secrets based on these
identifiers.
The property "when" will contain the exact time of the event occurred. Its provided
as a unix timestamp.
Your receiver should verify the signature provided in the request X-Hook-Signature header,
using HMAC-SHA1 algorithm with the the previously exchanged secret and the full request body as-is.