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

SIMBA Chain Client Credentials API

The Client Credentials API from SIMBA Chain — 10 operation(s) for client credentials.

SIMBA Chain Client Credentials API is one of 19 APIs that SIMBA Chain publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 17 operations across 10 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 2.10.1.

Requests are made against the base URL https://blocks.simbachain.com/api/platform-service.

17 operations 10 paths 16 schemas 3 DELETE5 GET3 POST6 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.10.1
Base URL
https://blocks.simbachain.com/api/platform-service
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

SIMBA Chain Client Credentials API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2AuthorizationCodeBearer) using the authorizationCode flow.

Paths & Operations 17

Across 10 paths, the API surfaces 17 operations — 3 DELETE, 5 GET, 3 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.

Client Credentials 17
POST
/organisations/{organisation_name}/client_credentials/
Create Client Credential
create_client_credential_organisations__organisation_name__client_credentials__post 1 param body → 201422
GET
/organisations/{organisation_name}/client_credentials/
Get Client Credentials
get_client_credentials_organisations__organisation_name__client_credentials__get 13 params → 200422
PUT
/organisations/{organisation_name}/client_credentials/
Admin Add Client Credential To Org Or Domain
admin_add_client_credential_to_org_or_domain_organisations__organisation_name__client_credentials__put 1 param body → 200422
GET
/organisations/{organisation_name}/client_credentials/{client_id}
Get Client Credential
get_client_credential_organisations__organisation_name__client_credentials__client_id__get 2 params → 200422
PUT
/organisations/{organisation_name}/client_credentials/{client_id}
Update Client Credential
update_client_credential_organisations__organisation_name__client_credentials__client_id__put 2 params body → 200422
DELETE
/organisations/{organisation_name}/client_credentials/{client_id}
Revoke Client Credential
revoke_client_credential_organisations__organisation_name__client_credentials__client_id__delete 2 params → 200422
PUT
/organisations/{organisation_name}/client_credentials/{client_id}/roles/
Update Client Credential Roles
update_client_credential_roles_organisations__organisation_name__client_credentials__client_id__roles__put 2 params body → 200422
POST
/organisations/{organisation_name}/client_credentials/{client_id}/roles/add/
Add Organisation Client Credential Roles
add_organisation_client_credential_roles_organisations__organisation_name__client_credentials__client_id__roles_add__post 2 params body → 200422
DELETE
/organisations/{organisation_name}/client_credentials/{client_id}/roles/remove/
Remove Organisation Client Credential Roles
remove_organisation_client_credential_roles_organisations__organisation_name__client_credentials__client_id__roles_remove__delete 2 params body → 200422
PUT
/organisations/{organisation_name}/client_credentials/{client_id}/refresh
Refresh Client Credential Secret
refresh_client_credential_secret_organisations__organisation_name__client_credentials__client_id__refresh_put 2 params → 200422
GET
/user_accounts/{user_account_id}/client_credentials/
Get User Client Credentials
get_user_client_credentials_user_accounts__user_account_id__client_credentials__get 12 params → 200422
POST
/user_accounts/{user_account_id}/client_credentials/
Create Impersonate User Client Credentials
create_impersonate_user_client_credentials_user_accounts__user_account_id__client_credentials__post 1 param body → 201422
GET
/user_accounts/{user_account_id}/client_credentials/{client_id}
Get User Client Credential
get_user_client_credential_user_accounts__user_account_id__client_credentials__client_id__get 2 params → 200422
PUT
/user_accounts/{user_account_id}/client_credentials/{client_id}
Update User Client Credential
update_user_client_credential_user_accounts__user_account_id__client_credentials__client_id__put 2 params body → 200422
DELETE
/user_accounts/{user_account_id}/client_credentials/{client_id}
Revoke User Client Credential
revoke_user_client_credential_user_accounts__user_account_id__client_credentials__client_id__delete 2 params → 200422
PUT
/user_accounts/{user_account_id}/client_credentials/{client_id}/refresh
User Refresh User Client Credential Secret
user_refresh_user_client_credential_secret_user_accounts__user_account_id__client_credentials__client_id__refresh_put 2 params → 200422
GET
/client_credentials/
List Global Client Credentials
list_global_client_credentials_client_credentials__get 12 params → 200422

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are ClientCredential (13 properties), OrganisationWithRoles (8 properties), Organisation (7 properties), Page_ClientCredential_ (5 properties). Each schema is shown below with its type and property counts.

ValidationError
object
5 properties 3 required
AddIdentityRolesInput
object
2 properties
UpdateClientCredentialInput
object
1 property 1 required
UpdateIdentityRolesInput
object
2 properties
OrganisationWithRoles
object
8 properties 4 required
RoleMinimal
object
4 properties 1 required
CreateInviteSubOrgsInput
object
3 properties 1 required
Organisation
object
A model representing an organisation. The field name is unique.
7 properties 3 required
HTTPValidationError
object
1 property
Page_ClientCredential_
object
5 properties 5 required
CreateImpersonateClientCredentialInput
object
2 properties 1 required
ClientCredential
object
13 properties 6 required
FreshClientCredential
object
Only time the plain secret is provided, at it's creation
4 properties 3 required
CreateClientCredentialInput
object
3 properties 1 required
SystemTypes
string
AdminAddClientCredentialToOrgDomain
object
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

simba-chain-client-credentials-api-openapi.yml Raw ↑

Other APIs SIMBA Chain publishes across the network.

SIMBA Blocks Platform Service (Dynamic Contract API)
SIMBA Blocks Documentation MCP Server
SIMBA Chain Authentication API
SIMBA Chain Bulk Users Import Requests API
SIMBA Chain Device App Admin API
SIMBA Chain Device App Registration API
SIMBA Chain Domains API
SIMBA Chain Events API
SIMBA Chain Invites API
SIMBA Chain Organisations API
SIMBA Chain Passkeys API
SIMBA Chain Permissions API
Where this information came from

This is an independent, third-party profile of SIMBA Chain Client Credentials 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.