NASCO APIs are exposed over Mutual TLS. Consumers and NASCO should share their respective Digital Certificates to establish mutual authentication (a.k.a 2-Way TLS).
NASCO APIs are secured using the OAuth 2.0 Client Credentials. We also use two way TLS.
To provide feedback, select the Contact Us link, and fill out the form. Please select “Portal Feedback” from the Reason type field.
We hate to hear that. To report a potential defect, select the Contact Us link, and fill out the form. Please select “Other” from the Reason type field.
Select the Contact Us link and fill out the form. Please select “Other” from the Reason type field.
NASCO offers best in class capabilities for healthcare claim processing and membership management. In many cases, we offer APIs and events to allow you to integrate our digital capabilities into your applications and business processes. We believe the developer portal provides the most effective way for you and your peers to discover the most up to date information about our digital capabilities.
Visit us at our website, www.NASCO.com. Otherwise, feel free to reach out to us via the Contact Us link.
Yes. We will associate an API or Event to one or more Customer Journeys when they may be useful in addressing the business problems of those journeys. If the name of the API and the functions are the same, they are the same API.
We think our Developer Portal is pretty amazing. But not that amazing. No, there is no cost to discover our digital assets.
Yes. You should define an application for Test purposes and eventually for Production. By defining your App, we can provide specific security credentials you will need to call the API endpoint successfully in Test or Production.
© 2024 NASCO • ALL RIGHTS RESERVED