Feel free to conduct direct testing on this website. We strongly encourage and recommend utilizing this feature as an efficient means to promptly test functionalities and configurations on your end.

Welcome

While we advocate for leveraging the testing capability offered on this website, we recognize that you may also wish to create client SDKs tailored to your use case. We recommend utilizing Nomba’s OpenAPI Spec along with the well-known Swagger tool for generating client SDKs.

This method ensures a seamless and convenient validation process, providing you with the flexibility to refine and optimize your implementations with ease. Incorporating client SDKs into your workflow enhances the overall development experience and promotes efficiency in handling various aspects of API integration for your specific needs.

Quick Action

OpenAPI Spec

Nomba API Endpoints

View the OpenAPI specification file

Authentication

Nomba streamlines the authentication of API calls through the utilization of OAuth2 HTTP bearer tokens. The authentication process encompasses two distinct methods, namely the Client-credentials method and the PKCE (Proof key for code exchange) method. In each method, an access_token is generated, serving as the key to authenticate your API requests seamlessly.

To furnish your API requests with the requisite access_token, employ the "Authorization" HTTP header, as illustrated: Authorization: {access_token}. This robust and secure authentication mechanism ensures the integrity of your interactions with Nomba’s API.

For an in-depth comprehension of Nomba’s authentication flow, explore further insights and details available here. These resources offer a comprehensive guide to navigating the intricacies of our authentication processes, empowering you to harness the full potential of Nomba’s capabilities for your API calls.

Cross-Origin Resource Sharing

The API incorporates Cross-Origin Resource Sharing (CORS) in accordance with the W3C specifications. CORS support is essential, facilitating calls from the request maker embedded within the API documentation. This adherence to CORS standards enhances the versatility of the API, ensuring seamless and secure communication with the API docs request maker, thereby contributing to an optimal developer experience.