I want to join
Content Creator Community


İçerik Bulutu API


What to do with İçerik Bulutu V1 API?

You can reach İçerik Bulutu database by using API and integrate it into your applications, web sites or mobil applications. You can get detailed information about the facilities and advantages API provides from these 3 examples below.





1. For agencies

You have an agency and you are a İçerik Bulutu Client Centre user. The domain name of your company is ajansim.com.

You want to see the total trading size and your gain without connecting to İçerik Bulutu website or its mobile application. Your software developers can provide these datas easly by integrating our API into your website and creating a page similar to (Agency->Adminisration->summary-table API) “sirketim.com/publisher/gain”

Agencies can perform every transaction made for the publisher separately for every publisher working for them.
Besides,
  • Account
    • profile:Viewing profile
    • profile/image/save:Changing profile picture
    • balance:Viewing wallet
    • balance/payment: Payment request
    • bank/account:bank account list
  • Administration:
    • publisher/active: List of active publishers working for you (in paging pattern)
    • publisher/waiting:List of waiting publishers who hasn't confirmed contents (e-mail sent) (in paging pattern)
    • summary-table:Your summary table (publisher expense-gain amounts, in paging pattern)
    • publisher/create:Making registrations to the active publisher list
    • publisher/invite:Making registrations to the waiting publisher list through invitation



2. Useful Regulations

You can perform more complex transactions with these APIs when it comes to your part. For example, you want someone to be informed in your company, too when you revize a content you requested for your brand or your small business. After calling the related revizing mechanism (if you get the successfull transaction notice), your software developers can write any informative application easily. (For example; Publisher->Content->article/revision API)

  • Publisher
    • Publisher
      • profile:Viewing profile
      • profile/image/save:Changing profile picture
      • balance:Viewing wallet
    • Content:
      • advert:Access to your content list (in paging pattern)
      • advert/detail:Access to content details list (in paging pattern)
      • article:Access to content details registration
      • article/approve:Confirmation of content detail registration confirmed by the editor
      • article/revision:Revision of a registration confirmed by the editor
      • writer/preference:Evaluation of writers (favourite-banned)
      • project:project list




3. Work on your CMS or CRM

You can perform more complex transactions with these APIs when it comes to your part. For example, you want someone to be informed in your company, too when you revize a content you requested for your brand or your small business. After calling the related revizing mechanism (if you get the successfull transaction notice), your software developers can write any informative application easily. (For example; Publisher->Content->article/revision API)

Common: Common systems are the ones all users can access.
  • Help:
    • all:Question list of help desk (in paging pattern)
    • get:Question list of help desk (in paging pattern)
    • add:Adding new questions to help desk
    • comment:adding new comment-question column to an existing question
    • solved:Solving an existing question (marking as solved)


Is that all? Of course not.



We will move the whole İçerik Bulutu system to our API. However, we can bring forward some modules according to your needs. Please, do not hesitate to suggest new features to us. You can send an e-mail to api@icerikbulutu.com to get your access key to API and your documents.