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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
TaskCall

TaskCall Incidents API

The Incidents API from TaskCall — 23 operation(s) for incidents.

Documentation Provider Profile APIs.io OpenAPI GitHub

TaskCall Incidents API is one of 3 APIs that TaskCall publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Incidents. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 23 operations across 23 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://incidents-api.taskcallapp.com, https://incidents-api.us.taskcallapp.com.

23 operations 23 paths 0 schemas 23 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://incidents-api.taskcallapp.com
Authentication
API Key
Contact
TaskCall
Resource Areas
1

Authentication & Security 1

TaskCall Incidents API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (tokenAuth). By default, every request must be authenticated.

  • tokenAuth — API key formatted as: token

Paths & Operations 23

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

Incidents 23
POST
/incidents/create
Create incident
createIncident → 200
POST
/incidents/list
List incidents
listIncidents → 200
POST
/incidents/details
Get incident details
getIncidentDetails → 200
POST
/incidents/alerts
Get incident alerts
getIncidentAlerts → 200
POST
/incidents/acknowledge
Acknowledge incident
acknowledgeIncident → 200
POST
/incidents/resolve
Resolve incident
resolveIncident → 200
POST
/incidents/escalate
Escalate incident
escalateIncident → 200
POST
/incidents/reassign
Reassign incident
reassignIncident → 200
POST
/incidents/snooze
Snooze incident
snoozeIncident → 200
POST
/incidents/unacknowledge
Unacknowledge incident
unacknowledgeIncident → 200
POST
/incidents/amend-urgency
Amend urgency
amendUrgency → 200
POST
/incidents/add-responders
Add responders
addResponders → 200
POST
/incidents/notate
Add notes to incident
notateIncident → 200
POST
/incidents/merge
Merge incidents
mergeIncidents → 200
POST
/incidents/unmerge
Unmerge alerts
unmergeIncident → 200
POST
/incidents/add-subscribers
Add subscribers
addSubscribers → 200
POST
/incidents/remove-subscribers
Remove subscribers
removeSubscribers → 200
POST
/incidents/update-status
Publish status update
updateStatus → 200
POST
/incidents/add-impact
Add business impact
addImpact → 200
POST
/incidents/remove-impact
Remove business impact
removeImpact → 200
POST
/incidents/run-workflow
Run workflow
runWorkflow → 200
POST
/incidents/edit-title
Edit incident title
editTitle → 200
POST
/incidents/update-tags
Update incident tags
updateTags → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

taskcall-incidents-api-openapi.yml Raw ↑

Other APIs TaskCall publishes across the network.

TaskCall Incidents API
AE Profile APIs.io
TaskCall Components API
AE Profile APIs.io
#Incidents
← Back to T APIs
API Details
ID
taskcall:taskcall-incidents-api
Base URL
https://incidents-api.taskcallapp.com
Docs
https://docs.taskcallapp.com/api-access/v1/incidents-api
Provider
TaskCall
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=taskcall-incidents-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/taskcall-incidents-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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