Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ARMO Integrations API

Jira and collaboration/notification integrations.

ARMO Integrations API is one of 8 APIs that ARMO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Integrations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against 2 base URLs: https://api.armosec.io/api/v1, https://api.us.armosec.io/api/v1.

5 operations 4 paths 2 schemas 1 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://api.armosec.io/api/v1
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

ARMO Integrations API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-KEY (apiKeyAuth). By default, every request must be authenticated.

  • apiKeyAuth — Account access key (Agent Access Key) generated in ARMO Platform under Settings, sent in the X-API-KEY header.

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 1 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Integrations 5

Jira and collaboration/notification integrations.

GET
/integrations/jira/config
Get Jira configuration
getJiraConfig → 200401
POST
/integrations/jira/config
Save Jira configuration
saveJiraConfig body → 200401
POST
/integrations/jira/issueV2
Create a Jira issue (ticket)
createJiraIssue body → 200401
POST
/collaboration/config
Create a collaboration configuration
createCollaborationConfig body → 200401
POST
/collaboration/share
Share data using a collaboration config
shareCollaboration body → 200401

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed is Error (2 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties
GenericResponse
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

armosec-integrations-api-openapi.yml Raw ↑

Other APIs ARMO publishes across the network.

ARMO Access Keys API
ARMO Clusters API
ARMO Posture API
ARMO Registry API
ARMO Runtime API
ARMO Security Risks API
ARMO Vulnerabilities API