Doc Summary 
Swedish Business Central view name: Web Connect Integrationer
Purpose #
The Web Connect Integration defines how an external system communicates with Business Central.
Each Integration Card contains the base settings, such as:
- URLs
- Authentication
- data format
- Processing rules
This setup is the backbone of the integration and without it Web Objects and mappings and other functions cannot function. It also links to the Web Objects, which define the specific entities to be synchronized (e.g., items, customers, prices, orders).
How It Works #
A Web Connect Integration determines:
- Where Business Central sends or retrieves data
Upload/Download URLs, HTTP methods - How the data is formatted
JSON, XML, envelope structure, array paths, identifiers - How authentication is handled
API key, token, certificate
General Fields #
Integration Source & Description #
Identifies and describes the purpose of the integration.
Useful when multiple integrations exist for different systems (e-commerce, WMS, returns, ERP bridge).
Enabled #
Toggles the entire integration on/off.
If disabled → all scheduling and manual sync stops.
Source Type #
Defines the type of integration.
Usually: Default (HTTP Server) for modern REST integrations.
Web Object Prefix #
Optional prefix for object codes created by the integration.
Integration Comment #
For internal notes.
HTTP Server #
These settings define how Business Central communicates with the external system.
Web URL Download #
The endpoint from which BC retrieves data (GET requests).
Web URL Upload #
The endpoint to which BC sends data (POST/PUT/DELETE).
Accept HTTP Content Type #
Specifies the data format BC expects to receive (commonly application/json).
HTTP Content Type #
Defines the content type BC uses when sending data.
HTTP Methods
Create → POST
Update → PUT
Download → GET
Delete → DELETE
Client Certificate / Password #
Only used when the external system requires certificate-based authentication.
Authentication #
Only relevant if the integration uses token-based or keyed authentication.
Authentication Code #
Reference to an authentication configuration stored in Business Central.
Authentication Token Download / Upload #
Used for systems requiring OAuth/token refresh. Your credentials is stored in a way that only Web Connect can access it and no other.
Authenticate Codeunit #
Defines custom authentication logic (if needed).
Content Processing #
This section controls how the incoming data is interpreted before Web Objects handle it.
Data Type #
Here we configure which datatype the integrated system uses, such as Json, XML or GrapQL.
Acknowledge Link JPath #
If the external system requires a callback/acknowledgement URL, this extracts it from the payload.
Data Array JPath #
Specifies where the actual entity list exists inside the data type structure.
Envelope Object #
If data is wrapped in an outer envelope, define it here.
Create Envelope Codeunit #
Allows custom logic for building outbound envelopes.
Source Identifier JPath #
Defines the path of the external unique ID.
Used to prevent duplication and support upserts.
Shared External ID #
Used when multiple objects share external identifiers (rare).
Web Objects (Overview Only) #
The Integration Card automatically lists all Web Objects linked to this integration.
This article does not explain Web Objects in detail, that is handled in Web Connect Objects