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
BigPanda

BigPanda Users & SCIM API

User management plus a standards-based SCIM 2.0 provisioning surface for Users and Groups.

Documentation Provider Profile APIs.io OpenAPI GitHub

BigPanda Users & SCIM API is one of 27 APIs that BigPanda publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 26 operations across 15 paths, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against 2 base URLs: https://api.bigpanda.io, https://api.eu.bigpanda.io.

26 operations 15 paths 6 schemas 2 DELETE11 GET4 PATCH7 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://api.bigpanda.io
Authentication
HTTP Bearer
Contact
BigPanda Support
License
Proprietary
Resource Areas
1

Authentication & Security 1

BigPanda Users & SCIM API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerUser11).

  • BearerUser11 — Format: "Bearer {User API Key}" BigPanda recommends adding [Authentication](https://docs.bigpanda.io/reference/introductionauthentication-and-headers) headers…

Paths & Operations 26

Across 15 paths, the API surfaces 26 operations — 2 DELETE, 11 GET, 4 PATCH, 7 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Users 26
POST
/resources/v2.1/users/activate
Activate User
postUserActivate body → 200400401404409500
POST
/resources/v2.1/users/change-password
Change user password
changeUserPassword body → 204400401403404409500
POST
/scim/v2/Groups
Create SCIM Group
createGroupSCIM body → 201400401500
GET
/scim/v2/Groups
Get SCIM Groups
getGroupsBySCIMQueryParams → 200400401500
POST
/scim/v2/Users
Create SCIM User
createUserSCIM body → 200201400401500
GET
/scim/v2/Users
Get SCIM Users
getUsersBySCIMQueryParams → 200400401500
DELETE
/scim/v2/Groups/{group_id}
Delete SCIM Group by ID
deleteGroupByIdSCIM 1 param → 204400401500
GET
/scim/v2/Groups/{group_id}
Get SCIM Group by ID
getGroupByIdSCIM 1 param → 200400401404500
PATCH
/scim/v2/Groups/{group_id}
Patch SCIM Group by ID
patchGroupByIdSCIM 1 param body → 200400401404500
PUT
/scim/v2/Groups/{group_id}
Update SCIM Group by ID
updateGroupByIdSCIM 1 param body → 200400401404500
DELETE
/resources/v2.1/users/{user_id}
Delete User by Id
deleteUserById 1 param → 200400401404409500
GET
/resources/v2.1/users/{user_id}
Get User by Id
getUserById 1 param → 200400401404500
PATCH
/resources/v2.1/users/{user_id}
Patch User by Id
patchUserById 1 param body → 200400401404500
GET
/resources/v2.1/users/{user_id}/permissions
Get User Permissions By Product
getUserPermissionsByProduct 1 param → 200400401403500
GET
/resources/v2.1/users
Get Users by Query Params
getUsersByQueryParams 11 params → 200400401500
POST
/resources/v2.1/users
Post New User
postUser body → 201400401409500
GET
/scim/v2/Users/{user_id}
Get user by ID
getUserByIdSCIM 1 param → 200400401404500
PATCH
/scim/v2/Users/{user_id}
Patch user by ID
patchUserByIdSCIM 1 param body → 200400401404500
PUT
/scim/v2/Users/{user_id}
SCIM Update user by ID
updateUserByIdSCIM 1 param body → 200400401404500
POST
/resources/v2.1/users/invite
Invite User
postUserInvitation body → 201400401404409500
POST
/resources/v2.1/users/invite/resend
Resend invite User
postUserResendInvitation body → 200400401404409500
GET
/users
Retrieve All Users
get-all-users 2 params → 200403
GET
/users/activity
Retrieve User Activity
get-user-activity 6 params → 200403
GET
/users/{userId}/roles
Retrieve User Roles
get-user-roles 1 param → 200403
PATCH
/users/{userId}/roles
Update User Roles
update-user-roles 1 param body → 200403
GET
/users/{userId}
Retrieve a User
get-a-user 1 param → 200403

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are error-response-v1 (2 properties), success-response-v1 (2 properties). Each schema is shown below with its type and property counts.

success-response-v1
object
2 properties 2 required
http-status-code-v1
number
Standard HTTP Status Code as explained in https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml
error-response-v1
object
BP default error response
2 properties 2 required
UserStateFilter-enum
string
User state
UserName
string
Resource name
id-v1
string
Object's ID

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bigpanda-users-api-openapi.yml Raw ↑

Other APIs BigPanda publishes across the network.

BigPanda Agents API (MCP & A2A)
AE Profile APIs.io
BigPanda AI Settings API
AE Profile APIs.io
BigPanda Alert Tags & Enrichment API
AE Profile APIs.io
BigPanda Alert Filters API
AE Profile APIs.io
BigPanda Alert Ingestion (OIM) API
AE Profile APIs.io
BigPanda Alerts API
AE Profile APIs.io
BigPanda API Keys API
AE Profile APIs.io
BigPanda Audit API
AE Profile APIs.io
BigPanda Biggy Query API
AE Profile APIs.io
BigPanda Change Risk API
AE Profile APIs.io
BigPanda Changes & Root Cause API
AE Profile APIs.io
BigPanda Correlation Patterns API
AE Profile APIs.io
#Users#SCIM#Identity
← Back to B APIs
API Details
ID
bigpanda:bigpanda-users-api
Base URL
https://api.bigpanda.io
Docs
https://api-docs.bigpanda.io/users-ai-detection-and-response
Provider
BigPanda
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=bigpanda-users-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/bigpanda-users-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 BigPanda Users & SCIM 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.