Skip to main content

Basics

Before you start with the technical integration of brokerize tools, it is important to understand the fundamental concepts and infrastructure behind brokerize. brokerize acts as an intelligent middleware that abstracts and unifies the complexity of different broker interfaces.

Here you will find the most important building blocks that are relevant for every integration – whether via the API, the JavaScript client, or the Elements.

🔑 Authentication & Identity​

Every interaction with brokerize requires clear identification of your application and (in most cases) the end user.

  • Client ID: This is the unique identifier for your application. Without a valid Client ID, no API requests can be made.
  • Create Client ID: Learn how to generate your own identifier for development.
  • Sessions: Learn what happens in the background with sessions in brokerize.

🌐 Environments​

We provide two full-fledged API environments:

  1. Preview (Test Environment): Our environment for development and testing. Here you use the demo broker to safely test your integration.
    • API endpoint: https://api-preview.brokerize.com
  2. Production (Live): The production environment for live operation with real brokers.
    • API endpoint: https://api.brokerize.com

🧪 Test Infrastructure​

To test UI flows and order processes without having to open a real custody account, we use the Demo Broker.

  • Demo Broker: A simulated broker module that provides realistic feedback for orders, portfolio updates, and challenges (e.g., 2FA).

🔒 Security & CORS​

Since brokerize components are often executed directly in the browser, security mechanisms play a major role:

  • Allowed Origins: Your Client ID is tied to certain domains (origins). Requests from unregistered domains will be rejected.
  • Redirect URLs: For brokers with OAuth login, valid return URLs must be stored so that the user returns safely to your app after logging in.

⚙️ Additional Resources​

For a deeper technical integration, there are other important aspects:

In the next chapters you will learn more about the specific integration paths: Elements, JavaScript Client or directly via the API.