Document toolboxDocument toolbox

HTTP endpoint

Owned by Juan Tomás Alonso Nieto (Deactivated)
May 08, 2023
5 min read
[ 1 Create the token needed to authorize the endpoint ] [ 2 Configure the HTTP endpoint ] [ 3 Code samples ]

You can send single events or stream data to your Devo domain over HTTP. Generate a token for your HTTP endpoint in the Devo web application, then use that token to set up event sending from your HTTP endpoint.

Maximum file size

Note that there’s a limit of 32 MB when you use this sending method.

Create the token needed to authorize the endpoint

The OAuth token is a 32-character alphanumeric string that authorizes a connection to Devo. When this token is used when making HTTP requests to Devo, it is recognized by the platform and the connection is authorized and the request is carried out. To create the required token:

Configure the HTTP endpoint

Once the token has been generated, you can configure the endpoint. The URL to send the HTTP request follows this format:

<endpoint>/<mode>/<domain>/token!<token>/<host>/<tag>?<message>

Where each element in the URL is described below:

Element

Description

Element

Description

<endpoint>

  • USA: https://http-us.devo.io:443

  • Europe: http[s]://http-eu.devo.io

  • Canada: https://http-ca.devo.io:443/

  • Asia-Pacific (APAC): https://collector-ap.devo.io:8443 (The endpoint will be different depending on the ingestion source. Currently we have collector-ap for Singapore and collector-ap2 for Sydney)

Use the endpoint that corresponds to the Devo Cloud region you use.

<mode>

This can be one of the following:

  • event - Use this mode to send single events. GET and POST methods are accepted.

  • stream - Use this mode to send multiple events. Only POST is accepted. Use the header Content-Encoding: gzip to send multiple compressed events in your request body. Check an example in the section below.

<domain>

The name of the Devo domain where the events are being sent to.

<token>

The token you generated in Devo to authorize your connection. 

<tag>

The Devo tag to be applied to the events. Learn more about tags in About Devo tags.

<message>

The log to be sent. Note that this is only valid if you’re using the event mode, that is to say, you're sending a single event to Devo. In this case, the event is added to the query string.

In case of a POST request in stream mode, events should be added to the request body. See some examples of this in the section below.

Here is an example of an endpoint URL:

https://http-us.devo.io/event/myDomain/token!a5370g9e8f7d7edf9d/local1/my.app.http.js?this%20is%20a%20example%20of%20log

Code samples

Here you can see a few examples of how token-based HTTP requests can be sent from an endpoint to a table (or tables) in a Devo domain. 

Python - Sending a single event

import requests from urllib.parse import quote devo_endpoint="http://devoEndpoint" domain="demoDomain" token="example_token_1234abcd" hostname="my_src_hostname" devo_table="my.app.demo.send" message = quote("test event") url = f'{devo_endpoint}/event/{domain}/token!{token}/{hostname}/{devo_table}?{message}' payload={} headers = {} requests.request("GET", url, headers=headers, data=payload)

Python - Sending a file with events

Java

Java (POST example)

HTML - jQuery

HTML - JavaScript

cURL - Sending a single event

cURL - Sending a file with events

cURL - Sending a file with compressed events

.cURL - Sending a file with events

Related articles