- 4 minutes to read

Endpoint Types

Unlock advanced filtering and actionable insights in your integration landscape with Nodinite Endpoint Types. This feature enables you to precisely register, categorize, and search endpoints from your Log Events, empowering both business and technical users to gain full control and visibility.

✅ Register and categorize endpoints for every Log Event
✅ Enable powerful, self-service filtering in Log Views
✅ Automate endpoint type assignment with Logging Agents
✅ Support compliance, troubleshooting, and business process optimization

Looking for messages sent by FTP or received by an Azure Service Bus Queue? Endpoint Type provides essential context for Nodinite Endpoints and enables richer filtering in Log Views.

EndPointTypeId is a mandatory numeric field in every Nodinite Log Event. It qualifies the type of Endpoint involved, making it easy to search, group, and analyze events across your integration solutions. Use this information to create tailored, self-service Log Views for your business and technical teams.

From the Repository Model, you can manage Endpoints and filter on Endpoint Type for targeted analysis.

Nodinite Logging Agents automatically set the correct EndPointTypeId for you. If you perform custom logging, use the reference table below to select the appropriate EndPointTypeId for your Log Event. This value is used to create and categorize Endpoints within Nodinite, providing better information and filter options for your organization.

Important
The EndPointTypeId property is mandatory. You must ALWAYS provide a value in the Log Event.

EndPointTypeId	Endpoint Type Name	Note
0	Unknown	(Please avoid this)
1	BizTalk - Receive
2	BizTalk - Send
3	BizTalk - Dynamic Send
4	BizTalk - Logical Receive
5	BizTalk - Logical Send

9	Log4Net

10	MSMQ
11	ActiveMQ
12	RabbitMQ
13	AMQP
14	AnypointMQ

20	AppFabric

25	Mule
26	CloudHub

30	AppFabric(Azure)

40	IBM MQ	Also known as IBM MQ / WebSphere MQ
41	IBM Integration Bus
42	IBM Data Queue
43	IBM API Connect	^{New 5.0.0.72}
44	IBM DataPower Gateway	^{New 5.0.0.72}
45	IBM Event Streams	^{New 5.0.0.72}
46	IBM IoT Platform	^{New 5.0.0.72}
47	IBM Cloud Functions	^{New 5.2.0.18}
48	IBM DB2	^{New 6.0.0.48}
49	IBM Sterling	^{New 6.1.0.61}

50	WCF

60	File
61	Dropbox

65	SMTP

70	Microsoft Azure Service Bus
71	Microsoft Azure API Management
72	Microsoft Azure API Apps
73	Microsoft Azure Logic Apps
74	Microsoft Azure Log Audits
75	Microsoft Azure Functions	^{New 5.2.0.18}

80	FTP
81	FTPS
82	SFTP
83	Connect:Direct

85	HTTP
86	HTTPS
87	REST API
88	Web API

90	ODBC
91	JDBC
92	SQL
93	Database
94	SSIS
95	Amazon DynamoDB
96	Amazon S3
97	PostgreSQL	^{New 5.0.0.72}

130	MLLP (Minimum Lower Layer Protocol)
140	Apache Kafka	^{New 5.0.0.72}
200	JMS	^{New 6.0.0.48}
230	MicrosoftAzureBlobStorage	^{New 6.0.0.48}
231	MicrosoftAzureFileSharesStorage	^{New 6.0.0.48}
232	MicrosoftAzureQueuesStorage	^{New 6.0.0.48}
233	MicrosoftAzureTablesStorage	^{New 6.0.0.48}
235	MicrosoftAzureEventGrid	^{New 6.0.0.48}
236	MicrosoftAzureEventHub	^{New 6.0.0.48}
240	MicrosoftAzureDatalake	^{New 6.0.0.48}
241	MicrosoftAzureDataFactory	^{New 6.0.0.48}
250	AmazonLambda	^{New 6.0.0.48}
251	AmazonKinesis	^{New 6.0.0.48}
260	MariaDB	^{New 6.0.0.48}
261	CosmosDB	^{New 6.0.0.48}
262	MySQL	^{New 6.0.0.48}
300	ORACLEDB	^{New 6.0.0.48}

Try it out yourself

To see the full list of values for your version, call the GET /LogAPI/api/LogEvent/EndPointTypes operation of the Log API. Open Scalar or Swagger at the root of the Log API web site in your Environment:

https://nodinite.contoso.com:40002/scalar
https://nodinite.contoso.com:40002/swagger

Note
Replace https://nodinite.contoso.com:40002 with the host and port of the Log API in your environment. The port is set for each environment in the Nodinite Portal, in the Servers step.

You can also call the operation directly from a script: GET https://nodinite.contoso.com:40002/LogAPI/api/LogEvent/EndPointTypes.