API

From Enterprise Help
Revision as of 09:18, 11 May 2015 by Sghosh (Talk | contribs)

Jump to: navigation, search

Intro—should include an overview of the QS and the API and why a client would need one vs. the other)


  • OAuth DRAFT--incomplete, needs work
  • Entities needs review--does this match what is in production?
  • Actions needs review
  • API Use Cases (w/sample docs)
  • Getting Site Information Needs review--written for partner audience, not for client audience, has references to enterprise.qa.fishbowl.com
  • Getting and Creating List Needs review--written for partner audience, not for client audience, has references to enterprise.qa.fishbowl.com
  • Getting Locations Needs review--written for partner audience, not for client audience, has references to enterprise.qa.fishbowl.com
  • Adding or Updating Members Needs review--written for partner audience, not for client audience, has references to enterprise.qa.fishbowl.com
  • Getting Member Profile Fields Needs review--written for partner audience, not for client audience, has references to enterprise.qa.fishbowl.com


Use cases not yet documented:

  • What are the existing InputSource field values
  • How to unsubscribe a member
  • What profile fields should be displayed to members on an eclub join form on my website
  • How to send a single message to a member (exiting mailing)
  • How do I know what storecode to use when adding or updating a member record
  • How do I see a list of all Stores for a site?
  • Which ones are open/closed, etc
  • How do I know which stores to show on an eclub join form on my website? And what should I show on my website?
  • Show display values, add StoreCode to member records