Table of Contents

Boltrics Postman Collections

Postman can be used to explore and test Boltrics APIs without building a custom integration first. It allows you to authenticate, send requests, inspect responses, and validate whether your setup and permissions are correct.

Boltrics provides two dedicated Postman collections:

  • Boltrics API
  • DI Post
Important

Before using these Postman Collections, you must authenticate using one of two methods:

  1. User Auth (OAuth2 Authorization Code): Best for interactive testing where you log in as a specific user.
  2. Application Auth (OAuth2 Client Credentials): Used for server-to-server integrations without user interaction.

See the Authorization through OAuth 2.0 Learn page for more information.

Boltrics API

Link: Boltrics API Postman Collection

Note

Access to these APIs requires purchasing the Analytics API module.

Description

This collection provides executable examples of the Boltrics APIs to help you understand, test, and validate available endpoints before implementing them in your own application or BI tool.

Included in This Collection

  • API reference requests, including:
    • Standard read operations for available resources
    • Required headers, parameters, and request bodies
    • Example responses illustrating expected API behavior
  • Workflow examples showing how multiple API calls can be combined to support common integration scenarios.

Required Setup Variables

To successfully retrieve data from the Analytics API, configure the following variables in your Postman environment:

  • {{clientId}} & {{tenantId}}: Your Azure app registration details.
  • {{bcEnvironment}}: The name of your BC environment (e.g., PROD-XXX or RAPP-XXX).
  • {{baseUrl}}: https://api.businesscentral.dynamics.com/v2.0/{{bcEnvironment}}
  • {{clientSecret}}: Only for Application Auth

DI Post

Link: DI Post Postman Collection

Important

Successful testing with this collection requires the purchase of the Connector module and prior configuration in your Boltrics environment.

For more information, see the Integration with the Standard eLearning and Learn page.

Description

The DI Post Postman collection is a short set of examples designed to post inbound XML messages into their Boltrics environment via the DIPost codeunit. The primary action used is PostXml, which submits the payload and returns a response containing status and tracking information.

Available Posting Methods

Integration partners can choose the method that best fits their technical stack:

  • SOAP Escaped/CDATA: Posts XML via the Business Central SOAP endpoint. Using CDATA is often preferred as it keeps the payload readable and handles special characters without manual escaping.
  • OData V4 (JSON): An unbound action that accepts a JSON object containing the XML string. This is recommended for modern integrations that prefer REST-like calls.

Required Setup Variables

To successfully route a message, you must configure the following variables in your Postman environment:

  • {{bcEnvironment}}: The name of your BC environment (e.g., PROD-XXX or RAPP-XXX).
  • {{bcCompanyName}}: The exact company name as it appears in the BC URL.
    BC Company Name
  • {{clientId}} & {{tenantId}}: Your Azure app registration details.

Guidance for a Successful XML Submission

To ensure the system recognizes your request, follow this workflow:

  1. Match the Namespace: Ensure the XML Namespace in your payload matches the one configured on the DI Message Type Card (e.g., www.boltrics.nl/receivereceipt:v100).
  2. If using SOAP: Make sure to set the SOAPAction Header to urn:microsoft-dynamics-schemas/codeunit/DIPost:PostXml
Edit this page