Nexeed
    • Introduction
    • Getting started
      • Getting access
      • Login
      • Main screen
      • Welcome dashboard
      • Detecting process anomalies
      • Analyzing data and detecting event sequences
      • Analyzing KPIs
    • How-tos
      • Monitors on production lines
        • Configuring the automatic login in the Nexeed Industrial Application System
        • Configuring the automatic login to the identity provider with the Windows user
        • Setting cookies in the browser
        • Configuring the automatic logout in the Nexeed Industrial Application System
        • Configuring the command line parameters in the browser
        • Known limitations and troubleshooting
      • Try out the APIs
    • Integration guide
      • Underlying concepts
        • Underlying concepts
        • Onboarding
        • Security
        • Communication
      • Integration journey
      • Overview of APIs
    • Operations manual
      • Release
      • System architecture and interfaces
      • System requirements
        • Cluster requirements
        • Database requirements
        • Support for service meshes
      • Migration from previous Nexeed IAS versions
      • Setup and configuration
        • Deployment process
        • Deployment with Helm
        • Advanced configuration
        • Integrations with external secret management solutions
        • Context paths
        • Service accounts and authorizations
        • Validation tests
        • Setup click once
        • Database user setup and configuration
      • Start and shutdown
      • Regular operations
        • User management & authentication
        • How to add additional tenants
        • How to access the cluster and pods
        • Automatic module role assignments in customer tenants
        • User credentials rotation - database and messaging secrets
      • Failure handling
        • Failure handling guidelines
        • Ansible operator troubleshooting
        • How to reach BCI for unresolved issues
      • Backup and restore
      • Logging and monitoring
        • The concept and conventions
        • ELK stack
        • ELK configurations aspects for beats
        • Proxy setup for ELK
        • Health endpoints configurations
      • Known limitations
      • Supporting functions
      • Security recommendations
        • Kubernetes
        • Security Best Practices for Databases
        • Certificates
        • Threat detection tools
    • Infrastructure manual
      • Release
      • System architecture and interfaces
        • RabbitMQ version support
      • System requirements
      • Migration from previous Nexeed infrastructure versions
      • Setup and configuration
        • Deployment process of the Nexeed infrastructure Helm chart
        • Deployment with Helm
      • Start and shutdown
      • Regular operations
        • RabbitMQ
          • User management & authentication
          • Disk size change
          • Upgrade performance with high performant disk type
          • Pod management policy
      • Failure handling
        • Connection failures
        • Data safety on the RabbitMQ side
        • Fix RabbitMQ cluster partitions
        • Delete unsynchronized RabbitMQ queues
        • How to reach BCI for unresolved issues
      • Backup and restore
      • Logging and monitoring
      • Known limitations
    • Glossary
    • Further information and contact
Industrial Application System
  • Industrial Application System
  • Core Services
    • Block Management
    • Deviation Processor
    • ID Builder
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • Global Production Overview
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Product Setup Management
    • Part Traceability
    • Process Quality
    • Setup Specs
  • Execution
    • Line Control
    • Material Management
    • Order Management
    • Packaging Control
    • Rework Control
  • Intralogistics
    • AGV Control Center
    • Stock Management
    • Transport Management
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
    • Maintenance Management
    • Tool Management
  • Enterprise & Shopfloor Integration
    • Archiving Bridge
    • Data Publisher
    • Direct Data Link
    • Engineering UI
    • ERP Connectivity
    • Gateway
    • Information Router
    • Master Data Management
    • Orchestrator

Nexeed Learning Portal

  • Industrial Application System
  • How-tos
  • Try out the APIs
preview 2025.03.00

Try out the APIs

This page provides tutorials on how to use API request tools like Bruno or Postman to interact with the NEXEED APIs.

Bruno

You can download our Bruno collection which includes predefined API requests to explore our module APIs.

Environment

Bruno uses a folder-based project structure. When importing the collection, any associated environments will be imported automatically.

After importing, open the environment named Nexeed IAS Integration in Bruno and update the variable values to match your setup. To obtain your client_id and client_secret, refer to the "https://learn.bosch-nexeed.com/en/multitenant_access_control/getting_started/10_appregistration" section of the Multitenant Access Control documentation.

bruno env variables

Collection

Import the prepared Bruno collection to Bruno. Each module API is organized in a dedicated folder inside the Bruno project.

Make sure you’re using the appropriate environment for the module you’re testing.

Request access token

Most API calls use the "Client Credentials Flow" for authentication.

To request an access token from Multitenant Access Control, visit the authorization tab on the parent folder of a request you want to try.

In Bruno 2.x, you can configure authorization settings at both the collection and folder levels. For example, if you want to test any request under Multitenant Access Control, the access token can be set at either the collection or the relevant folder level, depending on your project structure. All requests will inherit the token and settings defined at their nearest parent level—either from the folder or, if not set there, from the collection.

Also, make sure the following environment variables are configured:

  • Access Token URL

  • Client ID

  • Client Secret

  • Scope

These variables will be used in the OAuth2 flow to obtain and manage the token.

bruno collection auth

Click Get Access Token, this will let the auth server check the validity of your credentials and will create a bearer token, which will be added as an authorization header for all subsequent requests. Keep in mind that the token has a 5 minutes expiry time and therefore needs a refresh every couple minutes.

Postman

You can download our Postman collection with the API calls to try out how the various module APIs work.

Environment

Import the prepared environment file Postman Environment into Postman to create the default environment for the upcoming requests. Add your specific values for the environment variables. To get client ID and client secret, check out the https://learn.bosch-nexeed.com/en/multitenant_access_control/getting_started/10_appregistration section of the Multitenant Access Control documentation.

env variables

Collection

Import the prepared Postman collection to Postman.

Make sure your collection uses the environment "Nexeed IAS Integration" and that it is configured.

Request access token

Most of the requests will use the "Client Credential Grant Type Flow".

To request an access token from Multitenant Access Control, visit the authorization tab on the parent folder of a request you want to try.

For example, if you want to try any request from Multitenant Access Control, the token can be obtained from the authorization tab on the parent folder named Multitenant Access Control. All the requests in this folder will inherit the access token.

Verify that the variables for Access Token URL, Client ID, Client Secret and Scope are configured in the environment variables.

authorization

Click on Get New Access Token and then on use token.

authorization 2

This will let the auth server check the validity of your credentials and will create a bearer token, which will be added as an authorization header for all following requests. Keep in mind that the token has a 5-minute expiry time and therefore needs a refresh every couple minutes.

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2025, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses