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

Beyond Identity Applications API

An application represents a client application that uses Beyond Identity for authentication. This could be a native app, a single-page application, regular web application, or machine-to-machine application credentials.

Beyond Identity Applications API is one of 17 APIs that Beyond Identity publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Application. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 2 JSON Schemas.

This API exposes 5 operations across 2 paths, and defines 11 schemas. It is described by OpenAPI 3.0.1, at version 1.7.0.

Requests are made against 3 base URLs: https://api-us.beyondidentity.com, https://api-eu.beyondidentity.com, https://api.us1.beyondidentity-gov.com/.

5 operations 2 paths 11 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.7.0
Base URL
https://api-us.beyondidentity.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Beyond Identity Applications API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — See the [Authentication](section/Authentication) section for details.

Paths & Operations 5

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

Applications 5

An application represents a client application that uses Beyond Identity for authentication. This could be a native app, a single-page application, regular web application, or mac…

POST
/v1/tenants/{tenant_id}/realms/{realm_id}/applications
Create a New Application
CreateApplication 2 params body → 200400401403404500
GET
/v1/tenants/{tenant_id}/realms/{realm_id}/applications
List Applications for a Realm
ListApplications 4 params → 200400401403404500
GET
/v1/tenants/{tenant_id}/realms/{realm_id}/applications/{application_id}
Retrieve an Existing Application
GetApplication 3 params → 200401403404500
PATCH
/v1/tenants/{tenant_id}/realms/{realm_id}/applications/{application_id}
Patch an Application
UpdateApplication 3 params body → 200400401403404500
DELETE
/v1/tenants/{tenant_id}/realms/{realm_id}/applications/{application_id}
Delete an Application
DeleteApplication 3 params → 200401403404500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are SsoConfigSamlPartialUpdate (32 properties), Application (8 properties), Error (3 properties), ListApplicationsResponse (3 properties). Each schema is shown below with its type and property counts.

SsoConfigPayload
SsoConfigSamlPartialUpdate
object
32 properties 1 required
Application
object
An application represents a client application that uses Beyond Identity for authentication. This could be a native app, a single-page application, regular web…
8 properties
ErrorDetail
object
Additional details for errors designed to support client applications.
1 property 1 required
Error
object
3 properties 2 required
GrantType
array
Grant types supported by this application's token endpoint. Allowable values are: - authorizationcode: The authorization code grant type defined in OAuth 2.0,…
PkceConfig
string
PKCE code challenge methods supported for applications, as defined by [RFC-7636](https://datatracker.ietf.org/doc/html/rfc7636). Allowable values are: - disabl…
TokenConfiguration
object
Properties of a token issued for an application.
3 properties 1 required
ListApplicationsResponse
object
Response for ListApplications.
3 properties 2 required
TokenEndpointAuthMethod
string
Indicator of the requested authentication method for the token endpoint. Allowable values are: - clientsecretpost: The client uses the HTTP POST parameters as…
Confidentiality
string
The confidentiality of the client, as prescribed by OAuth 2.0 and OIDC. Confidentiality is based on a client's ability to authenticate securely with the author…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

beyond-identity-applications-api-openapi.yml Raw ↑

Other APIs Beyond Identity publishes across the network.

Beyond Identity Next Generation API
Beyond Identity Authenticator Configurations API
Beyond Identity Credential Binding Jobs API
Beyond Identity Credentials API
Beyond Identity Groups API
Beyond Identity Identities API
Beyond Identity Identity Provider API
Beyond Identity Launch Mechanisms API
Beyond Identity Realms API
Beyond Identity Resource Servers API
Beyond Identity Roles API
Beyond Identity SCIM API
Where this information came from

This is an independent, third-party profile of Beyond Identity Applications 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.