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

Miro User API

The User API from Miro — 2 operation(s) for user.

Miro User API is one of 51 APIs that Miro publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 6 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version v2.0.

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

6 operations 2 paths 5 schemas 1 DELETE2 GET1 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2.0
Base URL
https://api.miro.com/v2
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Miro User API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oAuth2AuthCode) using the authorizationCode flow, exposing 8 scopes.

  • oAuth2AuthCode — For more information, see https://developers.miro.com/reference/authorization-flow-for-expiring-tokens

Paths & Operations 6

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

User 6
GET
/Users
List users
listUsers 6 params → 200400401403404429500
POST
/Users
Create user
createUser body → 201400401403404409413429
GET
/Users/{id}
Get user
getUser 2 params → 200400401403404429500
PUT
/Users/{id}
Replace user
replaceUser 1 param body → 200400401403404409429500
PATCH
/Users/{id}
Patch user
patchUser 1 param body → 200400401403404409429500
DELETE
/Users/{id}
Delete user
deleteUser 1 param → 204400401403404409429500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are UserResource (14 properties), CreateUserResource (10 properties), UserListResponse (5 properties), PatchUserResource (2 properties). Each schema is shown below with its type and property counts.

CreateUserResponse
UserListResponse
object
5 properties
CreateUserResource
object
10 properties 1 required
UserResource
object
14 properties
PatchUserResource
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

miro-user-api-openapi.yml Raw ↑

Other APIs Miro publishes across the network.

Miro AI Interaction Logs API
Miro App card items API
Miro App metrics (experimental) API
Miro Audit Logs API
Miro Board classification: Board level API
Miro Board classification: Organization level API
Miro Board classification: Team level API
Miro Board Content Logs API
Miro Board Export API
Miro Board members API
Miro Boards API
Miro Bulk operations API
Where this information came from

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