v2.44.0 - Three MD Provider Support - Catena Telematics API

Three MD added to source_name enum

The three_md value has been added to the source_name / TspEnum enumeration. This new value is now accepted and returned across all Integrations API endpoints that reference a telematics service provider.Affected endpoints:

Method	Endpoint
`GET`	`/v2/integrations/connections`
`POST`	`/v2/integrations/connections`
`GET`	`/v2/integrations/connections/{connection_id}`
`PATCH`	`/v2/integrations/connections/{connection_id}`
`GET`	`/v2/integrations/connections/{connection_id}/schedules/{schedule_id}/executions`
`GET`	`/v2/integrations/connections/{connection_id}/resource-operations/{resource_operation_id}`
`GET`	`/v2/integrations/connections/resource-operations`
`GET`	`/v2/integrations/tsps`
`GET`	`/v2/integrations/tsps/{tsp_id}`

Filtering by Three MD:

# List connections for Three MD
GET /v2/integrations/connections?source_name=three_md

# List resource operations for Three MD
GET /v2/integrations/connections/resource-operations?source_name=three_md

Example response:

{
  "items": [
    {
      "id": "conn_abc123",
      "source_name": "three_md",
      "status": "active"
    }
  ]
}

Integrations API

View complete endpoint documentation for the Integrations API

Contact Support

Questions about this release? Our team is here to help

Overview

Authentication

Telematics

Organizations

Integrations

Notifications

Intelligence

v2.44.0 - Three MD Provider Support

Three MD Provider Support

New Provider Support

Need Help?

Integrations API

Contact Support

​Three MD Provider Support

​New Provider Support

​Need Help?

Integrations API

Contact Support

Three MD Provider Support

New Provider Support

Need Help?