API archive entry · source-reported
SIGNL4 API
Use our API for systems integration or to build your own use cases. Sample scenarios include but are not limited to: 2-way integration: Triggering of Signls and updates in the third party systems when alert state changes occur Retrieving alarms for logging purposes Calendar integrations: Creation and management of on-call duties Punch users in and out based on external calendars etc. AUTHENTICATION Using the API requires an API key, which you can generate in the SIGNL4 portal under 'Developers'. This key must then be specified in a special header in every HTTP request. This header is called X-S4-Api-Key . The base URL of the API is https://connect.signl4.com/api/ . Copyright © Derdack GmbH
Documentation & source
Use the provider’s reference for current endpoints, setup, limits and terms.
No separate documentation URL has been confirmed for this record.
Provider content retains its own terms. This listing does not grant reuse or training rights.
Access at a glance
These are reported access facts. Check the current documentation before integrating.
- Authentication: Unknown.
- HTTPS: not confirmed.
- Browser access (CORS): Unknown.
Pricing and limits
Current plans, quotas, and rate limits have not been reviewed for this listing. Check the provider’s current terms; no authentication does not necessarily mean free usage.
Documentation and sources
Imported from APIs.guru OpenAPI Directory. A detailed editorial review has not been published yet.
APIs.guru OpenAPI Directory · CC0 contributed definitions; upstream provider terms may differ
More Communication APIs
Airflow API (Stable)
# Overview To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases. Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ``` ## Resources The term `resource` refers to a single type of object in the Airflow metadata. An API is broken up by its endpoint's corresponding resource. The name of a resource is typically plural and expressed in camelCase. Example: `dagRuns`. Resource names are used as part of endpoint URLs, as well as in API parameters and responses. ## CRUD Operations The platform supports **C**reate, **R**ead, **U**pdate, and **D**elete operations on most resources. You can review the standards for these operations and their standard parameters below. Some endpoints have special behavior as exceptions. ### Create To create a resource, you typically submit an HTTP `POST` request with the resource's required metadata in the request body. The response returns a `201 Created` response code upo
Unknown · HTTPS unconfirmed · CORS Unknown
Airflow API (Stable)
# Overview To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases. Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ``` ## Resources The term `resource` refers to a single type of object in the Airflow metadata. An API is broken up by its endpoint's corresponding resource. The name of a resource is typically plural and expressed in camelCase. Example: `dagRuns`. Resource names are used as part of endpoint URLs, as well as in API parameters and responses. ## CRUD Operations The platform supports **C**reate, **R**ead, **U**pdate, and **D**elete operations on most resources. You can review the standards for these operations and their standard parameters below. Some endpoints have special behavior as exceptions. ### Create To create a resource, you typically submit an HTTP `POST` request with the resource's required metadata in the request body. The response returns a `201 Created` response code upo
Unknown · HTTPS unconfirmed · CORS Unknown
API iSendPro
[1] Liste des fonctionnalités : - envoi de SMS à un ou plusieurs destinataires, - lookup HLR, - récupération des récapitulatifs de campagne, - gestion des répertoires, - ajout en liste noire. - comptage du nombre de caractères des SMS [2] Pour utiliser cette API vous devez: - Créer un compte iSendPro sur https://isendpro.com/ - Créditer votre compte - Remarque: obtention d'un crédit de test possible sous conditions - Noter votre clé de compte (keyid) - Elle vous sera indispensable à l'utilisation de l'API - Vous pouvez la trouver dans le rubrique mon "compte", sous-rubrique "mon API" - Configurer le contrôle IP - Le contrôle IP est configurable dans le rubrique mon "compte", sous-rubrique "mon API" - Il s'agit d'un système de liste blanche, vous devez entrer les IP utilisées pour appeler l'API - Vous pouvez également désactiver totalement le contrôle IP
Unknown · HTTPS unconfirmed · CORS Unknown
D7SMS
D7 SMS allows you to reach your customers via SMS over D7's own connectivity to global mobile networks. D7 provides reliable and cost-effective SMS services to businesses across all industries and aims to connect all countries and territories via direct connections.
Unknown · HTTPS unconfirmed · CORS Unknown
FastAPI
FastAPI: API definition published in the OpenAPI directory for botschaft.local. See the linked specification for supported operations.
Unknown · HTTPS unconfirmed · CORS Unknown
Qakka
API for Qakka Queue System
Unknown · HTTPS unconfirmed · CORS Unknown
Source reference
This page separates source-reported facts from questions that need live provider verification.