Add documentation on what callback actually is. For most people it's clear to be a function but even then it would be good to document what to expect exactly.
[Original issue]
Hello there,
would it be possible to add the response to all function calls ?
Otherwise I am unable to determine if for example an SMS message was sent.
The testing instructions should show it in action, not responding to a curl request.
At the moment our READMEs are useful for developers testing that the blocks work, not people trying to integrate the functionality. We should make them more useful
When creating an application on Nexmo, the endpoints for Event URL and Answer URL should be documented
The event URL is /api/event_ivr
the answer URL is /api/answer_inbound
event_ivr and answer_inbound are hardcoded into the demo application.
Also, the base route /api is hardcoded as well
Currently, we have most of the copy and links for authentication in our custom renderer. Bring these into the specs so that they can be used in other contexts
Whichever solution we choose for running the quickstarts, whether via the browser or the command-line, we should have a better UI for running the code. The supporting code for this should be clearly separated from the quickstart code itself, but also easily understood.
[Edit by @cbetta]
Add documentation on what
callbackactually is. For most people it's clear to be a function but even then it would be good to document what to expect exactly.[Original issue]
Hello there,
would it be possible to add the response to all function calls ?
Otherwise I am unable to determine if for example an SMS message was sent.
Cheers.