Shared credentials authorization type (legacy)

❗ Important The shared credentials option described in this topic is deprecated as of December 1, 2020 and is no longer be available for new product integrations. Integrations that were created with shared credentials prior to that date continue to work. For enhanced security, AppDirect recommends that you use the separate credentials type for applications, and that you migrate existing products that use shared credentials to separate credentials. For more information about deprecation, see Product lifecycle phases.

The shared credentials authorization type uses a single OAuth 1.0 consumer key and secret to secure outbound distribution event notifications as well as incoming API requests for your product integration.

The topics in this section describe the shared credentials authorization type in more detail.

• Authorize inbound API requests (legacy)
• Validate outbound event notifications (legacy)
• Sign return URLs
• OAuth API code examples