Yep, saw that and other informational pages on Mock Services. The concept seems OK. I create a mock service (I guess give it a name). Then I create mock actions (which I guess are the ?methods? / functionality exposed by the API. Each mock action (I guess) has one or more responses; made up of success responses, warning, or error responses. For example, a success response can be 'here's the data you requested' or you made a valid request - there's just no data to return to you', or errors like XYZ is a required input parameter, or the format for DATE is incorrect, or username/password incorrect, etc. etc.
I was able to name a mock service but couldn't get one step past that. I couldn't name/create a mock action (it was asking for a "resource path". I don't understand Resource Path or Dispatch. I guess Resource Path is a folder, but what do you put in the folder? Dispatch concept is foreign, I just don't understand it. I don't know any scripting languages... Clearly I don't have sufficient background to create & document a mock service ergo that's why I asked, where do I start?
The API under development is REST based. It has 5 required inputs and 2 optional inputs. There's only one mock action, the data request. The user makes a request for data and the API responds. There isn't a 'conversation'. If successful data a 'table' of data (several of rows of data) is returned (the response) to the user. I know the fields/format of the data that's returned.
Thanks, DaveK