Last update on 12 July, 2022

Help and Support

We are here to help you, feel free to contact us on

Disclaimer: We strive to respond to all your queries at the earliest but give us 48 hours to come back to you. If the issue would require deeper investigation, we may need more time, but we will keep you informed via email.

When emailing us, please provide as much detail as possible for effective support. Here is a guide of the different types of queries and what information you can provide when emailing us.

  • Get in touch if you are interested in partnering with NewDay: Interested in using NewDay's solution? We're at hand to help you with your questions on NewDay's Technology products. Please get in touch if you'd like further information on options around customisation, pricing etc. When contacting NewDay, please include information of the sector and size you represent. Other points to include — the problem you are trying to solve and the NewDay Product you are interested in. We are here to help you, feel free to contact us on

  • Troubleshooting on existing integrations: The API documentation is normally a good place to start. Similarly pages within this site such as API Reference, Getting started, and the FAQ pages should help you. If you're unable to find what you are looking for, then please get in touch on Explain what you've tried, what you want to achieve, or what you need us to do. If you've tried something and didn't achieve the results you expected, explain what happened. Consider sharing identifiers, copies of your HTTP requests, and responses in form of screenshots, screen recordings, and code snippets.

  • Report an Incident: If you are encountering issues that impact your users, please raise it with us on To help us understand the incident and its severity, provide us details on the impact of the incident — how many of your users are affected and in what way? When did the incident occur, number of complaints (if any) etc.?

  • How to report Bugs: Something doesn't make sense or work as expected? Provide us with how you encountered the issue, what you've done, what happened, and what you expected to happen. Also consider adding details of when the issue occurred when you reach out on

  • Recommendations on New features and best practices: We are always working on improving existing features and introducing new features/APIs onto the portal. We would love to hear from you what features/APIs would you want us to consider and why. Tell us about it on

Tip: Found something in our docs that isn't making sense or can be improved? Tell us by either providing feedback at the bottom of the page where you found the issue or email us with the relevant URL and description of the issue.

Was this page helpful?