Circuit Developer Community

Congratulations to the TADHack winners...

... and especially to our winner Jean-Luc Nguyen (@jeanlucnguyen) who used many of the Circuit API capabilities to create a Circuit module that can be plugged on any marketplace product page to allow customers to interact with other customers and product specialists via text, voice and video chat. He realized his hack within 24 hours and took home a prize of $1k.

Thanks Jean-Luc for the great hack and great presentation! More details will be published here soon.

 

http://blog.tadhack.com/2015/12/13/tadhack-paris-winners/

Circuit at TADHack in Paris

We are happy to present Circuit at the international developer scene at TADHack in Paris this coming week-end!

http://blog.tadhack.com/2015/11/23/circuit-by-unify-at-tadhack-paris/

TADHack Paris will run over the weekend of the 12th and 13th December at NUMA Sentier at 39 rue du Caire Paris, just before the WebRTC Conference and Expo. The hackathon will focus on WebRTC based on the resources of various sponsors, and Unify will be one of them. 

 

Remote entries are being accepted as well, so if you can not make it to Paris, you can still take part. You can find more detail about the TADHack concept and the Paris event on the following pages:

http://tadhack.com/2015/

http://tadhack.com/2015/tadhack-mini-paris/

Looking forward to meeting you at TADHack Paris on 12/13 December, and helping you realize your ideas on Circuit by Unify with the chance to win $1k in prize money :)

Jobs around Circuit Development

We just recieved the first requests from partners that look for engaged developers with Circuit skills. 

We will post these job offers here on developers.circuit.com

Another reason to register as a developer here and see the full content of the category...

See the first posting below. Dolatel (www.dolatel.com), based in Frankfurt/Germany is looking for a CTO. 

 

 

Another 3 days of code: #CircuitHack 4, going beyond...

Starting today, the Circuit APIs will be in the hands of Ixperta, one of our long standing, trusted development partners based in Brno in Czech Republic. After three successful internal hackathons, this is the first time that #CircuitHack happens outside of our own development sites. Ixperta is excited about the upcoming event. Having used Circuit for more than a year in their day to day work, they are eager to get their hands on Circuit as a platform for application development.

Ixperta primarily focuses on developing OpenScape 4000 components and devices for Unify. Ixperta developers have great experience in SW development in telecommunications and now, as they are getting ready for the hackathon, they are looking forward to enhancing their skills especially in the area of developing cloud solutions and modern web applications. They see this interesting opportunity to apply their own user experience with Circuit in Ixperta and ideally convert it into new Circuit features, contributing to the Circuit ecosystem.

In addition, the general idea of a hackathon – to develop things that are fun, cool and innovative, without solely looking at the market potential – is motivating and attractive to Ixperta. Five teams consisting of approx. 25 developers are looking forward to spending 3 days of creative hacking and team building, while exploring the full potential of Circuit’s open interfaces as they are available for the developer community here on our community pages.

Thanks to all of you, our Circuit developer community has been steadily growing since its launch in March 2015. Going forward, your continuous feedback as developers regarding the use of our APIs and Circuit's various integration opportunities is priceless. Over the last couple of months, we have been able to establish some very promising relationships with many of you, and we look forward to growing the community much more, making your products and ours even better. 

Curious to see what the Ixperta teams will come up with on Friday when they present their results!

Watch out for our tweets #CircuitHack #CircuitDev.

Freemium Pricing Model

Dear Circuit Developers and Unify Partners,

the developers.circuit.com page is usually a totally marketing-free zone and focus on the technical enablement of the growing Circuit developer community.

But, today's press release is so important to all of you, that I really need to make an exception.

We just unveiled the NEW CIRCUIT FREEMIUM pricing.

Check the new web pages: https://www.circuit.com/pricing and https://www.circuit.com/register

This step is a major milestone in the evolution and growing market success of Circuit. We enable teams of up to 100 people to use the full Circuit functionality* free of charge and with no time restrictions. Your data will still be there in many years, as long as you like.

The free subscription complements three commerical subscription levels, which provide larger tenants, higher quota of video- and storage-usage as well as seamless integration of telephony systems to turn Circuit into a easy-to-use UC solution. This is a very good fit not only for customers, but also for you, if you are an existing Openscape partner. Your customers can adopt Circuit for free team collaboration and WebRTC-to-WebRTC communication. But, if they really like to hook it into their existing PBX landscape (that you sold), or even like to replace Openscape UC with Circuit and the Advanced Telephony Connector, you will be able to sell the commercial Circuit subscription into your existing customer relation. There are also trial offerings for this level of Circuit. You will also participate ongoing in this revenue streams, as long a the customer subscribes to Circuit. Please reach out to your commercial Unify partner contact to learn about the details. Basically, we listened very well to our partners and have created a Freemium model, which drives massive adoption with the "free" part and fully involved the partner revenue streams in the "premium" upsell.

Many of you enjoy a free developer tenant and know Circuit quite well. The developer sandbox remains the place where you can try out APIs, do POCs and pilot Circuit extensions. The free subscription to the Circuit.com complements this with a mature productive cloud, where you can do your next real customer project, or sales presentation, or scrum meeting, or requirement brainstorming - and all with outstanding video and sound quality. 

Please enjoy Circuit and spread the news.

Stefan Ried, 
CTO

 

* The limiitations in the free usage intensity may be subject of change in the future. The Circuit telephony connector is not part of the permanent free subscriptom. The unversal telephony connector can be requested for a free permanent sandbox tenant out of the admin setting. For the commercial Circuit.com subscription, you can request a trial including the universal or advanced telephony connector.

Circuit SDK examples on Codepen and Github

A good number of code examples have been added to Codepen and Github during the last couple of months:

- Group call (audio & video)

- Messaging

- Direct call (audio & video)

- Circuit chat (Polymer example)

- Screenshare, etc.

 Use these to get started with Circuit! Your feedback is very welcome. 

https://github.com/yourcircuit/yourcircuit.github.io  

http://codepen.io/circuit 

WebRTC Video Codec Wars - The Enemy Of My Enemy is My Friend!

By Andy Hutton, Head of Standardization at Unify

In July 2015 following a day of meetings during IETF93 in Prague I had dinner with a number of IETF Video experts coming from the WebRTC & IMTC community and representing some browser vendors and application developers.  That very day the IETF (Internet Video Codec) NETVC had met to discuss progress on producing a new royalty free video codec for the internet and it probably was not a coincidence that those administering the HEVCAdvance patent pool had on the very same day been preparing a press release, which would tell the community how much they would need to pay to license HEVC (H.265) in future products. 

It turned out to be a very interesting discussion and that evening it became clear to me that there was an end in sight to the Video Codec wars which for so long had been the biggest failure of the whole WebRTC standardization effort.

A few months early during IETF91 the IETF WebRTC community came to a very rough consensus that both VP8 and H.264 should be mandatory to implement (MTI) for WebRTC browsers. However this decision really did not make that many people happy; a few maybe thought this was the end of the discussion but the majority were thinking that it was only the end of the beginning.

What really matters is not which of the current generation of video codec’s is supported by WebRTC 1.0 implementations but what will be the next generation codec for communication on the internet and here I have great optimism for the future.  That optimism is fuelled by the fact that many of those who had battled so hard in the IETF have now come together after realising that they do after all have a common goal and that is to support the development of an open and interoperable video codec for the future internet.   On Sept 1st many of those unlikely friends came together to form the Alliance for Open Media.  You might spot that there is still one major browser vendor missing (no prizes for guessing) but I would not be surprised if we see them join one day.

Now that we have Google implementing H.264 for WebRTC and Microsoft openly talking about VP9 support, the future is looking a lot brighter for WebRTC Video interoperability which can only benefit WebRTC and WebRTC platforms such as Circuit.

JS SDK now supports Group Calls

The new JS SDK now supports group audio/video calls (aka conferences).

Live example is on codepen

API documentation is updated.

 

Webinar: Update on the Circuit Developer Community, Thursday Oct 1st

Stefan Ried, CTO, Unify:

  • Quick overview of Circuit and our developer resources on developers.circuit.com
  • Outlook to the new extension framework, an easy way to package Circuit add-ons

Roger Urscheler, Application Architect:

  • Introduction to Javascript SDK
  • Status of JS SDK
  • Examples on Codepen and Github
  • NodeJS SDK
  • Polymer SDK

Here is the recording of the session:

 

 

Salesforce Customer Success With Circuit

 

Everybody globally enthusiastic about cloud computing is looking at the announcements, networking and spirit at Dreamforce in San Francisco this week.

Unify and I am onsite and meet Salesforce and Unify Customers and many Unify partners. Of course we brought something exciting with us:

The integration of Circuit and Salesforce.com

Based on the open APIs of the Circuit collaborative PaaS platform, Unify showed even two different Salesforce.com integration scenarios and technologies:

Circuit Salesforce Extension By Unify

This is the first Circuit extension leveraging the new Circuit extension framework, which will be officially launched and explained here shortly. This native Circuit extension use the Node-injection approach (register to see this article) and actually runs on Heroku using the already available APIs of the Circuit sandbox.

The current extension captures and filters business events such as new or changed leads or opportunities from Salesforce.com and turns them into Circuit conversations and posts with the related people.

The extension is a preview today and will be shared with full source code, here on developers.circuit.com around November this year. It's basically an advanced extension source template that should motivate you to build your own extension if you are a corporate developer, or even build a commercial Circuit extension if you are an independent software vendor or systems integrator. Everybody should feel free to productize more advanced packaged Salesforce-Circuit integration scenarios based on this source.

See the details here:

 

Salesforce-Circuit Integration Showcase By Informatica Cloud

Many enterprises don’t like to develop custom integrations on the coding level, even if the APIs are powerful. Many Enterprises like to have an easy-to-use middleware cloud service. One of the market leaders in that Salesforce.com ecosystem is Informatica Cloud.

I’d like to thank the Informatica Cloud team for putting together a very impressive showcase. It is just using the Informatica Cloud Application Integration product and the published Salesforce.com and Circuit APIs. All the rest is “just metadata” – meaning configuration of the Informatica Cloud service, that took about ONE DAY.

The showcase picks a very common situation of the sales cycle. Many sales reps just schedule meetings with prospects directly in salesforce.com. Most meetings are not in-person but remote, and you waste a lot of time to create a calendar invite, phone bridge and a screen share session in different tools manually. The Informatica-powered integration creates fully automated a Circuit conversation and sends a calendar invite including the WebRTC video link and traditional dial-in links to the participants of meeting.

I met Ronen Schwartz, GM of Informatica Cloud today. Please see our chat and the following demo:

 

Don't miss to register at developers.circuit.com to get access to the full details soon.

Register

New Node SDK

The improvements made to the Circuit JS SDK have been incorporated in the Circuit node SDK.

Architecture Changes

Public interfaces are implemented with Promises. Promises significantly improve control flow and provide robust error handling. The examples published on github show how promises can be used for both sequential and parallel execution flows.

The SDK’s external dependencies have been reduced to the bare minimum. The SDK’s footprint is smaller and the SDK’s performance is improved.

Internal caching has been removed from the SDK, providing more flexibility to applications for the selection of a caching strategy and implementation. Applications also have improved interfaces for access to conversation and user data.

New Functionality

The SDK provides support for Presence, Likes, and Flags.

Documentation

The documentation for the improved SDK is available on the sandbox

Examples

Updated examples are available on github

Download

The node SDK can be downloaded from the sandbox

Notes

The new SDK offers a simpler application interface based on Promises. Please note that the new promise based interface is not backwards compatible with the previous interface based on callbacks. Moving to the new SDK requires an application change. The promise based interface offers far better flow control and error handling to applications.

New light-weight JS SDK

Hi all, we have made some major improvements to our JS SDK. See the post by @rurscheler here on codepen.io.

Circuit Webinar For Technology Partners - Featuring ASC

Hello,

the last days have been horribly busy, but finally I found time to upload the recording of the Webinar we've done about two weeks back. The Webinar gave an overview of the APIs available here on developers.circuit.com and explains our future engagement with partners. 

 

 

My special thanks to Johann Böhme, developer at ASC Technologies AG. ASC is one of the market leaders in compliant long-term recording solutions, which we use frequently for Unify's contact center solutions or in the financial services industry that require a 10 year archiving of every message. In addition to  the recording of audio, ASC is now preparing the full recording of all chat messages, users type into Circuit conversations. Johann shared his awesome experience hooking ASC's recording solution up to Circuit within a few days: "The implementation of the demonstrated chat recording integration was very easy", says Johann. "Thanks to the well documented Circuit API, we were able to bring our proof of concept to competition within a few days."

If you like to jump to ASC's part of the recording, you can fast-forward to 37:50.

Don't hesitate to leave questions here or comments.

Stefan Ried

WebRTC Standardization – Re-Chartering of WebRTC, What does it mean?

By Andy Hutton, Head of Standardization at Unify

Welcome, my name is Andy Hutton, and I am leading Unify’s engagement in multiple standard bodies including the W3C WebRTC Working Group. I’d like to introduce myself in case you have any questions about the evolution of the emerging WebRTC standard. Let’s start sharing an update of the W3C WebRTC Working Group. It is currently undergoing a re-chartering exercise which is necessary because all the current charter has reached its end date, although it has had a temporary extension until the end of September, to allow work to continue.

I participated in a small W3C task force asked to come up with a new draft charter proposal as a previous attempt was found to be not acceptable to some of the W3C WebRTC Working Group Participant companies, you can probably guess which.

The new charter is currently under review by the W3C advisory committee which includes a voting period which has ended on July the 19th.  My expectation is that the new charter will be approved but that is not guaranteed and some major vendors have not yet registered their vote.

If the charter update is approved, I believe it will be an important milestone in the history of WebRTC standardization.  The new charter paves the way towards a future, in which WebRTC is supported by all the major browser vendors and we really have a unified WebRTC standardization community. Significantly Erik Lagerway, of Hookflash and editor of the ORTC specification, has already accepted the role of Co-Chair of the W3C WebRTC working group, so hopefully we will start to see WebRTC and ORTC merge into a single development path.

Importantly the proposed new charter contains the following statement regarding backwards compatibility:

The new APIs will extend the WebRTC 1.0 APIs, rather than replace them. Applications that use the PeerConnection API will continue to function, unless there is a clear and compelling reason to deprecate specific 1.0 functionality.”

This is an important statement for those developers already using the WebRTC 1.0 API’s and fulfils the desire of many in the community that ORTC functionality brought in to WebRTC will enhance the existing API’s rather than replace them. 

I saw in a recent presentation by Harald Alvestrand, Google and current WebRTC Co-Chair, that the current WebRTC 1.0 work is about “making it possible” and the next version will be about “making it brilliant” and I agree with that sentiment although WebRTC is already brilliant in many ways we can look forward to it getting even better.

In our recent Munich WebRTC meetup, I discussed the current movements with my colleague Jan Hickisch in a remote Circuit session. Here's a link to the recording if you'd like to listen in:

https://app.box.com/s/ldmpm0zvlfbz3dvsslfgne4frxt0rnmz

Don’t hesitate to comment here as a registered developer.

Update on July 27th: The W3C today announced the successful re-charting of the WebRTC group. The new charter can be found here. 

Sandbox Upgrade July 16th

Hi all, today, July 16th, the Circuit sandbox will be upgraded to the next sprint starting at 3 pm EST. It will be available again at 7 pm EST. Thanks for your understanding.

Unify’s Circuit cPaaS Now Available to All Developers

Over 300 developers have joined the community to create extensions to Circuit or use Unify’s WebRTC service in their application. Please see the full press release.

Register to see the full content of developers.circuit.com here

Register

 

Greece, Germany, Brasil - The next Circuit Hackathon is with YOU

Athens, Alsdorf, Curitiba -

Three #CircuitHack events prove openness of Circuit platform and inspire the developer community

The best way to validate a new development platform and APIs is to ask many developers who have never seen it before. That's what we did. Although a significant number of Unify developers are working on Circuit, there are another hundreds of developers, who have not been involved in Circuit so far and work on other Unify products. We asked specifically these people to try out crazy ideas in a short time period of 2-3 days and provide brutal feedback to the Circuit platform team.

These events went so well, that we'd like to share some of the more than 40 hacks, ideas and pilot implementations here. We are now in the process of planning the next Circuit hackathons open to all registered Circuit developers in Europe and the US.

 

1. Athens, Greece, February 2015

Text2Speech and Speech-Control

Team "Unicoders'" hack aimed to enable visually disabled users to use Circuit to collaborate via text2speech. The team used the following speech synthesis API in Chrome:

http://updates.html5rocks.com/2014/01/Web-apps-that-talk---Introduction-to-the-Speech-Synthesis-API

The pilot implementation shows how blind or visually disables people could signon to Circuit, navigate through their conversations, reply to a post etc - without touching the keyboard. It is also an ideal approach to work with Circuit while you are driving. See the video: https://www.youtube.com/watch?v=gtAT-DpaoA0 

 

Conversation Data Analytics

Based on analytics produced by Circuit conversation data, the team "DataCorruption" realized a data representation model that visualizes who’s talking or who should be talking to whom on Circuit. They used the Circuit Node.JS SDK and Heroku to help users to handle a mass of data by visualization. In contrast to an traditional instance messaging system all chat data, we call conversation data, is persistent. You can basically crawl through the data and understand who said something containing certain keywords to whom. The hack inspires also the collabroation with upcoming partners in the space.

 

 

AdvanvedVisualSearch2.png

 

 

Real-Time Gaming - Chess Example

"DataCorruption’s" second hack was to enable collaboration during a chess game: The client shows a chessboard instead of the conversation stream. Moves of the chess pieces are being translated into text messages. The real time chess game can be combined with a WebRTC video conference between the players. 

For more detail on this team’s hack, please contact us.

chess.jpg

  

 

Internet of Things - Connected Room

The idea of the "PowerRangers" team was to make Circuit interact with the physical environment, for example controlling lights/projectors in a meeting room, checking the temperature in a server room, etc. The team presented the following use case: An arduino platform is connected to lights in a meeting room lights, a projector, etc. When a Circuit user enters the meeting room, the platform informs Circuit about this event and a conversation with the meeting room name will pop up on the user’s screen. This conversation will contain the appropriate UI for controlling whatever is “controllable” in a meeting room. The ideas are flowing also in a future Unify product targeting the best Circuit meeting room experience. 

For more detail about this hack, please contact us.

  

Knowledge based search in Circuit based on specific algorithms

Did you ever have a question, but did not know who to ask? What if you had a genie to tell you who can help? Team Eureka introduced a “Guess who knows” genie in Circuit: First it searches all your conversations for a given keyword, second it ranks your contacts based on keyword occurences with a custom algorithm. We cannot share the full hack due to patent issues, but show it to developers under NDA.

For more detail on Eureka’s hack, please contact us.

 

We posted a blog article (link http://blog.unify.com/2015/03/circuithack-1/) and a video (link https://www.youtube.com/watch?v=Mw-97UuJMlo#) on the Athens #CircuitHack back in February.

 

Happy Athens winners:

winning team.jpg

 

 

2. Alsdorf, Germany, May 2015

Peer2peer File Transfer during Circuit Call with WebRTC data channel

The idea was to transfer files, for example big log files or media files, over the data channel inside a 1-to-1 connection, instead of using a file service. Circuit is heavily using the media channel of the WebRTC protocol, but we have not been leveraging the WebRTC data channel a lot until now. The hack shows how to transfer files from one participant to the other, leveraging the full speed and encryption of the WebRTC communication. It is an interesting alternative to the persistent file upload into an conversation. Such a non-persistent file transfer is even requested for compliance reasons by some Circuit customers. The "team" consisted of a single person, and also he had only about six hours time to realize his hack, which let us award him with the special "personal challenge" prizein Alsdorf. 

A cool, simple feature which can be easily expanded and integrated into Circuit:

 

FileTransfer.PNG

 

Integration of RSS feeds into Circuit

RSS feeds are being registered in a conversation. The relevant messages will be shown inside the conversation stream and thus being included in search. Challenges were the use of Heroku and Node.js as the team never used Node.js before. The source will be shared shortly.

 

Collaborative whiteboarding 

The team created "MIAU" - the “Mostly Indispensible Ansible Utilities”. It's basically a mashup of Circuit and a collaborative whiteboarding, based on a downloadable Chrome extension which places an additional icon next to every Circuit conversation http://tiny.cc/miau 

 

MIAU.PNG

 

 

Streaming of external media sources into a Circuit conversation

Team "Hackman" was the winning team in Alsdorf, Germany. This hack was about integrating external streaming sources into a Circuit conversation. For example, a YouTube video stream (broadcast) can easily be integrated into the conversation and broadcasted to all participants. This could be interesting for e-learning offerings from universities or further education institutions:

Hackman Youtube streaming.PNG

 

In reverse, any Circuit RTC conversation can be broadcasted live to webcast, live-streaming or recording systems. For more detail about Hackmans’ ideas and hacks, please contact us.

 

Lightweight CRM based on Circuit:

This idea focused on customer relationship management. SMBs who don’t want to run a real CRM system can use a lightweight CRM system based on Circuit. The hack showed basically how to use Circuit's persistence to store information about customers if Circuit is used in the customer engagement process. When communicating with a certain customer, the system will provide all the existing data about this particular customer, right in the converesation with an incoming call.

 

Read more about the Alsdorf #CircuitHack in the Unify bloghttp://blog.unify.com/2015/05/unify-developers-gather-alsdorf-2nd-circuit-hackathon/

Team pic.PNG

 

 

3. Curitiba, Brazil, June 2015
 

Integration of Circuit into OpenScape Contact Center

Our winning team, "OS CC Rocks", integrated Circuit with Unify’s OpenScape Contact Center solution. The idea is to use Circuit as call center agents’ devices for processing calls, instead of using a hard phone or PC softclient. As you can see in the video linked below, it is really integrated into the Unify OpenScape Contact Center solution.

The team used the Circuit JS API in order to allow WebRTC calls to the Contact Center. The Circuit users’ presence information was monitored by OSCC. Customers on a public web page (bottom right picture) will even see in real time when an agent is available for an audio or video call. 

https://youtu.be/UCruK_vg0TY

OS CC screenshot.PNG

 

Internet of Things and Business Event Integration

The "Power Circuit" Team won the special engagement prize in Curitiba, as they developed four different small projects in only four days, in addition to their day-job. See all in this video: http://youtu.be/Rzqi_IYGGQU

- Bizagi (Business Process Management Software) ticketing system integration with Circuit

 

Bizagi integration.PNG

- Web Cam camera movements controlled by Circuit (used by Call Center Supervisors). Supervisor’s video camera positioning via Circuit. Please contact us for more detail.

camera movements.PNG

 

- Circuit messages displayed on an LED wallboard (in order to display Contact Center statistics).

 

Wallboard Unify Curitiba.PNG

 

- Unify OpenScape Contact Center Web Chat and Circuit Integration.

web chat integration.PNG

 

Circuit Feedback

Circuit Feedback was a hack developed by Celso Sidor, the Team "One Man Band". It allows anyone in a Circuit conversation to request feedback or votes from other people in the conversation. People will be notified about the feedback request, and the result will be automatically compiled based on certain parameters defined by the requesting person. This is a great idea to facilitate the decision making process inside teams.

Meanwhile you can find a similar "voting button" as an alpha feature rolled out to the Circuit productive cloud. 

For more detail on Circuit Feedback, please contact us.

Circuit Feedback.PNG

 

Outlook Social Connector

This is a hack integrating Outlook 2010 and 2013 with Circuit for an easy migration to or co-existence with Microoft Outlook. With one click, e-mails and meeting appointments can easily be copied into a Circuit conversation. And Circuit members' information can also be visualized on Outlook. This hack was done based on the Outlook Social Connector: https://blogs.office.com/2010/07/13/use-the-outlook-social-connector-with-facebook-linkedin-myspace-and-windows-live/

For more detail on Circuit Social Connector, please contact us.

And, yes, we we will definitely be productizing this very soon!

 

Happy Curitiba winners:

winning team1.PNG

 

 

We hope this gives you a feeling of the spirit and fun of developing with Circuit! While Circuit comes with its outstanding strength of modern WebRTC based communitcation, each of you can turn it into the magic glue between people, any kind of document content, and business events. At the end, communication, collaboration and business networks and even the Internet of Things get into one simple context - provided by Circuit.
 

developers.circuit.com

Circuit Developer Community Available Now

Register

Today, Unify introduced a developer community around its cloud based collaboration service Circuit. We are excited to open up a wide range of Circuit APIs to external developers as a beta program. This is a key step towards establishing Circuit as the leading collaborative Platform-as-a-Service (cPaaS), and an industry first. We are offering two sets of APIs, which offer a variety of integration scenarios and the possibility to write applications "inside" Circuit. You will be able to integrate your apps and services into the Circuit collaboration platform. That way, your customers can access capabilities and data you provide within the business collaboration context that Circuit provides. Second, we expose Circuit WebRTC real-time capabilities like voice, video or chat through standard APIs.  So you, our technology partners, independent software vendors, or corporate developers can enhance your web apps, mobile apps, CRM- or ERP systems with a minimum development effort. Basically, the Circuit cPaaS can consume business logic from any existing legacy or cloud resource and can provide real time services to anything else:

 

We have tested these APIs during a hackathon that we organized at our development lab in Athens, with developers who have not been in touch with Circuit before. See some of the amazing first results in this article on NoJitter. In a few months from now, we'll start planning public hackathons in the US and in Europe. 

 

How to get started:

Everybody can register for the free Circuit developer community membership. Just click register on this page.    
 

Here is what you will find on developers.circuit.com:

  1. News: Announcements of new APIs, code snippets, sample applications, community members to chat with, etc.
  2. cPaaS use cases: Collection of blog posts about use cases of a collaboration PaaS, helping developers navigate the different sets of APIs.
  3. APIs: Access to the Circuit API portal (beta) with REST, Javascript APIs, and a Node module. More mobile APIs will follow later. Interactive testing of Javascript and REST APIs. The APIs are currently holding hundreds of calls already and enable external developers – it‘s all ready to start.
  4. Samples: Growing number of posts, one for each sample, including corresponding samples stored on GitHub or CodePen.
  5. Sandbox: Your free developer account on CircuitSandbox.net, where you can try your new code or point APIs to. The sandbox is one sprint ahead of the current production environment. There are no functional restrictions to the sandbox compared to the commercial Circuit subscription. Only data volume, number of members, data persistence across releases arerestricted, and there is no commercial support for the free sandbox accounts.

   
 
We are looking forward to engaging with you! If you have any further questions, please contact our developer community manager Eva Hoertrich.

Have fun with developers.yourcircuit.com

 

Stefan Ried

CTO

   
 

 

Circuit APIs Overview

REST And Javascript/WebSockets

REST or WebSockets? This is almost a religious discussion among developers. We simply support both - as one or the other makes more sense depending on the use case. 

  • The Circuit REST API works great for many integration scenarios across different languages and frameworks. 
    REST is the fastest way to get started for many use cases. Imagine you are scanning an ERP system for important business alerts and you would like to post these alerts to a Circuit Conversation. This can be quickly done with the REST API. There is a restricted set of REST APIs available initially. 
     
  • The Circuit Client Javascript API/Library uses WebSockets to connect to Circuit. To rapidly enhance a Web-App with multi-party voice, video, and real-time chat sessions we provide an easy to use JavaScript library. Developers can enhance or create a Web-App as illustrated on CodePen with just a few API calls. The library encapsulates real-time signaling and connectivity via WebSocket. The connected nature of the WebSocket allows the library to efficiently receive asynchronous events even when located behind a FW/NAT device.
     
  • The Circuit NodeJS Library/Module also uses WebSockets connectivity and provides quick integration opportunities with the rapidly growing node.js community. We are also packaging the Circuit JS library as node.js module. The Circuit node.js module provides quick integration opportunities with the vast number of available node modules. Code samples for the Circuit node.js module are on GitHub. See the also Circuit's Node Injection concept.

All bookmarks for your overview:

  1. Dev Community: http://developers.circuit.com/
  2. Sandbox: https://circuitsandbox.net
  3. Client JS SDK Doc: https://circuitsandbox.net/sdk/index.html
  4. Client JS SDK Samples: http://codepen.io/circuit/
  5. NodeJS SDK Doc: https://circuitsandbox.net/sdk/#toc2
  6. NodeJS SDK Samples: https://github.com/yourcircuit
  7. REST API & Doc: https://rest.circuitsandbox.net/swagger-ui/index.html

 

 

 

Limitations Of The Current API Release

A commercial cloud platform is about reliability and openness. 

Of course, you as an independent developer, system integrator, software vendor, or corporate developer like to have a reliable, secure, fast, rich and open cloud platform. This can't be for free. But, before we talk about commercials, you need to see how the technology works. That's why we run the free developer community in addition to our commercial cloud service.  

A free developer community is about learning, exchange of ideas, finding opportunities and fun.

Before you get started, please be aware of the some limitations explained below. Many of our partners, system integrators and ISV, told us that they like to learn the APIs as soon as possible and don't care about possible changes. We hope you share this mindset.

Alpha - Beta - Production is the plan. Alpha is the current stage!

All APIs and SDKs are in alpha stage. They might change in coming sprints. We hope to announce major changes here on developers.YourCircuit.com, but some might change without any notice. We will watch carefully which APIs are actually used, and we also listen to you which APIs you like most and which ones you don't care about. Those APIs that are most used and wanted will make it into the beta stage of an upcoming sprint. You can count on beta APIs for your real applications and integration. There might be still bugs - as in any beta - but beta APIs will not disappear in the following production version of Circuit. General available APIs in an production release will not disappear in future production releases (if they are actually used).

As Unify drives sprints of only two weeks with our scrum teams, everything moves really fast. Don't hesitate to get familiar with the APIs now, and check the versions again before you do the final coding for commercial projects. The CircuitSandbox is always ahead of the production environment to provide developers an opportunity to test extensions ahead of time.

CircuitSandbox today - APIs to production soon.

We restrict the current API access to the CircuitSandbox. We do not open API access to our production instances in the US or in Europe at this point in time. We are currently in the process of creating an appropriate API security shell around our production environments and to develop protection policies. Once we have done this, we will give developers access to the production YourCircuit.com. If we see intentional misuse of API access or data volume, we might delete your developer membership.

We move fast - maybe too fast to migrate your Sandbox data.

The CircuitSandbox usually keeps your conversation data. However, if a sprint does major changes in the data model on our Cassandra environment, we do not migrate your test conversations. You might get an empty CircuitSandbox tenant suddenly. But, don't worry, this will never affect code that you keep elsewhere anyway; it will also not affect the conversations you shared with other developers on YourCircuit.com (see more details here).

Community Support - Blogs, Code Samples, Circuit conversations open to all developers.

The current API have no commercial support offering yet. We actively read comments to these blog posts or any public conversations you post on YourCircuit.com. We also like to create more code samples addressing the most common questions and hope you also contribute some. Please use these channels to ask questions or point us to bugs.

Pricing - Will be fair.

If you have a commercial YourCircuit.com subscription, most likely additional access to this user via APIs will not cost anything. However, if you like to consume Circuit in components without using the full application at all, we will have an industry typical API pricing. As Circuit's combination of WebRTC functionality and conversation data is new to the market, we'd like to learn your usage patterns to come up with a fair pricing. We do our best leveraging a massively scaled out and leading IaaS underneath of Circuit, to have the lowest possible production price for the best possible HD experience.

A commercial user subscription is currently at €/$ 14,99 per user/month.

 
— 20 Items per Page
Showing 20 results.