Update application

Updates an existing application using JSON Merge Patch (RFC 7396).
Only provided (non-null) fields will be updated. Omitted fields remain unchanged.

Updatable fields:

  • applicationName: Unique name within tenant
  • status: ACTIVE, SUSPENDED, or DISABLED
  • displayName: Human-readable name for UI
  • description: Purpose and scope description
  • environment: PRODUCTION, STAGING, DEVELOPMENT, or SANDBOX
  • businessUnit: Organizational unit
  • costCenter: Cost center for chargeback
  • ownerName: Business owner name
  • ownerEmail: Business owner email
  • technicalContactName: Technical contact name
  • technicalContactEmail: Technical contact email
  • dataClassification: PUBLIC, INTERNAL, CONFIDENTIAL, or RESTRICTED
  • riskLevel: LOW, MEDIUM, HIGH, or CRITICAL
  • regulatoryScope: Array of regulations (e.g., PCI-DSS, SOX, GDPR)
  • tags: Free-form tags (full replacement)
  • externalRefs: External system references (full replacement)
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required
string
required
Body Params

Request payload for partially updating an APPLICATION business container using
JSON Merge Patch (RFC 7396). Only fields that are provided (non-null) will be
updated. Omitted fields remain unchanged. Applications are business-entity
containers; authentication is performed through their Cryptographic Actors,
not through the Application directly — credential management is exposed under
/actors/{actorId}/credentials.

string
length between 0 and 255

New unique name for the application within the tenant. If provided, must be unique
across all applications in the same tenant (case-insensitive). Used for identification
and management purposes. Omit this field to keep the current name unchanged.

string
enum

New operational status for the application. Controls whether the application can authenticate:
ACTIVE - Application can authenticate and access resources normally.
SUSPENDED - Temporarily disabled, authentication attempts will be rejected.
DISABLED - Permanently disabled, cannot be reactivated.
Omit this field to keep the current status unchanged.

Allowed:
string
length between 0 and 255

Human-readable name for UI and reports. Used in dashboards and governance views.
Omit to keep current display name unchanged.

string

Purpose and scope description. Helps with governance and documentation.
Omit to keep current description unchanged.

string
enum

Environment classification for lifecycle management:
PRODUCTION - Live production environment.
STAGING - Pre-production staging environment.
DEVELOPMENT - Development and testing environment.
SANDBOX - Isolated sandbox for experiments.
Omit to keep current environment unchanged.

Allowed:
string
length between 0 and 255

Organizational unit responsible for this application. Used for reporting and cost allocation.
Omit to keep current business unit unchanged.

string
length between 0 and 100

Cost center for chargeback and billing purposes. Links to financial systems.
Omit to keep current cost center unchanged.

string
length between 0 and 255

Business owner name. Primary contact for business decisions and approvals.
Omit to keep current owner name unchanged.

string
length between 0 and 320

Business owner email for critical notifications. Used for incident escalation and approvals.
Omit to keep current owner email unchanged.

string
length between 0 and 255

Technical contact name for incident response. Primary technical point of contact.
Omit to keep current technical contact name unchanged.

string
length between 0 and 320

Technical contact email for incident response. Used for technical issue escalation.
Omit to keep current technical contact email unchanged.

string
enum

Data sensitivity level for compliance:
PUBLIC - Publicly available information.
INTERNAL - Internal use only.
CONFIDENTIAL - Sensitive internal information.
RESTRICTED - Highly sensitive, regulated data.
Omit to keep current data classification unchanged.

Allowed:
string
enum

Operational risk level for incident prioritization:
LOW - Minimal operational impact.
MEDIUM - Moderate operational impact.
HIGH - Significant operational impact.
CRITICAL - Mission-critical system.
Omit to keep current risk level unchanged.

Allowed:
regulatoryScope
array of strings

Applicable regulations for compliance tracking. Examples: PCI-DSS, SOX, GDPR, HIPAA, DORA.
Full replacement strategy: provide complete array to replace current scope.
Omit to keep current regulatory scope unchanged.

regulatoryScope
tags
object

Free-form tags for categorization. Useful for custom classification and filtering.
Full replacement strategy: provide complete map to replace current tags.
Omit to keep current tags unchanged.

externalRefs
object

References to external systems: CMDB, Jira, ServiceNow, etc. Enables cross-system correlation.
Full replacement strategy: provide complete map to replace current external references.
Omit to keep current external references unchanged.

Response

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
*/*