How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Armor Support API

The Support API from Armor — 16 operation(s) for support.

Armor Support API is one of 70 APIs that Armor publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 18 operations across 16 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.armor.com.

18 operations 16 paths 26 schemas 1 DELETE14 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.armor.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Armor Support API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (Authorization). An API key is passed in the header as X-Account-Context (X-Account-Context).

  • Authorization — Authorization Token
  • X-Account-Context — X-Account-Context

Paths & Operations 18

Across 16 paths, the API surfaces 18 operations — 1 DELETE, 14 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Support 18
GET
/tickets/{issueKeyId}/comments
Get ticket comments for given issueKeyId
Tickets_GetTicketComments 5 params → 200400
POST
/tickets/{issueKeyId}/comments
Add comment to a JSD ticket
Tickets_CreateTicketComment 1 param body → 200400
GET
/tickets/{issueKeyId}/details
Get Ticket Details
Tickets_GetIssueDetails 1 param → 200400404
GET
/tickets/{issueKeyId}/transition
Gets Available transition statuses for given ticket
Tickets_GetAvailableIssueStatuses 1 param → 200400404
POST
/tickets/{issueKeyId}/transition
Transition status for ticket in question and add optional comment
Tickets_TransitionIssueStatus 1 param body → 200400
GET
/tickets/{ticketNumber}
(Archive Only) Retrieve the details for a given ticket.
Tickets_GetTicket 1 param → 200404
GET
/tickets/{ticketNumber}/attachments
(Archive Only) Return an attachment associated with ticket.
Tickets_GetAttachment 1 param → 200
GET
/tickets/count
(Archive Only) Return the count of all the tickets on the account.
Tickets_GetPagedTicketsCount → 200
GET
/tickets/entries
(Archive Only) Return a list of support tickets entries.
Tickets_GetPagedTickets 8 params → 200400
GET
/tickets/groups
Return ticketing organizations for an individual account
Tickets_GetTicketGroupsByAccountId → 200400500
DELETE
/tickets/groups/{id}/member/{userId}
Remove individual user from a specific ticketing organization
Tickets_RemoveTicketGroupMember 2 params → 200400500
GET
/tickets/groups/{id}/members
Return members of a specific ticketing organization
Tickets_GetTicketsGroupMembers 1 param → 200400500
POST
/tickets/groups/member
Add individual user to a specific ticketing organization
Tickets_AddTicketGroupMember body → 200400500
GET
/tickets/list
Returns all tickets accessible by the calling user
Tickets_GetIssuesForAccount 5 params → 200400404
GET
/tickets/list-all
Returns all tickets regardless of the calling user
Tickets_GetAllIssuesForAccount 5 params → 200400404
GET
/tickets/members/groups
Return ticketing organizations for an individual user
Tickets_GetTicketGroupsByUserId → 200400500
GET
/tickets/meta-data
(Archive Only) Return ticket meta-data for a list of tickets.
Tickets_GetTicketsMetaData → 200
GET
/tickets/users
Return list of users with permissions to Armor ticketing
Tickets_GetUsersWithTicketingPermissions → 200400500

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are FireHost.Infrastructure.Tickets.Models.TicketDetailsDto (35 properties), FireHost.Infrastructure.Tickets.Models.TicketDto (30 properties), FireHost.Infrastructure.Tickets.Models.TicketCommentDto (11 properties), FireHost.Services.Http.Tickets.ApiExamples.Models.IssueDetailsSampleResponse (11 properties). Each schema is shown below with its type and property counts.

FireHost.Infrastructure.Tickets.Models.TicketAttachmentDto
object
5 properties
FireHost.Infrastructure.Tickets.Models.TicketRelatedServerDto
object
4 properties
FireHost.Infrastructure.Tickets.Models.Responses.TicketGroupsResponseDto
object
5 properties
FireHost.Infrastructure.Tickets.Models.TicketDto
object
30 properties
FireHost.Services.ServiceDesk.Request.AssetsDto
object
2 properties
FireHost.Services.ServiceDesk.Response.JiraIssueStatus
object
2 properties
FireHost.Infrastructure.Tickets.Models.ParticipantDto
object
3 properties
FireHost.Infrastructure.Tickets.Models.Responses.TicketGroupMembersDto
object
10 properties
FireHost.Infrastructure.Tickets.Models.JiraTicketOrganizationDto
object
2 properties
FireHost.Infrastructure.Tickets.Models.Responses.TicketMetadataResponse
object
4 properties
FireHost.Services.Http.Tickets.ApiExamples.Models.IssueDetailsSampleResponse
object
11 properties
FireHost.Infrastructure.Tickets.Models.TicketCommentDto
object
11 properties
FireHost.Services.Http.Tickets.ApiExamples.CreateTicketCommentExampleRequest
object
FireHost.Infrastructure.Tickets.Models.RequestTypeDto
object
3 properties
FireHost.Infrastructure.Tickets.Models.TicketDetailsDto
object
35 properties
FireHost.Infrastructure.Tickets.Models.TicketResultDto
object
2 properties
FireHost.Infrastructure.Tickets.Models.TicketRecipientDto
object
8 properties
FireHost.Services.ServiceDesk.Response.ServiceDeskTransitions
object
2 properties
FireHost.Services.Http.Tickets.ApiExamples.Models.IssueSummarySampleResponse
object
6 properties
FireHost.Services.Http.Tickets.ApiExamples.Models.AddTicketGroupMemberSampleRequest
object
3 properties
FireHost.Infrastructure.Tickets.Models.Insight.InsightAccountDto
object
2 properties
FireHost.Infrastructure.Tickets.Models.TicketRelatedTicketDto
object
2 properties
FireHost.Infrastructure.Tickets.Models.Responses.JiraTicketComments
object
4 properties
FireHost.Services.Http.Tickets.ApiExamples.Models.TransitionTicketSampleRequest
object
2 properties
FireHost.Infrastructure.Tickets.Models.TicketStatusDto
object
5 properties
FireHost.Infrastructure.Tickets.Models.TicketUser
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

armor-support-api-openapi.yml Raw ↑

Other APIs Armor publishes across the network.

Armor Access Control Lists API
Armor Account API
Armor Account Management API
Armor Account Primary Billing API
Armor Active Response API
Armor Advanced Backup API
Armor AIP - Entity Intelligence API
Armor AIP - Incident Data API
Armor Assessments API
Armor Authentication API
Armor Cloud Connections API
Armor Connector API
Where this information came from

This is an independent, third-party profile of Armor Support API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.