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

MyCase Documents API

Documents and document folders associated with a case.

MyCase Documents API is one of 8 APIs that MyCase publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

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

2 operations 2 paths 4 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Server
https://api.mycase.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

  • bearerAuth — Bearer token issued through the MyCase Open API onboarding flow. The exact authorization endpoint is documented inside the authenticated Stoplight reference.

Paths & Operations 2

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

Documents 2

Documents and document folders associated with a case.

POST
/cases/{caseId}/documents
Create a Document for a Case
createDocumentForCase 1 param body → 201401422
GET
/cases/{caseId}/documents_folder
Get Case Documents Folder
getCaseDocumentsFolder 1 param → 200401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Document (7 properties), DocumentsFolder (5 properties), DocumentInput (3 properties), Error (2 properties). Each schema is shown below with its type and property counts.

DocumentsFolder
object
5 properties
DocumentInput
object
3 properties 1 required
Document
object
7 properties
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mycase-documents-api-openapi.yml Raw ↑

Other APIs MyCase publishes across the network.

MyCase Webhooks
MyCase Case Stages API
MyCase Cases API
MyCase Companies API
MyCase Contacts API
MyCase Events API
MyCase Firm API
Where this information came from

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