Frequently used terms in the Transposit Developer Platform are as follows.
Application. An application is the representation of a particular project; a container for functionality you want to build. Applications contain the following functionality.
- data parsers
- data connections
- keys to access data connections
- configurations for authentication and deployment
Note: Currently Transposit does not support multiple users modifying an application in the console at the same time.
Data Connection. Transposit creates a unified interface for interacting with APIs. A data connection represents either external applications or other Transposit applications. OpenAPI or WSDL specifications are used to map external APIs to the Transposit ecosystem.
Applications built within Transposit can be connected to each other without additional bindings.
A data connection encapsulates:
- Authentication (OAuth, username/password, basic header auth, etc)
- API schema and delivery mechanism
- Pagination (supported by some operations)
Operations inside a Transposit application can be private (e.g., used only for development, or called by other operations within the application), scheduled for periodic execution, or deployed as endpoints.
Authentication. Data connections used by your application may require access credentials, referred to as keys in Transposit to disambiguate from other related concepts. Keys may be supplied by you as the developer, or by your users, if your application so specifies.
Separately, there is the "front door" to your application, which can have its own authentication requirements, entirely unrelated to data connection keys—your application may require users to register and log in, for example.
Transposit provides powerful tools to centrally manage these types of authentication and user management issues, making apps easier to build and faster to deploy.