Skip to main content

Orbitas B2B API Documentation

Welcome to the Orbitas B2B API documentation, designed to facilitate seamless communication between Enterprise Resource Planning (ERP) systems or applications and the data stored in our databases. Our API enables users to securely access and manage their respective databases in a controlled and efficient manner.

About the API

The Orbitas B2B API has been carefully designed to bridge the gap between ERP systems or applications and our robust database infrastructure. Each client registered on our platform will have a unique and exclusive database for their operations, as indicated by the {dbName} parameter in our Swagger documentation. This ensures that every interaction with data is secure and tailored to the specific business operations of the client.

Key Features​

  • Data Integration: Seamlessly integrate your ERP or application with our database using standardized endpoints for efficient data communication.
  • User-Specific Database Access: Users are provided controlled access to their respective databases, ensuring data privacy and security.
  • Scalable and Secure: Designed with scalability and security in mind, our API supports businesses of all sizes, facilitating reliable data management and transactions.

Getting Started​

To effectively begin using the Orbitas B2B API, please refer to our detailed documentation below. Whether you're looking to register users, authenticate access, manage profiles, or perform data operations, our documentation provides comprehensive guides and examples to streamline your integration process.

Explore the API endpoints and functionalities to leverage the full potential of Orbitas B2B in enhancing your business operations.

API Access After Registration​

Once the client has completed registration on our platform and selected the necessary modules, access to the Orbitas B2B API will be facilitated as follows:

  • Automatically Generated Credentials: A username and password will be automatically generated for the client. These credentials will be used to authenticate all API requests.
  • Assigned Database ñName: Additionally, a unique database name will be automatically assigned to the client. This database name must be specified in each API request by replacing {dbName} as shown in our Swagger documentation.

This process ensures that each interaction with the API is properly authenticated and configured to securely and efficiently access and manage the client's specific data.