The GET Conversation settings allows you to verify your E-Mandate configuration and to see the next available steps in your current conversation
Before calling any of the conversation APIs, you must first make a request to Prepare Emandate and retrieve an E-Mandate token. This token must be provided in your HTTP Token header. |
In this conversation example, we are assuming that you want to create an e-mandate with authorisation method = SMS.
To begin:
- Confirm that you have been properly configured for this authentication method.
- Generate a GET request to
/conversations/settings - Confirm in the response that
authorizationisSMS_PASSWORD.
Note: It is not possible to set up your authentication configuration via the API; a member of the Nuapay Customer Support team will set up your business as requested. See Configurations for details on what configurations are possible.
Move to the next stage in the conversation: Initialization
Note:
When working with our APIs, please use the Sandbox URI when testing and the Live URI when you move to Production.
LIVE https://api.nuapay.com SANDBOX https://sandbox.nuapay.com/
If you haven't done so already and would like to do some testing, please Request Sandbox Access
Important: Endpoints and Webhooks may be extended from time to time and any changes we make will follow our Versioning and Backward Compatibility rules. This means that the code that you write today must be designed to be robust enough to handle any future changes (where a new object is added to (or removed from) a specific API response, for example).