Skip to content
Events Service

HTTP protocol

The HTTP protocol is used for one-to-one, uni-directional communication. By using the HTTP protocol subscribers poll for events at regular intervals.

Click here to view a demo{:target=“_blank”} of using Events with HTTP protocol. Long polling is not possible using the HTTP protocol, this feature is only available over a websocket connection. Note that subscribers are able to monitor their backlog of unconsumed notifications and adjust their polling interval to prevent them from falling too far behind in the notification queue. For more details, see Monitor Consumer Lag.

  • API CALL:

    GET {baseUrl}/{apiVersion}/consumers/namespaces/{namespaceName}/events/{eventName}/{eventVersion}

  • HEADER:

    • Accept: application/json
    • Authorization: Bearer {token}
    • TCP-Request-ID: Unique ID of the request. This parameter is optional. Include Trimble Identity OAuth Bearer token for your application.

  • Sample response:

    {
      "id": "1212",
      "specversion": "1.0",
      "source": "/tid/<apiid>",
      "type": "delete.v1",
      "time": "2020-12-10T07:23:44.599Z",
      "subject": "/tid/UserDelete",
      "data": {
        "uuid": "121212"
        }
    }

The consumption endpoint is unique to each consumer. Contact cloudplatform_support@trimble.com to confirm with you the endpoint after the onboarding process is complete.

For more details, refer to API Reference.