API request examples using cURL

These examples show how to consume the Verify APIs by using the cURL tool to send HTTP requests to access, create, and manipulate the API resources.

OAuth access token
Your application needs an OAuth access token to call the target API. The access token verifies that your application is authorized to access the requested resource. Use the client ID and client secret to exchange an access token at the token endpoint.
Configuring and managing API Clients
If a developer builds an application that uses one or more of the Security Verify functions, the application must be entitled to call the appropriate Security Verify APIs. Register the in-house application as an API client in API access to assign it a unique client ID and secret.
Managing users in the API client
To use the external APIs to manage users, follow the prerequisites and use Client for URLs (cURL) to get or send the API requests.
Using Time-based One-time Password (TOTP) in the API client
To use a time-based one-time password (TOTP) as the authentication method for your application (API client), follow the prerequisites and use Client for URLs (cURL) to get or send the API requests.
Managing IBM Verify registrations and authentication factor enrollments
To configure IBM Verify authenticator options, initiate and manage registrations and initiate and manage runtime authentication verification transactions, you need an API client with specific API access entitlements. You also need an access token that is derived from this client.
Verifying usernames and passwords
Verify supports a set of runtime API endpoints to enable consumers to validate a username and its password against an identity source.

Parent topic: Verify Application programming interfaces (APIs)