2025-07
Scheduled for release July 7, 2025

Updates to GET /sdk/integrations and Proxy API

To improve the ergonomics of the API, we are introducing a few changes to the GET /projects/:projectId/sdk/integrations and Proxy API endpoints for Custom Integrations.

We are also removing some unnecessary fields from the response of the GET /projects/:projectId/sdk/integrations endpoint to improve performance. Please review these changes to ensure that your application is not using any of the fields scheduled for removal.

Affected endpoints:

  • GET /projects/:projectId/sdk/integrations
  • Proxy API

Breaking changes:

  • In GET /projects/:projectId/sdk/integrations, the type field of Custom Integrations will now be the full slug that is used in paragon.connect() calls.

  • In GET /projects/:projectId/sdk/integrations, some unnecessary fields are being removed from Integrations:

    • To optimize the performance of this endpoint, some fields of Integrations are being removed. Please ensure that the following fields are not in use by your application:
      • integration.dateCreated
      • integration.dateUpdated
      • integration.resourceId
      • integration.configs[].dateCreated
      • integration.configs[].dateUpdated
      • integration.configs[].integrationId
      • integration.workflows[].dateCreated
      • integration.workflows[].dateUpdated
      • integration.workflows[].teamId
      • integration.workflows[].isOnboardingWorkflow
      • integration.workflows[].workflowVersion
      • integration.customIntegration.oauthScopes
      • integration.customIntegration.oauthIncludeClientAuthorizationHeader
      • integration.customIntegration.usePKCEInCodeExchange
      • integration.customIntegration.apiBaseUrl
      • integration.customIntegration.testEndpointPath
      • integration.customIntegration.isTestEndpointVerified
      • integration.customIntegration.apiAuthorization
      • integration.customIntegration.userProfileConfig

Other non-breaking changes:

  • Proxy API now supports using the custom.name format when sending Proxy requests for Custom Integrations
    • Instead of passing in a customIntegrationId, you will now be able to pass in custom.name (the same slug used for paragon.connect) directly to the Proxy API.

    • Example:

      - https://proxy.useparagon.com/projects/:projectId/sdk/proxy/custom/:customIntegrationId/:path
      + https://proxy.useparagon.com/projects/:projectId/sdk/proxy/custom.integrationName/:path
      
      

What do I need to do?

  • Verify that your use of integrations.type for Custom Integrations does not rely on the value being exactly "custom". The new type field will include the full slug value, e.g. custom.integrationName.
  • Verify that you are not using any of the fields scheduled for removal from the API.

When are these changes being released?

  • These changes will be released on July 7, 2025.