Request failed with status code 502


Receive and Send REST APIs and build your own integrations - long

  • Episodes4
  • Duration8m 50s
  • LanguagesEN
Episode 1

Introduction to REST APIs

Learn how APIs can help your automation fever


eramba can receive and send APIs in most modules, this means you can write your own code to automate actions in between eramba and other systems. Remember you can think of APIs as a both way route:

  • Receive APIs in eramba to add, list, edit, remove, Etc
  • Send APIs from eramba to any system based on your own defined triggers

For example: When your SIEM matches a trigger rule it can REST API to eramba and create an incident on the Incident Module. All our API documentation can be found on each module (you need to be logged as Admin or member of the Admin group to see the documentation) using Swagger.

For Example: when someone writes a comment or attachment on a Risk Review, you can send an email to all involved or you can send a REST API call that will send a Slack or Teams message instead. This is one out of million different possibilities.

Is important to remark eramba can send APIs to system (not just receive them) based on your own defined conditions with the use of Statuses (see the Status course). Statuses are everywhere in eramba and they trigger based on your conditions, for example: If a control failed more than %40 of the audits this year apply a status called "Horrible Control" (there are endless examples).

This is done trough Warning and Comments & Attachments notifications which can send either email or REST notifications. Please review the Notification course for details.