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

Apiman Users API

The Users API from Apiman — 13 operation(s) for users.

Apiman Users API is one of 16 APIs that Apiman 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.

This API exposes 16 operations across 13 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 3.1.0-SNAPSHOT.

Requests are made against a single base URL, /apiman.

16 operations 13 paths 23 schemas 11 GET1 HEAD2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.1.0-SNAPSHOT
Base URL
https://{apiman_host}/apiman
Resource Areas
1

Paths & Operations 16

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

Users 16
POST
/users/{userId}/notifications/filters
createNotificationFilter 1 param body → default
GET
/users/{userId}
get_5 1 param → 200
PUT
/users/{userId}
update_4 1 param body → 204
GET
/users/{userId}/activity
getActivity 3 params → 200
GET
/users/{userId}/apiorgs
getApiOrganizations 1 param → 200
GET
/users/{userId}/apis
getApis 1 param → 200
GET
/users/{userId}/clientorgs
getClientOrganizations 1 param → 200
GET
/users/{userId}/viewable-clients
getClients 1 param → 200
GET
/users/{userId}/editable-clients
getEditableClients 1 param → 200
GET
/users/currentuser/info
getInfo → 200
PUT
/users/{userId}/notifications
markNotifications 1 param body → 202
POST
/users/{userId}/notifications
getNotificationsForUser 1 param body → 200
HEAD
/users/{userId}/notifications
getNotificationCountForUser 2 params → 204
GET
/users/{userId}/organizations
getOrganizations 1 param → 200
GET
/users/{userId}/permissions
getPermissionsForUser 1 param → 200
GET
/users/{userId}/planorgs
getPlanOrganizations 1 param → 200

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are NotificationDtoObject (10 properties), AuditEntryBean (9 properties), ApiSummaryBean (8 properties), CurrentUserBean (8 properties). Each schema is shown below with its type and property counts.

SearchResultsBeanNotificationDtoObject
object
2 properties
NotificationPreferenceEntity
object
4 properties 1 required
CurrentUserBean
object
8 properties
NotificationDtoObject
object
10 properties
PagingBean
object
2 properties
PermissionBean
object
2 properties
NotificationActionDto
object
3 properties 1 required
AuditEntryBean
object
9 properties
UpdateUserBean
object
3 properties
UserBean
object
6 properties
SearchResultsBeanAuditEntryBean
object
2 properties
CreateNotificationFilterDto
object
5 properties
NotificationCriteriaBean
object
5 properties
SearchCriteriaBean
object
5 properties
OrderByBean
object
2 properties
SearchCriteriaFilterBean
object
3 properties
KeyValueTagDto
object
Key value tag pair
2 properties 1 required
ApiSummaryBean
object
8 properties
UserPermissionsBean
object
2 properties
OrganizationSummaryBean
object
6 properties
UserDto
object
6 properties 5 required
ClientSummaryBean
object
7 properties
NotificationFilterEntity
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

apiman-users-api-openapi.yml Raw ↑

Other APIs Apiman publishes across the network.

Apiman Actions API
Apiman Blobs API
Apiman Developers API
Apiman Devportal API
Apiman Downloads API
Apiman Events API
Apiman Experimental API
Apiman Gateways API
Apiman Organizations API
Apiman Plugins API
Apiman Policy Definitions API
Where this information came from

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