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

Middesk subpackage_signals API

The subpackage_signals API from Middesk — 2 operation(s) for subpackage_signals.

Middesk subpackage_signals API is one of 28 APIs that Middesk publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 3 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

3 operations 2 paths 8 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.middesk.com/v1/
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Middesk subpackage_signals API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearer_auth).

Paths & Operations 3

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

subpackage_signals 3
GET
/v1/signals
List signals
list-signals 12 params → 200
POST
/v1/signals
Create a signal
create-signal 1 param body → 201422
GET
/v1/signals/{id}
Retrieve a signal
get-signal 2 params → 200404

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are type__Signal (14 properties), type__SignalReasonsItem (5 properties), type_signals_ListSignalsResponse (4 properties), type__SignalRequester (3 properties). Each schema is shown below with its type and property counts.

type__ErrorResponseErrorsItem
object
1 property 1 required
type__ErrorResponse
object
1 property 1 required
type__SignalReasonsItemCategory
string
type_signals_ListSignalsResponse
object
4 properties 2 required
type__SignalReasonsItemCode
string
type__SignalRequester
object
3 properties 3 required
type__Signal
object
14 properties 4 required
type__SignalReasonsItem
object
5 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

middesk-subpackage-signals-api-openapi.yml Raw ↑

Other APIs Middesk publishes across the network.

Middesk subpackage_actions API
Middesk subpackage_agents API
Middesk subpackage_applications API
Middesk subpackage_businessBatches API
Middesk subpackage_businesses API
Middesk subpackage_companies API
Middesk subpackage_connections API
Middesk subpackage_documents API
Middesk subpackage_identities API
Middesk subpackage_informationRequests API
Middesk subpackage_jurisdictions API
Middesk subpackage_liens API
Where this information came from

This is an independent, third-party profile of Middesk subpackage_signals 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.