Machine-to-machine authentication for SafeSend APIs
Use machine-to-machine (M2M) authentication to authenticate SafeSend API requests securely without user interaction.
SafeSend supports additional authentication options for public-facing APIs, including machine-to-machine (M2M) authentication and OAuth authentication.
All public-facing SafeSend APIs require an access token. Include the access token in the
Authorization
request header to authenticate API requests. About M2M authentication
M2M authentication lets applications, services, and devices securely verify their identities when they exchange data or call APIs. M2M authentication doesn't require a person to sign in or interact with the authentication process.
note
Use M2M authentication for integrations and API processes that don't require user interaction.
Webhooks
The API authentication changes don't affect webhooks. Firms don't need to update webhook settings for webhooks to continue functioning.
Prerequisites
- The firm will need to use a SafeSend product.
- The SafeSend user must have permission to access theDevelopersection.
