Authentication Methods

\<font color="#78b5c7">\</font> topic type constraint purpose explain authentication methods used for accertify apis audience api integrators and client developers applies to accertify apis that require authenticated http requests does not apply to internal batch processing or non‑request‑based integrations all api requests must be authenticated using one of the supported authentication methods authentication establishes the identity of the client and ensures that requests are processed under the correct integration context authentication requirements apply uniformly across industries, endpoints, and fraud‑related lifecycle contexts supported authentication methods apis support the following authentication methods basic authentication oauth 2 0 client credentials clients must use one of these methods consistently per integration, as configured during onboarding basic authentication uses credentials issued by and is typically implemented during initial integrations when using basic authentication credentials are provided with each request requests must still comply with all hashing and integrity requirements authentication credentials are tied to the client’s integration configuration (for example, importer id–based configurations where applicable) basic authentication does not alter how events are evaluated; it only establishes authorization and request legitimacy oauth 2 0 using the client credentials grant is supported as an alternative authentication method when using oauth 2 0 clients obtain an access token from the authorization service the access token is included with api requests token acquisition and refresh occur outside the api request flow oauth 2 0 is commonly used when centralized credential management is required short‑lived tokens are preferred over static credentials integration standards require oauth‑based authentication