Gininet

Welcome to Gininet!

Our mission is to deliver an easy-to-use streaming solution to any application from one to one conversations to simple live streaming, conference or interactive broadcast to a large audience.

In the following, we will show you how to use Gininet in your live streaming media project and the options you have from no coding at all to full integration of the Gininet API.

Easiest way to use Gininet

You need to use only the Gininet API Self-Service Platform to create and deliver your live event. No coding or long integration and testing.


You need an account.

You need to create a project.

Then create your event.

Issue tickets for your viewers.

Download the tickets and send the ticket URLs in email to your users.

15 minutes before your events starts start testing and setting up your session.

You audience join the session when the session officially starts.

Download your recorded archive

As you can see, you can use Gininet without any technical knowledge. However, we recommend to have some experience in basic text editing like copy and paste and using email client software.

Please continue reading to understand how Gininet works and what other options you have to customise and perfect your live, interactive streaming activities.

Key facts

Events created on this platform are NOT promoted or listed on our platform or any other way.

We do NOT sell or deliver tickets to your events.

We do NOT sell your or your ticket holders' data captured by our system. (see our T&Cs)

The Gininet API and the Gininet API Self-Service Platform help you to deliver your live streaming event and to control access to it. (see our other products).

Concept in a nutshell

Scheduled sessions

When you create your session, you need to specify when it starts and when it ends.

Session types

Based on your concept, you can choose from different Session Types from Simple Broadcast to Interactive and Conference sessions which can be broadcast to a large number of viewers. (more about session types)

Access control and roles in a session

In a Gininet session, participants have roles and they must present a valid and unique access code, called the ticket. (more about roles)

Streaming in

Gininet accepts RTMP (only Simple Broadcast session type) and WebRTC streams from 15 minutes before the session starts. (more about how to publish an RTMP stream) (more about WebRTC streaming in)

Requirements

Audio-Video Interactive ticket holders and the Presenter must use a WebRTC-capable platform, except in case of a Simple Broadcast Session, when Presenter can use RTMP to publish a stream in. Client side of other ticket types (Text-Chat Interactive and Non-Interactive) and Presenter in a Simple Broadcast session require a platform with HTML5 video or h.264+AAC playback capabilities. (more about roles)

Using Gininet without coding

We provide not just a dry API interface to work with but a complete web interface known as the Gininet API Self-Service Platform.
This enables you to create your broadcast simply and easily - no coding required.

Of course, a full integration has many benefits including giving you a complete white label solution.

Example scenario:

Let's assume, you have a blogging website, by using Gininet, it becomes a video blogging website, where your users attend your weekly live, interactive broadcast.
You know your users' email addresses because they signed up to your newsletter for instance, so you can issue and deliver tickets to each of them.
You create your event and issue as many tickets as needed, for instance 100 TC tickets. You download the list of tickets as a CSV file.
When sending your newsletter, you simply add the unique, generated ticket URL into the template from the CSV file.

Example:

Hi {username},

Our next live broadcast, "Next awesome broadcast" is live on 14th September, at 7pm EST

Please find your personal ticket to the event:

http://gininet.com/embed?ticket={ticketid}

This newsletter has just become an invitation to your live, interactive broadcast.

You need a Gininet account

Go to the Gininet website and from the menu, select the Gininet API menu item. On this page, you can find various methods to sign in, including registering with your email or using your Google, Github or Twitter account to sign in.

Create your project

After signing in, you can find a 'My Projects' item on the sidebar menu on the left hand side. Click on the plus symbol on the right hand side of that menu item to start adding your project.

Fill the form on the page and click on the 'Create project' button.

Create an event

After signing in, please find the 'My projects' section on the sidebar menu. If you have created a project earlier, you can find your project in the list just under this line. Click on your project to open it.

Find the 'Create event' button on this page and click on it.

Fill the form on this page and click on the 'Create event' button.

Create your tickets

On the event's page, find the 'Issue tickets' button and click on it.

Select the type and amount of tickets that you request.

The list of tickets can be downloaded as a CSV file.

Deliver tickets to the ticket holders

Use the downloaded CSV file to send the tickets to their ticket holders one-by-one via your email client.

By using a template and simply feeding the CSV file into your email client or online mass email sender services like MailChimp or Sendinblue you can shorten the procedure significantly.

Start your event

15 minutes before your event starts, you can find a 'Start publishing' button on the event's page to make you able to set your scene.

Your guests are able to join your event when the event starts using the ticket URL that you previously requested.

Download your recording

30 minutes after your event finished, you are able to download the automatic composite recording of your session.

Go to the events page and find the Automatic composite archive section

Find the Download recorded content button

From this dialog, download all of the items by clicking on the download button on the right hand side of each video record

An event may have multiple recorded files due to interrupted publishing of stream.

The recorded video is available for download for two weeks after the event finished.

Please note that we automatically remove recordings after the two weeks period.

Using Gininet Embedded Session

If you want to deliver the session on your own page, the Gininet Embedded Session is the perfect choice.

You will need to issue tickets on the Gininet.com and uniquely assign each ticket to a user who can access the event. For instance:

Example scenario:

Let's assume, you have a blogging website, by using Gininet, it becomes a video blogging website, where your users attend your weekly live, interactive broadcast.
The articles and other content are available after the visitor registered an account on the blogging website and signed in.
You create your event and issue as many tickets as needed for all or a selected group of users, for instance 100 TC tickets and 1000 NI tickets.
You save the tickets (id or url) in your database, assigning a ticket to each user.
When the user visits the article's page, your application reads the user's ticket url from the database and uses it in the source code as the source of the iframe tag of the Gininet Embedded Session. (for more information, see below at "Deliver tickets to the users")

You need a Gininet account

Go to the Gininet website and from the menu, select the Gininet API menu item. On this page, you can find various methods to sign in, including registering with your email or using your Google, Github or Twitter account to sign in.

Create your project

After signing in, you can find a 'My Projects' item on the sidebar menu on the left hand side. Click on the plus symbol on the right hand side of that menu item to start adding your project.

Fill the form on the page and click on the 'Create project' button.

Create an event

After signing in, please find the 'My projects' section on the sidebar menu. If you have created a project earlier, you can find your project in the list just under this line. Click on your project to open it.

Find the 'Create event' button on this page and click on it.

Fill the form on this page and click on the 'Create event' button.

Create your tickets

On the event's page, find the 'Issue tickets' button and click on it.

Select the type and amount of tickets that you request.

The list of tickets can be downloaded as a CSV file.

Deliver tickets to the users

Save the tickets in your database, assinging a ticket to each user in the selected group.

When the user visits the article's page with the live session you simply embed our Gininet Embedded Session using an iframe tag and the ticket url as source.

<iframe src="https://gininet.com/embed?ticket= <ticket ID> " allowfullscreen="true" allow="geolocation; microphone; camera" ></iframe>

Example:
<iframe src="https://gininet.com/embed?ticket=9cefc4b214594d63a1cb4a47f557fc81" allowfullscreen="true" allow="geolocation; microphone; camera" style="width:100%" class="responsivegininetsession"></iframe>

Start your event

15 minutes before your event starts, you can find a 'Start event' button on the event's page to make you able to set your scene.

Your visitors are able to join your event when the event starts.

Download your recording

30 minutes after your event finished, you are able to download the automatic composite recording of your session.

Go to the events page and find the Automatic composite archive section

Find the Download recorded content button

From this dialog, download all of the items by clicking on the download button on the right hand side of each video record

An event may have multiple recorded files due to interrupted publishing of stream.

The recorded video is available for download for two weeks after the event finished.

Please note that we automatically remove recordings after the two weeks period.

Using the Gininet API

By using the Gininet API, you can automate a few tasks like issuing a ticket, or creating an event.

You can still use our embedded session to make things easier or you can implement your own client side. See more about Gininet Client Side API

Example scenario:

Let's assume, you have a blogging website, by using Gininet, it becomes a video blogging website, where your users attend your weekly live, interactive broadcast.
The articles and other content are available after the visitor registered an account on the blogging website and signed in.
You create the article in your application, create a Gininet event using the Gininet API and save the event's id in the article's record. See Create Event API call for more information.
When a user visits the article the first time, the application backend requests an access code using the Gininet API and saves it in the database. Next time it uses the stored ticket. See Create Ticket API call for more information.
You can dynamically insert the Gininet Embedded Session in the article using an iframe tag and the ticket url (containing the ticket id) or alternatively, you can implement your own client side. See Gininet Client Side API for more information.

You need a Gininet account

Go to the Gininet website and from the menu, select the Gininet API menu item. On this page, you can find various methods to sign in, including registering with your email or using your Google, Github or Twitter account to sign in.

Create your project

After signing in, you can find a 'My Projects' item in the sidebar menu on the left hand side. Click on the plus symbol on the right hand side of that menu item to start adding your project.

Fill the form on the page and click on the 'Create event' button.

If you have an account-scope access token, you can use the '/project/create' API endpoint to POST the required information. For more information, see the API documentation.

Create an access token

On your project's page, please find the 'Access tokens' list. Click on the plus symbol to add a new access token

Important: Do not share your API access token and never expose it to the client side.

If you have an account-scope access token, you can use the '/apitoken/create' API endpoint to POST the required information. For more information, see the API documentation

Create an event

POST the event's data to the '/event/create' API endpoint

For more information please see the API documentation's create event section

Start your event

15 minutes before your event starts, you can find a 'Start publishing' button on the event's page to make you able to set your scene.

Your ticket holders are able to join your event when the event starts using the ticket code that you previously requested.

Create your ticket

When your user needs it, make a POST request to the '/ticket/create' API endpoint to get an access code. For more information, see the API documentation

Deliver this ticket code to your visitor's client side

Start the client side

After you transferred the user's ticket code to the client side, you can either start the Gininet Embedded Session or use your own implementation to deliver the event to your user. For more information, see the Client side API documentation

Download your recording

30 minutes after your event finished, you are able to download the automatic composite recording of your session.

Go to the events page and find the Automatic composite archive section

Find the Download recorded content button

From this dialog, download all of the items by clicking on the downbload button on the right hand side of each video record

An event may have multiple recorded files due to interrupted publishing of stream.

The recorded video is available for download for two weeks after the event finished.

Please note that we automatically remove recordings after the two weeks period.