Streak methods

I have implemented following methods in Streak API

• getUser : This call will return the details for the user specified

• getPipeline: Return all pipeline details related to use

• getSpecificPipeline : Return a specific pipeline

• createPipleline : Create a pipeline for a user with a specific name

• editPipeline : Edit an existing Pipeline

• getBox : return all boxes 

• getBoxInPipeline : Return all boxes in a specific pipeline

• createBox : Create a box for the user

• editBox : Edit an existing box

• getStage : return all Stages

• getSpecificStage : Return a specific Stage

• createStage : Create a new Stage for the user

• editStage : Edit an existing Stage

• getTask : return all tasks

• getSpecificTask : Return a specific Tasks

• createTask : Create a new Tasks for the user

• editTask : Edit an existing Tasks

• getFields : Return all fIelds

• getSpecificField : Return a specific Field

• createField : Create a new Field for the user

Streak API

About Streak API

Advantages of Streak gmail based CRM

• Streak is the developer of an eponymous customer relationship management platform for Gmail.

• Receive a notification when your proposal is viewed, and you’ll know exactly when to follow up. Know if your email is read and not responded to, or never reaches the recipient.

• Know if your support message has resolved an issue or if the contact hasn’t yet read your helpful message.

• Streak creates a visual of the history of your message views so you can understand what's happening at a glance.  

• Access a full list of every time (and device type) the message has been read.

• Know to a neighborhood level what part of a city your recipient has viewed your message.

• Sort your email not by when you sent it, but when it was viewed. Streak helps you see which messages are generating a response.

• See all the messages that need follow up in one location.

WealthboxCRM methods

I am going to implement following methods

1. Retrieve activity stream            : This endpoint will return all of the activity stream                                                                    items for the user who  has authenticated with                                                                             their access token.
2. Retrieve all contacts                  : When fetching contacts, results can optionally                                                                      be filtered by the following parameters (contactType,                                                                name, email, phone, active, householdTitle,type, order)
3. Create a new contact                 : This endpoint use to create a new contact.
4. Fetch Contact                            :  Retrieve all contacts. 
5. Fetch an existing contact           : Retrieve a specific contact using it unique identifier. 
6. Update an existing contact        : Update a specific contact using it unique identifier.
7. Delete an existing contact          : Delete a specific contact using it unique identifier.
8. Retrieve all tasks                        :  This endpoint will fetch all of the tasks that                                                                        are accessible by the user.
9. Create a new task                        : This endpoint use to create a new task.
10. Fetch task                                    :  Retrieve all tasks. 
11. Fetch an existing task                  : Retrieve a specific task using it unique identifier. 
12. Update an existing task               : Update a specific task using it unique identifier.
13. Delete an existing task                : Delete a specific task using it unique identifier.
14. Retrieve all workflow templates : This endpoint will fetch all of the workflow templates                                                                   that are accessible by the user.
15. Update status of a workflow step : This endpoint use to update a status for workflow step.
16. Retrieve all events                        :  This endpoint will fetch all of the tasks that are accessible                                                             by the user.
17. Create a new events                      : This endpoint use to create a new events.
18. Fetch events                                  :  Retrieve all events.
19. Fetch an existing events               : Retrieve a specific events using it unique identifier. 
20. Update an existing events             : Update a specific events using it unique identifier.
21. Delete an existing events              : Delete a specific events using it unique identifier.
22. Retrieve all opportunities              :  This endpoint will fetch all of the opportunities that are                                                                  accessible by the user.
23. Create a new opportunities             : This endpoint use to create a new opportunities.
24. Fetch opportunities                         :  Retrieve all opportunities. 
25. Fetch an existing opportunities       : Retrieve a specific opportunities using it unique identifier.
26. Update an existing opportunities    : Update a specific opportunities using it unique identifier.
27. Delete an existing opportunities     : Delete a specific opportunities using it unique identifier. 
28. Retrieve all projects                        :  This endpoint will fetch all of the projects that are                                                                              accessible by the user.
29. Create a new projects                      : This endpoint use to create a new projects.
30. Fetch projects                                  :  Retrieve all projects. 
31. Fetch an existing projects                : Retrieve a specific projects using it unique identifier. 
32. Update an existing projects             : Update a specific projects using it unique identifier.
33. Delete an existing projects              : Delete a specific projects using it unique identifier. 
34. Retrieve all notes                             :  This endpoint will fetch all of the notes that are                                                                              accessible by the user.
35. Create a new notes                           : This endpoint use to create a new notes.
36. Fetch notes                                       :  Retrieve all notes. 
37. Fetch an existing notes                     : Retrieve a specific notes using it unique identifier. 
38. Update an existing notes                  : Update a specific notes using it unique identifier.
39. Delete an existing notes                   : Delete a specific notes using it unique identifier. 
40. Retrieve all reports                           : This endpoint will fetch all of the reports that are                                                                             accessible by the user. 
41. Fetch an existing report                     : Retrieve a specific report using it unique identifier.
42. Retrieve all comments                       : This endpoint will fetch all of the comments that are                                                                     accessible by the user   for the                                                                                                            specified resource.

amoCRM methods

I am going to implement following methods

• Account 
• Though API, you can obtain all necessary information about the account: name, paid period, account’s users and their privileges, guides on custom contact and lead fields, lead status guide, event types guide, task types guide and other account parameters. 
•  getCurrentAccount  : Acquisition of information on the authorized account.

• Lead 
• This is one of the general entities of the system.
• It consists of a predefined set of fields and custom fields created by the account administrator.
• Each lead can be linked to one or more contacts, or to none.
• A responsible user may be assigned to each lead in order to assign access privileges among the account’s personnel.
• Each lead has a status, which specifies the current position of the lead within its lifecycle (business process). 
• Status must be necessarily assigned to any lead. 
• The list of statuses within the account may be changed except for two final system statuses. 
• createLeads : This method allows to create new leads, and also to update                                         information on the already existing leads. 
• getLeads : This method allows obtaining detailed information on already created                         leads with possibility of filtration and page-by-page selection.
• Company 
• This entity is identical with “contact” entity.  
• It consists of a predefined set of fields and custom fields created by the account administrator. 
• Each company may take part in one or more leads, or may be not linked to any leads at all. 
• The e-mail address and phone number are used as identifiers in association with other systems. 
• A responsible user may be assigned to each company in order to assign access privileges among the account’s personnel.
•  getCompany : A method for obtaining company lists with possibility of filtration                             and page-by-page selection.
• createCompany : This method allows to add companies one by one or in                                             packages, and also to update data for the already existing                                           companies. 
• Customer 
• A customer is similar to a lead. 
• It consists of a set of preset fields, and account administrators can add additional custom fields. 
• Each customer may be attached to one or more contacts or not attached at all.
• For every customer, user access rights can be modified including assigning a user as the responsible manager. 
• The current stage that a customer is in is also displayed. 
• Stages represent the position of the customer in the purchase process.
•  getCustomer  :  This method allows obtaining detailed information on already                                   created customers with possibility of filtration and page-by-                                     page  selection. 
•  createCustomer :  A method that allows you to create / update / delete a                                                customer individually or in batches.
• Transaction 
• A transaction is the main characteristic of a purchase (date and amount) and is connected to a "customer".
• createTransaction : A method for getting a filterable list of transactions. 
• getTransaction :  A method for getting a filterable list of transactions.
• Task 
• Each task must necessarily have a responsible user and date (day and time) assigned to it.
• Also, a task may be linked to a lead or contact, but not necessarily.
•  It may be not linked to any object.It is possible to set a result for a completed task by means of POST notes/set method. 
• createTask : This method allows to create new tasks, and also to update                                         information on the already existing tasks.
• getTask : A method for obtaining a list of already created tasks with possibility                      of  filtration and page-by-page selection.  
• Custom fields 
• This method allows creating or deleting custom fields one by one or in packages. 
• The user will not be able to change their values from the interface, but can browse them and use them for filtering.  
• Creation or deletion of a field is also possible from the interface. 
• getCustomFields : This section describes how to transmit values of custom fields.

Buffer API methods

I am going to implement following methods.

User
A user represents a single Buffer user account.

methods

• getUser - A user represents a single Buffer user account.   
• createAuthorize - Deauthorize your client for the user.

Profiles
A Buffer profile represents a connection to a single social media account.

methods

• getProfiles - Returns an array of social media profiles connected to a users account.
• getProfilesId - Returns details of the single specified social media profile.
• getProfilesIdSchedules - Returns details of the posting schedules associated with a social media profile.
• postProfilesIdSchedulesUpdate - Set the posting schedules for the specified social media profile.

Update
An update represents a single post to a single social media account. An update can also include media attachments such as pictures and links.

methods

• getUpdatesId - Returns a single social media update.
• getProfilesIdUpdatesPending - Returns an array of updates that are currently in the buffer for an individual social media profile.
• getProfilesIdUpdatesSent - Returns an array of updates that have been sent from the buffer for an individual social media profile.
• postProfilesIdUpdatesReorder - Edit the order at which statuses for the specified social media profile will be sent out of the buffer.
• postProfilesIdUpdatesShuffle - Randomize the order at which statuses for the specified social media profile will be sent out of the buffer.
• postUpdatesCreate - Create a new status update for one or more profiles.
• postUpdatesIdUpdate - Edit an existing, individual status update.
• postUpdatesIdShare - Immediately shares a single pending update and recalculates times for updates remaining in the queue.
• postUpdatesIdDestroy - Permanently delete an existing status update.
• postUpdatesIdMove_to_top - Move an existing status update to the top of the queue and recalculate times for all updates in the queue. Returns the update with its new posting time.

Links
A link represents a unique URL that has been shared through Buffer.

methods

• getLinksShares - Returns an object with a the numbers of shares a link has had using Buffer.

Info
This namespace is used for auxilary information that can be useful when creating your app.

methods

• getInfoConfiguration - Returns an object with the current configuration that Buffer is using, including supported services, their icons and the varying limits of character and schedules.

Reference for WealthboxCRM

For get to know more about wealthboxCRM

• http://www.wealthbox.com/api/

• http://www.wealthbox.com/blog/

• https://apiant.com/connect/Wealthbox-CRM-to-OpenSocial

• https://zapier.com/zapbook/wealthbox/

• http://www.wealthbox.com/company/tech-partners/

• http://www.businesswire.com/news/home/20160628005563/en/Wealthbox-CRM-Advizr-Announce-Integration

• https://zapier.com/zapbook/wealthbox/

• https://zapier.com/zapbook/gmail/wealthbox/

• http://www.prnewswire.com/news-releases/wealthbox-crm-announces-integration-with-orion-300263543.html

• http://www.prnewswire.com/news-releases/wealthbox-crm-releases-an-api-to-enable-fintech-integrations-for-financial-advisors-300214335.html

• http://www.destinationcrm.com/Articles/CRM-News/CRM-Across-the-Wire/Wealthbox-CRM-Launches-for-Financial-Advisors-94775.aspx

• http://fppad.com/tag/wealthbox-crm/

• https://insurancenewsnet.com/oarticle/Wealthbox-CRM-Brings-Simplicity-and-Social-Networking-Design-to-Managing-Advisor-a-459427#.WeDblGiCxPY

Buffer API

About Buffer API

• It is a software application for the web and mobile, designed to manage accounts in social networks, by providing the means for a user to schedule posts to Twitter, Facebook and Linkedin.
• Buffer is also the name of the company that creates this software.

Advantage of Buffer

• With one easy click, you’ll be able to share content and schedule posts via Twitter, Facebook, LinkedIn, Google+ and Pinterest.
• Buffer also allows you to share and schedule on Pinterest. However, it is through another app called Tailwind, which is a paid application ($9.99 per month). Buffer has integrated pinning into its platform on their paid plans.
• Buffer has Pablo, a free image creation tool that can help you create social media images for Facebook, Twitter, Pinterest and Google+ very quickly.
• Lets you select your default shortener as the well-known bit.ly, and also offers buff.ly and j.mp.
• The buffer extension for Chrome is also a helpful addition. The extension allows you share links, pictures and videos from wherever you are on the web. The extension also allows you to choose the single composer option or power scheduler where you can post the same thing multiple times over a specific period of time.
• Buffer analytics is useful, showing your best and worst performing posts based on engagement (which you can filter by engagement type, i.e. Retweets, favourites, replies, likes, comments, clicks), reach, and post type (image posts, link posts, text posts and your Retweets). All of this is exportable, too, if you need to do any further analysis.
• It’ll help you find the best times to post and automatically time your posts to get maximum engagement.
• Clean and simple layout.
• You can integrate blog feeds to give you sources of content to post out.
• Paid plans cost from only USD$10/month

Disadvantages of Buffer

• No Instagram integration into the platform
• No monitoring tools for mentions, searches and hashtags, so you’ll have to monitor these from another tool or through the networks themselves.