Create new event

POST

/events

curl --request POST \
  --url https://legion.picogrid.com/v2/events \
  --header 'Content-Type: application/json' \
  --data '{ "fragment_id": "example", "event_type_id": "example", "confidence": 1, "location": { "type": "lat_lng_alt", "altitude": 1, "latitude": 1, "longitude": 1 }, "meta_data": { "additionalProperty": "example" } }'

• The server that hosts the Legion prod API

Create a new event by specifying the properties of the new object in the request body

Request Body^required

Specify the fields of the event here

Media typeapplication/json

object

fragment_id

required

The id of the fragment this event occurred on

string

event_type_id

required

The id of the event type this event is classified as. If using one of Picogrid’s global event types you can cache/hardcode the event type id as we guarantee that we won’t change it

string

confidence

required

The confidence that the event is correctly classified as a floating point percentage from 0-100

number

<= 100

location

required

One of:

Latitude, Longitude, Altitude

Latitude, Longitude, Altitude

Provide the latitude and longitude of the resource using WGS84, and the altitude of the resource in meters above sea level

object

type

required

string

Allowed values: lat_lng_alt

altitude

required

The altitude of the resource in meters above sea level

number

latitude

required

number

>= -90 <= 90

longitude

required

number

>= -180 <= 180

meta_data

required

If writing to a custom event type you have created yourself you can add any additional metadata you want to include with the event here. If you are writing to one of Picogrid’s globally available event types you must read meta_data documentation to see what metadata is required for that event type. If you do not include the required metadata the event will be rejected.

object

key

additional properties

Responses

200

Success

Media typeapplication/json

One of:

Event On A Blob Fragment

Event On A Blob Fragment

object

id

required

string

primitive_fragment_type

required

This key can be used as a discriminator for which type of event you have received. In this case the value is ‘blob’. The fragment this event occurred on is stored in our blob storage, which we use for large files and unstructured data, so we provide the fragment to you via the presigned url found in this object.

string

Allowed values: blob

presigned_url

required

An http url you can send a GET request to in order to fetch the blob data of the fragment this event occurred on. If it is an image for example you can use this url directly in an <img> tag to display the image. The url is only valid for 24 hours, so will need to be refetched after that time if needed. The url should be treated as a secret token, and only shared with people you want to have access to the data.

string

confidence

required

The confidence of the processor that it classified the event correctly as a percentage from 0-100

number

<= 100

timestamp

required

The time which this event occurred at. The timestamp is an epoch milliseconds integer. See https://en.wikipedia.org/wiki/Unix_time for more information

integer

processed_timestamp

required

The time the event was created. The timestamp is an epoch milliseconds integer. See https://en.wikipedia.org/wiki/Unix_time for more information

integer

location

required

Location

Gives multiple different formats and units to choose between that all represent the location of the resource

object

lat_long_alt

required

Latitude, Longitude, Altitude

Provides the latitude and longitude of the resource using WGS84, and the altitude of the resource in meters above sea level

object

altitude

required

The altitude of the resource in meters above sea level

number

latitude

required

number

>= -90 <= 90

longitude

required

number

>= -180 <= 180

meta_data

required

Any additional metadata that the processor wanted to add to the event. See meta_data documentation for more information

object

key

additional properties

event_type_id

required

string

fragment_type_id

required

string

stream_id

required

string

terminal_id

required

string

Event On A JSON Fragment

Event On A JSON Fragment

object

id

required

string

primitive_fragment_type

required

This key can be used as a discriminator for which type of event you have received. In this case the value is ‘json’. The fragment this event occurred on is stored as a json object smaller than 200kb and is therefore provided directly in the json_data key in this object.

string

Allowed values: json

json_data

required

The json data which describes the fragment this event occurred on

object

key

additional properties

confidence

required

The confidence of the processor that it classified the event correctly as a percentage from 0-100

number

<= 100

timestamp

required

The time which this event occurred at. The timestamp is an epoch milliseconds integer. See https://en.wikipedia.org/wiki/Unix_time for more information

integer

processed_timestamp

required

The time the event was created. The timestamp is an epoch milliseconds integer. See https://en.wikipedia.org/wiki/Unix_time for more information

integer

location

required

Location

Gives multiple different formats and units to choose between that all represent the location of the resource

object

lat_long_alt

required

Latitude, Longitude, Altitude

Provides the latitude and longitude of the resource using WGS84, and the altitude of the resource in meters above sea level

object

altitude

required

The altitude of the resource in meters above sea level

number

latitude

required

number

>= -90 <= 90

longitude

required

number

>= -180 <= 180

meta_data

required

Any additional metadata that the processor wanted to add to the event. See meta_data documentation for more information

object

key

additional properties

event_type_id

required

string

fragment_type_id

required

string

stream_id

required

string

terminal_id

required

string

Example

{
  "primitive_fragment_type": "blob"
}

Headers

Access-Control-Allow-Origin

string

default: *

Example

https://developer.mozilla.org

The Access-Control-Allow-Origin response header indicates whether the response can be shared with requesting code from the given origin. - MDN Link

Access-Control-Allow-Credentials

boolean

default: true

The Access-Control-Allow-Credentials response header tells browsers whether to expose the response to the frontend JavaScript code when the request’s credentials mode (Request.credentials) is include. - MDN Link

400

Bad Request Error

Media typeapplication/json

object

message

required

string

Example^generated

{
  "message": "example"
}

Headers

Access-Control-Allow-Origin

string

default: *

Example

https://developer.mozilla.org

The Access-Control-Allow-Origin response header indicates whether the response can be shared with requesting code from the given origin. - MDN Link

Access-Control-Allow-Credentials

boolean

default: true

The Access-Control-Allow-Credentials response header tells browsers whether to expose the response to the frontend JavaScript code when the request’s credentials mode (Request.credentials) is include. - MDN Link

401

Authentication Error

Media typeapplication/json

object

message

required

string

Example^generated

{
  "message": "example"
}

Headers

Access-Control-Allow-Origin

string

default: *

Example

https://developer.mozilla.org

The Access-Control-Allow-Origin response header indicates whether the response can be shared with requesting code from the given origin. - MDN Link

Access-Control-Allow-Credentials

boolean

default: true

The Access-Control-Allow-Credentials response header tells browsers whether to expose the response to the frontend JavaScript code when the request’s credentials mode (Request.credentials) is include. - MDN Link

403

Unauthorized Error

Media typeapplication/json

object

message

required

string

Example^generated

{
  "message": "example"
}

Headers

Access-Control-Allow-Origin

string

default: *

Example

https://developer.mozilla.org

The Access-Control-Allow-Origin response header indicates whether the response can be shared with requesting code from the given origin. - MDN Link

Access-Control-Allow-Credentials

boolean

default: true

The Access-Control-Allow-Credentials response header tells browsers whether to expose the response to the frontend JavaScript code when the request’s credentials mode (Request.credentials) is include. - MDN Link

404

Resource Not Found Error

Media typeapplication/json

object

message

required

string

Example^generated

{
  "message": "example"
}

Headers

Access-Control-Allow-Origin

string

default: *

Example

https://developer.mozilla.org

The Access-Control-Allow-Origin response header indicates whether the response can be shared with requesting code from the given origin. - MDN Link

Access-Control-Allow-Credentials

boolean

default: true

The Access-Control-Allow-Credentials response header tells browsers whether to expose the response to the frontend JavaScript code when the request’s credentials mode (Request.credentials) is include. - MDN Link

408

Timeout Error

Media typeapplication/json

object

message

required

string

Example^generated

{
  "message": "example"
}

Headers

Access-Control-Allow-Origin

string

default: *

Example

https://developer.mozilla.org

The Access-Control-Allow-Origin response header indicates whether the response can be shared with requesting code from the given origin. - MDN Link

Access-Control-Allow-Credentials

boolean

default: true

The Access-Control-Allow-Credentials response header tells browsers whether to expose the response to the frontend JavaScript code when the request’s credentials mode (Request.credentials) is include. - MDN Link

500

Error

Media typeapplication/json

object

message

required

string

Example^generated

{
  "message": "example"
}

Headers

Access-Control-Allow-Origin

string

default: *

Example

https://developer.mozilla.org

The Access-Control-Allow-Origin response header indicates whether the response can be shared with requesting code from the given origin. - MDN Link

Access-Control-Allow-Credentials

boolean

default: true

The Access-Control-Allow-Credentials response header tells browsers whether to expose the response to the frontend JavaScript code when the request’s credentials mode (Request.credentials) is include. - MDN Link

502

Bad Gateway Error

Media typeapplication/json

object

message

required

string

Example^generated

{
  "message": "example"
}

Headers

Access-Control-Allow-Origin

string

default: *

Example

https://developer.mozilla.org

The Access-Control-Allow-Origin response header indicates whether the response can be shared with requesting code from the given origin. - MDN Link

Access-Control-Allow-Credentials

boolean

default: true

The Access-Control-Allow-Credentials response header tells browsers whether to expose the response to the frontend JavaScript code when the request’s credentials mode (Request.credentials) is include. - MDN Link