To authenticate with the Keka APIs, you'll need an access token. Generating this token requires providing specific details, namely the client_id
, client_secret
, api_key
and scope
to the Identity URL. Additionally, Keka offers a Sandbox Environment, allowing you to conduct integration testing for your applications.
Authentication Details:
To generate the access token, you'll need the following details:
client_id
: Your client identifier for authentication.client_secret
: Your client secret for secure authentication.api_key
: Your unique API key for accessing the system.scope
: You will need to pass kekaapi for this key.
Identity URLs:
For generating the access token, you'll interact with the Identity URLs. Depending on your environment, choose the appropriate URL:
- Production Identity URL: https://login.keka.com/connect/token
- Sandbox Identity URL: https://login.kekademo.com/connect/token
Sandbox Environment:
Keka provides a Sandbox Environment designed for integration testing purposes. This environment allows you to thoroughly test your applications' integration with the Keka APIs, ensuring seamless functionality before moving to production.