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

AppOmni Monitored Services API

Register and administer the SaaS services AppOmni monitors, inspect their data-sync state, rotate ingest tokens, and manage the tenant-wide custom fields, custom field values, tags and value lists attached to them.

AppOmni Monitored Services API is one of 9 APIs that AppOmni publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 22 operations across 15 paths, organized into 5 resource areas, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://{instance}.appomni.com.

22 operations 15 paths 1 schemas 1 DELETE12 GET3 PATCH6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://{instance}.appomni.com
Authentication
HTTP Bearer
Contact
Resource Areas
5

Authentication & Security 1

AppOmni Monitored Services API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — AppOmni API access token, created and managed in the AppOmni platform under Settings API Settings. Sent as Authorization: Bearer .

Paths & Operations 22

Across 15 paths, the API surfaces 22 operations — 1 DELETE, 12 GET, 3 PATCH, 6 POST. They span 5 resource areas: Monitored Services, Custom Fields, Custom Field Values for a Monitored Service, Tags, ValueList. Each is listed below with its method, path, parameters, and response codes.

Monitored Services 7
GET
/api/v1/core/monitoredservice/
List monitored services
listMonitoredServices → 200401403
GET
/api/v1/core/monitoredservice/{serviceType}/{serviceType}org/{id}
Monitored service detail
monitoredServiceDetail 2 params → 200401403
GET
/api/v1/{serviceType}/{serviceType}org/{id}/sync_timestamps/
Data syncs
dataSyncs 2 params → 200401403
POST
/api/v1/{serviceType}/{serviceType}org/{id}/request_adhoc_sync/
Request sync data type
requestSyncDataType 2 params body → 200401403
POST
/api/v1/{serviceType}/{serviceType}org/{id}/request_adhoc_all_sync/
Request sync all data types
requestSyncAllDataTypes 2 params → 200401403
PATCH
/api/v1/core/monitoredservice/{ms_id}/rotate_ingest_token/
Rotate ingest token
rotateIngestToken 1 param → 200401403
GET
/api/v1/core/monitoredservice/{ms_id}/get_ingest_token/
Get ingest token
getIngestToken 1 param → 200401403
Custom Fields 5

The Custom Fields API controls the tenant-wide fields that can be custom-created and assigned to different monitored services. Note : Delete operations for custom fields is disabl…

GET
/api/v1/core/custom_field/
List custom fields
listCustomFields 9 params → 200401403
POST
/api/v1/core/custom_field/
Create custom field
createCustomField body → 201401403
GET
/api/v1/core/custom_field/{custom_field_id}/
Retrieve a custom field
retrieveACustomField 1 param → 200401403
PATCH
/api/v1/core/custom_field/{custom_field_id}/
Update custom field
updateCustomField 1 param body → 200401403
GET
/api/v1/core/custom_field/types
List custom field types
listCustomFieldTypes → 200401403
Custom Field Values for a Monitored Service 5

The Custom Field Values API accesses the value of the custom field associated with a given monitored service.

GET
/api/v1/core/monitoredservice/{ms_id}/custom_fields/
List MS custom field value
listMSCustomFieldValue 7 params → 200401403
POST
/api/v1/core/monitoredservice/{ms_id}/custom_fields/
Create MS custom field value
createMSCustomFieldValue 1 param body → 201401403
GET
/api/v1/core/monitoredservice/{ms_id}/custom_fields/{custom_field_value_id}/
Retrieve a MS custom field value
retrieveAMSCustomFieldValue 2 params → 200401403
PATCH
/api/v1/core/monitoredservice/{ms_id}/custom_fields/{custom_field_value_id}/
Update MS custom field value
updateMSCustomFieldValue 2 params body → 200401403
DELETE
/api/v1/core/monitoredservice/{ms_id}/custom_fields/{custom_field_value_id}/
Delete MS custom field value
deleteMSCustomFieldValue 2 params → 204401403
Tags 1
GET
/api/v1/core/tag/
List tags
listTags 2 params → 200401403
ValueList 4

ValueList and ValueListElement are used to manage lists of items used by Insights. ValueLists have a type designation and will be used by Insights on convention based on their typ…

GET
/api/v1/core/valuelist/
List Value Lists
listValueLists 6 params → 200401403
POST
/api/v1/core/valuelist/
Create Value List
createValueList body → 200401403
GET
/api/v1/core/valuelistelement/
List Value List Elements
listValueListElements 6 params → 200401403
POST
/api/v1/core/valuelistelement/
Create Value List Element
createValueListElement body → 200401403

Schemas 1

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

Error
object
Standard Django REST Framework error envelope returned by the AppOmni API.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

appomni-monitored-services-api-openapi.yml Raw ↑

Other APIs AppOmni publishes across the network.

AppOmni Posture Findings API
AppOmni Policies API
AppOmni Compliance and Reports API
AppOmni Identity and Access API
AppOmni SCIM 2.0 API
AppOmni Discovery, Insights and Audit API
AppOmni Developer Platform API
AppOmni AI API
Where this information came from

This is an independent, third-party profile of AppOmni Monitored Services 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.