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
DoiT

DoiT Support Requests API

Create and manage support tickets with DoiT.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Support Requests. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 9 operations across 4 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version v1.

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

9 operations 4 paths 13 schemas 1 DELETE4 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 3

DoiT Support Requests API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (api_key). An API key is passed in the header as X-Tenant-Id (tenantId). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 1 scope. By default, every request must be authenticated.

  • api_key — Use the "Bearer " format or sign in for autofill
  • tenantId — Tenant (customer) ID that sets the request's customer context. Required when the credential can access more than one tenant; omit when the credential is scoped…

Paths & Operations 9

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

Support Requests 9

Create and manage support tickets with DoiT.

GET
/support/v1/tickets
List requests
idOfTickets 5 params → 200400401403404502503
POST
/support/v1/tickets
Create a request
idOfTicketsPost body → 201400401403404
GET
/support/v1/tickets/{ticketId}
Get a request
idOfTicketGet 1 param → 200400401403404502503
PATCH
/support/v1/tickets/{ticketId}
Update a request
idOfTicketUpdate 1 param body → 200400401403404
GET
/support/v1/tickets/{ticketId}/comments
List request comments
idOfTicketCommentsList 1 param → 200401403404502503
POST
/support/v1/tickets/{ticketId}/comments
Add a comment
idOfTicketCommentsPost 1 param body → 201400401403404
GET
/support/v1/tickets/{ticketId}/tags
List tags on a support request
listTicketTags 1 param → 200400401403404
POST
/support/v1/tickets/{ticketId}/tags
Add tags to a support request
idOfTicketTagsAdd 1 param body → 200400401403404
DELETE
/support/v1/tickets/{ticketId}/tags
Remove tags from a support request
idOfTicketTagsRemove 1 param body → 200400401403404

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are TicketDetailExtAPI (14 properties), TicketListItem (12 properties), TicketResponseExtAPI (9 properties), TicketExtAPI (6 properties). Each schema is shown below with its type and property counts.

CreateCommentRequest
object
Request body for adding a comment to a support ticket.
2 properties 1 required
TicketsList
object
List of support tickets.
3 properties
TicketResponseExtAPI
object
Response returned after creating a ticket.
9 properties
Error
object
Standard error response structure.
1 property
CommentExtAPI
object
A comment on a support ticket.
5 properties
TagsResponse
object
Response body echoing the tags the operation actually acted on, after server-side transformation (trim + lowercase + customer namespace prefix where applicable…
1 property
TicketDetailExtAPI
object
Detailed information about a single support ticket.
14 properties
TicketExtAPI
object
Payload to create a support ticket via API.
6 properties 5 required
TicketListItem
object
Summary information about a support ticket.
12 properties
CommentsResponseExtAPI
object
Response containing all comments on a support ticket.
1 property
TicketCreateFormExtAPI
object
Wrapper object for creating support tickets via the external API.
1 property 1 required
TagsRequest
object
Request body for adding (POST) or removing (DELETE) tags on a support request. The operation is surgical — only the tags listed are affected; any other tags on…
1 property 1 required
TagsGetResponse
object
Response body for GET /support/v1/tickets/{ticketId}/tags. Contains the current tags visible to the caller.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

doit-support-requests-api-openapi.yml Raw ↑

Other APIs DoiT publishes across the network.

DoiT MCP Server
AE Profile APIs.io
DoiT Account Team API
AE Profile APIs.io
DoiT Alerts API
AE Profile APIs.io
DoiT Allocations API
AE Profile APIs.io
DoiT Annotations API
AE Profile APIs.io
DoiT Anomalies API
AE Profile APIs.io
DoiT Assets API
AE Profile APIs.io
DoiT Auth API
AE Profile APIs.io
DoiT Ava API
AE Profile APIs.io
DoiT Billing Transfer API
AE Profile APIs.io
DoiT Budget Suggestions API
AE Profile APIs.io
DoiT Budgets API
AE Profile APIs.io
#Support Requests
← Back to D APIs
API Details
ID
doit:doit-support-requests-api
Base URL
https://api.doit.com
Docs
https://developer.doit.com/
Provider
DoiT
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=doit-support-requests-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/doit-support-requests-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 DoiT Support Requests 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.