Summary
We're finalizing the migration from Private Applications to Private Resources for customers using client-based ZTNA. If your organization has been migrated to support client-based ZTNA, the legacy Private Applications and Private Application Groups API endpoints will now return HTTP 410 (Gone) responses, aligning the API behavior with what you've already been seeing in the Dashboard.
Before
Private Applications were the original method for configuring secure access to internal resources. Customers used these API endpoints to manage their applications and application groups:
Legacy Private Applications Endpoints: https://developer.cisco.com/meraki/api-v1/create-organization-secure-connect-private-application/
Legacy Private Application Groups Endpoints: https://developer.cisco.com/meraki/api-v1/create-organization-secure-connect-private-application-group/
For customers migrated to client-based ZTNA, the Dashboard has been showing a warning message indicating that Private Applications have been migrated to Private Resources. However, the API endpoints continued to function during the transition period.
Today
For customers migrated to support client-based ZTNA:
The Private Applications and Private Application Groups API endpoints will now return HTTP 410 (Gone) when called. This status code indicates that the resource has been permanently removed and you should migrate to the replacement API.
Note: For client-based ZTNA migrated organizations, any Private Applications or Private Application Groups created through the legacy endpoints would not be used by the upgraded services, therefore these endpoints now return 410 errors to prevent unintentional misconfiguration.
Example Error Response:
When calling Private Applications or Private Applications groups endpoints, you'll receive:
json
{
"errors": [
"This endpoint has been deprecated and is no longer available."
],
"message": "Private applications have been migrated to Private Resources. Please use the Private Resources API endpoints instead.",
"documentation": "https://developer.cisco.com/meraki/api-v1/create-organization-secure-connect-private-resource/"
}
Who is affected: - Organizations that have been migrated to support client-based ZTNA - If you've been seeing deprecation warnings in the Dashboard for Private Applications, this applies to you
Who is NOT affected: - Organizations still using the Private Applications system who have not been migrated for client-based ZTNA will continue to have access to these endpoints until their migration is completed
Migration Path
Use Private Resources instead of Private Applications:
Private Resources provide enhanced functionality and support for client-based ZTNA. Your existing Private Applications have already been migrated to Private Resources in the Dashboard, and are available via private resource endpoints documented below.
New API Endpoints:
Private Resources: https://developer.cisco.com/meraki/api-v1/get-organization-secure-connect-private-resources/
Private Resource Groups: https://developer.cisco.com/meraki/api-v1/get-organization-secure-connect-private-resource-groups/
Action Required
If you're using the legacy Private Applications API endpoints and have been migrated to client-based ZTNA:
1. Update your API integrations to use the new Private Resources endpoints 2. Test your integrations to ensure they work with the new API structure 3. Handle HTTP 410 responses gracefully in your error handling code
If you have questions or need assistance with the migration, please reach out to Secure Connect support.
... View more
