Custom integration

With custom integration, we receive data in our API (Application
Programming Interface). We generate a CURL that will send us the
“alarmed” (opens an incident on the platform) or “resolved” (closes the
incident on the platform) data. This way, our platform can process this
data and contact your team if your application has an error. To
configure a custom integration, request CURL from our team.

Observation:

All of the following steps must be done after External Integration
has already been configured by the ElvenWorks team. Request integration
via chat on the platform or on the website.

Below is an example of a CURL for custom integration:

curl --request POST \

  --url '<URL da API Elven>' \

  --header 'Content-Type: application/json' \

  --header 'User-Agent: 1PcustomAuth/1.0' \

  --data '{

  "title": "<incident title>",

  "description": "<incident description>",

  "external_aggregate_key": "001",

  "action": "alarmed",

  "organization": "<org_uid provided by Elven>",

  "severity": "critical"

}'
  • “–url” = API_URL generated when creating the External Integration provided by Elven;
  • “title” = In this field you define a title that will appear in the incident opened in 1P;
  • “description” = In this field you define a description for the incident, it will appear in “cause” in the incident opened in 1P;
  • “external_aggregate_key” = In this field you define an identifier to
    “open” and “close” the incident, that is, when closing the incident, it
    must have the same external_aggregate_key as the open incident;
  • “action” = In this field you define the action to be executed, which
    can be “alarmed” (opens the incident) or “resolved” (closes the
    incident);
  • “organization” = This field is provided by the Elven team at the time of the request;
  • “severity” = In this field you define the severity associated with
    the incident, which can be informational, low, moderate, high or
    critical.

Note: don’t forget to add the headers:

–header ‘Content-Type: application/json’ \

–header ‘User-Agent: 1PcustomAuth/1.0’ \

By posting this CURL you will open/close incidents on the platform, thus being able to manage them and be notified.

With custom integration, we receive data in our API (Application
Programming Interface). We generate a CURL that will send us the
“alarmed” (opens an incident on the platform) or “resolved” (closes the
incident on the platform) data. This way, our platform can process this
data and contact your team if your application has an error. To
configure a custom integration, request CURL from our team.

Observation:

All of the following steps must be done after External Integration
has already been configured by the ElvenWorks team. Request integration
via chat on the platform or on the website.

Below is an example of a CURL for custom integration:

curl --request POST \

  --url '<URL da API Elven>' \

  --header 'Content-Type: application/json' \

  --header 'User-Agent: 1PcustomAuth/1.0' \

  --data '{

  "title": "<incident title>",

  "description": "<incident description>",

  "external_aggregate_key": "001",

  "action": "alarmed",

  "organization": "<org_uid provided by Elven>",

  "severity": "critical"

}'
  • “–url” = API_URL generated when creating the External Integration provided by Elven;
  • “title” = In this field you define a title that will appear in the incident opened in 1P;
  • “description” = In this field you define a description for the incident, it will appear in “cause” in the incident opened in 1P;
  • “external_aggregate_key” = In this field you define an identifier to
    “open” and “close” the incident, that is, when closing the incident, it
    must have the same external_aggregate_key as the open incident;
  • “action” = In this field you define the action to be executed, which
    can be “alarmed” (opens the incident) or “resolved” (closes the
    incident);
  • “organization” = This field is provided by the Elven team at the time of the request;
  • “severity” = In this field you define the severity associated with
    the incident, which can be informational, low, moderate, high or
    critical.

Note: don’t forget to add the headers:

–header ‘Content-Type: application/json’ \

–header ‘User-Agent: 1PcustomAuth/1.0’ \

By posting this CURL you will open/close incidents on the platform, thus being able to manage them and be notified.