CamShow API FAQ

1. Can we keep our site branding?

Yes, the CamShow API offers complete UI/UX flexibility. You create your room experience from scratch to match your existing site branding. Our Flirt4Free logos will not appear anywhere and none of your users should even know they’re using our models.

2. Is this expensive?

There are absolutely no out-of-pocket costs. We only charge you based on your customers’ credit usage.

3. Can users tip or is this just for private shows?

The API supports tipping and private shows. However, it does not currently support cam2cam shows, VOD integration, or show offers.

4. Does the API support RTMP & HLS?

Yes, we currently support both formats, but RTMP support will cease by June 1st 2017, so we highly recommend using the HLS stream. Furthermore, there are two CDNs delivering HLS streams, so we heavily recommend coding your integration so that it will switch to the other CDN in the event that the first CDN’s stream fails.

5. Do you provide a SDK or pre-built player/room experience?

At this time, no; the front-end interface must be developed by your team. We simply supply the models, stream information, and technology required to engage in chatting, tipping, and private shows.

6. Will you provide us with test model accounts so we can debug the integration?

Yes, each API partner can link up to two test models to their account, which they can use for testing purposes and have their private shows and tips automatically refunded to their test user accounts.

7. Is this something I can set up in a day or two?

While it is very straight forward, the API does take quite a bit of resources to develop, test, and launch. The average time from start to finish for our new partners is around ten weeks. It could be much shorter or longer, depending on your competency and development resources available.

8. Do you have any examples of active integrations?

Yes, of course. On this website we provide all of the male models for their cam experience:

And on this website we provide all of the female models for their cam experience:

As you can see, the integrations are drastically different and the UI/UX is completely determined by the API partners.

9. Do you have a sample workflow for how this should be integrated?

Every integration will be unique, depending on how exactly you want to use the CamShow API, but the general flow is as follows:

1. Call /performers to get a list of available models and their relevant stream info.

• Cache that info for at least 2-3 minutes.

2. Call /performerInfo for the online models to obtain more info about them

• Store that info in a database that you create specifically for this, or alternatively, in the database of models that you have already for your site.

3. When a customer wishes to join an open room, call the /customer path and use the joinRoom function.

4. Once in a room, call the /customer path and then use the pingRoom function every 10 seconds to let the system know that the customer is still in the room.

5. If the customer wishes to leave an open room, call the /customer path and use the leaveRoom function.

6. If the customer purchases additional credits or spends credits elsewhere on the site, call the /customer path and use the updateCredits function.

7. If the customer wishes to send a message from within a room, use the /message path.

8. If the customer wishes to send a tip from within a room, use the /tip path.

9. When a customer is ready to transition into a private show, call the /show path and use the showLogin function.

• Once you’ve received a positive response from the system, call the /show path again and use the showReady function.

• You will be returned new stream info to transition that customer into the private show.

10. When a customer is ready to end a private show, call the /show path and use the showLogout function.

11. Throughout all of that, your system should also be able to accept our system’s webservice postbacks which relay vital information:

• a.) performerStatus, which sends updated information about our performers as they transition into and out of private shows, go on break, and transition between online/offline states.
• b.) customerBoot, which indicates when one of your customers has become unruly and must be booted from a performer’s room (or booted from the system entirely).
• c.) message, which will send messages to your system whenever a performer, user, or system message should be displayed in chat.
• d.) showEnd, which will be sent at the end of every private show with the total credits used for that private show. It will also be sent in the event that a performer or our system ends a private show abruptly, prior to your customer choosing to do so.