CyCognito Users API
The Users API from CyCognito — 2 operation(s) for users.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/cycognito-users-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
version: 0.0.1
title: CyCognito API V1 Reference Users API
description: The CyCognito API V1 is a REST API that allows you to post and get data from our main data entities—assets and issues.
tags:
- name: Users
paths:
/v1/users:
get:
description: Get user data for all users registered in your CyCognito account.
security:
- apiAuth: []
summary: Get all user data
tags:
- Users
responses:
'200':
content:
application/json:
schema:
type: array
items:
type: object
properties:
name:
description: The user's full name.
type: string
example: Marty McFly
email:
description: The user's email address.
type: string
example: marty@acme.com
roles:
description: 'Indicates the user''s permission levels corresponding to their teams. In the following example, the user has IT user permissions in Team1, Admin permissions in Team2, and Viewer permissions in all other teams: {"Team1": "it-user", "Team2":"admin", "":""viewer"}`. Supported user roles are *admin*, *viewer*, *guest*, *it-user*, and *analyst-ext*. <span name="kb-user-roles-explanation">Read more</span>.'
type: object
additionalProperties:
type: string
example: "{\n \"Team1\": \"it-user\",\n \"Team2\": \"admin\",\n \"\": \"viewer\"\n}"
activated:
description: Indicates whether or not the user has activated their account.
type: boolean
example: 'true'
invited-at:
description: Indicates the date and time at which the user received an invitation to the CyCognito platform.
anyOf:
- type: string
format: date-time
- type: 'null'
example: '2024-05-18T09:29:26.259Z'
invited-by:
description: The user who sent the invitation to the specified user.
type: string
example: Biff Tannen
last-login:
description: Indicates the date and time at which the user last signed in to the CyCognito platform.
anyOf:
- type: string
format: date-time
- type: string
- type: 'null'
example: 2024-05-20T10:31.368Z
required:
- name
- email
- roles
- activated
- invited-by
- last-login
operationId: getV1Users
x-operation-id-source: derived
post:
description: Create a new user.
security:
- apiAuth: []
summary: Create user
tags:
- Users
requestBody:
content:
application/json:
schema:
type: object
properties:
name:
description: The full name of the new user.
type: string
example: Marty McFly
email:
description: The new user's email address.
type: string
example: marty@acme.com
roles:
description: 'Designates the new user''s permission levels corresponding to their teams. In the following example, the new user will have IT user permissions in Team1, Admin permissions in Team2, and Viewer permissions in all other teams: `{"Team1": "it-user", "Team2":"admin", "":"viewer"}`. Supported user roles are *admin*, *viewer*, *guest*, *it-user*, and *analyst-ext*. <span name="kb-user-roles-explanation">Read more</span>.'
type: object
additionalProperties:
type: string
enum:
- viewer
- it-user
- admin
- analyst
- guest
example: "{\n \"Team1\": \"it-user\",\n \"Team2\": \"admin\",\n \"\": \"viewer\"\n}"
required:
- name
- email
- roles
responses:
'200':
content:
application/json:
schema:
type: object
properties:
status:
description: Indicates whether a new user was successfully added and an invitation was sent.
type: string
example: New user invitation was sent
required:
- status
operationId: postV1Users
x-operation-id-source: derived
/v1/users/{email}:
get:
description: Get user data for the specified individual user.
security:
- apiAuth: []
summary: Get individual user data
tags:
- Users
parameters:
- name: email
in: path
schema:
type: string
required: true
responses:
'200':
content:
application/json:
schema:
anyOf:
- type: object
properties:
name:
description: The user's full name.
type: string
example: Marty McFly
email:
description: The user's email address.
type: string
example: marty@acme.com
roles:
description: 'Indicates the user''s permission levels corresponding to their teams. In the following example, the user has IT user permissions in Team1, Admin permissions in Team2, and Viewer permissions in all other teams: {"Team1": "it-user", "Team2":"admin", "":""viewer"}`. Supported user roles are *admin*, *viewer*, *guest*, *it-user*, and *analyst-ext*. <span name="kb-user-roles-explanation">Read more</span>.'
type: object
additionalProperties:
type: string
example: "{\n \"Team1\": \"it-user\",\n \"Team2\": \"admin\",\n \"\": \"viewer\"\n}"
activated:
description: Indicates whether or not the user has activated their account.
type: boolean
example: 'true'
invited-at:
description: Indicates the date and time at which the user received an invitation to the CyCognito platform.
type: string
format: date-time
example: '2024-05-18T09:29:26.259Z'
invited-by:
description: The user who sent the invitation to the specified user.
type: string
example: Biff Tannen
last-login:
description: Indicates the date and time at which the user last signed in to the CyCognito platform.
anyOf:
- type: string
format: date-time
- type: string
- type: 'null'
example: 2024-05-20T10:31.368Z
required:
- name
- email
- roles
- activated
- invited-at
- invited-by
- last-login
- type: string
operationId: getV1UsersByEmail
x-operation-id-source: derived
put:
description: Edit single teams or roles for the specified user.
security:
- apiAuth: []
summary: Edit single user teams or roles
tags:
- Users
parameters:
- name: email
in: path
schema:
type: string
required: true
requestBody:
content:
application/json:
schema:
type: object
properties:
roles:
description: 'Designates the new user''s permission levels corresponding to their teams. In the following example, the new user will have IT user permissions in Team1, Admin permissions in Team2, and Viewer permissions in all other teams: {"Team1": "it-user", "Team2":"admin", "":"viewer"}`. Supported user roles are *admin*, *viewer*, *guest*, *it-user*, and *analyst-ext*. <span name="kb-user-roles-explanation">Read more</span>.'
type: object
additionalProperties:
type: string
enum:
- viewer
- it-user
- admin
- analyst
- guest
example: "{\n \"Team1\": \"it-user\",\n \"Team2\": \"admin\",\n \"\": \"viewer\"\n}"
required:
- roles
responses:
'200':
content:
application/json:
schema:
type: object
properties:
status:
description: Indicates whether the user's role within the specified team was updated.
type: string
example: User was edited.
required:
- status
operationId: putV1UsersByEmail
x-operation-id-source: derived
delete:
description: Remove a CyCognito user from the current team associated with your API key.
security:
- apiAuth: []
summary: Delete user
tags:
- Users
parameters:
- name: email
in: path
schema:
type: string
required: true
description: The email of the user who you want to remove from the current team associated with <span name="kb-api-key-management-link">your API key</span>.
responses:
'200':
content:
application/json:
schema:
type: object
properties:
status:
description: Indicates whether a user was successfully removed from the team.
type: string
example: User was deleted
required:
- status
operationId: deleteV1UsersByEmail
x-operation-id-source: derived
components:
securitySchemes:
apiAuth:
type: apiKey
name: Authorization
in: header