Upsert an application's resources and permissions
Replaces the application’s access structure by upserting its resources and their permissions in a single call.
Authorizations
Bearer token authentication. Pass your AccessOwl API token in the Authorization header as Bearer <token>.
Headers
Optional key (1–255 chars) for safely retrying a request. Reusing the same key for the same request returns 409 Conflict and is not processed again — this confirms the request was already received. Keys are retained for 14 days.
1 - 255Path Parameters
Body
Update structure parameters
Upsert resources and permissions for an application. This is a partial upsert, not a full overwrite: omitted items are left untouched. To remove an item, send it with its id and delete: true (this applies to both resources and their nested permissions).
Response
Application
An application in the organization
Application ID
Application status
ignored, discovered, approved, requestable Application title
User IDs of the application's admins
Authentication method used to sign in
google, microsoft, okta, sso_provider, credentials, other Where the vendor stores data
Description
Creation timestamp
Date of the last vendor security review
Whether MFA is activated for this application
Internal notes
Owner user ID
Types of data this application processes
customer_metadata, customer_pii, company_metadata, company_sensitive_data, employee_pii, employee_sensitive_data, ephi Provisioning type
application_admin, automatic Risk level assessment
low, medium, high Tags assigned to this application
Last update timestamp
Application URL
Number of users with access
URL where existing users are shown and new users are invited
Security/compliance certifications held by the vendor
iso_22301, iso_27001, iso_27017, iso_27701, iso_31000, iso_42001, soc1, soc2_t1, soc2_t2, soc3, pci_dss, nist_csf, fed_ramp, hipaa, hitrust_csf, gdpr, csa_star, fsd_safe 
