The Bila API employs a robust and secure authentication process to ensure that your interactions with our services are protected. Here’s a breakdown of how authentication works and what you need to get started.

​
Authentication Components

Access Token

This is the primary token used to authenticate your requests to the API.

Client Key

A unique identifier provided to you upon registration.

Client Secret

A confidential key that works in tandem with your client key to authenticate your requests.

These credentials are issued immediately after you sign up for an account on the Bila website. The signup process is user-friendly and can be completed with just a few clicks, ensuring that you can quickly begin integrating with the API.

​
Secure Protocols

To further enhance the security of our API, Bila utilizes industry-standard protocols:

{
  "Authorization": "Bearer YOUR_JWT_TOKEN",
  "x-client-key": "YOUR_CLIENT_KEY",
  "x-client-secret": "YOUR_CLIENT_SECRET"
}
  • JWT Tokens (JSON Web Tokens): Our API uses JWT tokens for secure, stateless authentication. These tokens ensure that your sessions are secure and that your authentication data is tamper-proof.
  • OpenID Connect: We leverage OpenID Connect, an identity layer on top of the OAuth 2.0 protocol, to authenticate users securely. This provides a seamless and secure way to verify the identity of the API users, ensuring that only authorized users can access the services.

​
Token-Based Access

Upon obtaining your client key and secret, you will generate an access token that is used to authenticate each API request. The access token must be included in the Authorization header of your API calls. The token typically has a limited lifespan and will need to be refreshed periodically to maintain secure access.

​
Easy Setup and Integration

The entire process of obtaining and using these credentials is designed to be straightforward. After signing up and receiving your credentials, integrating with the Bila API is as simple as configuring your API client with the appropriate headers and tokens.

​
Additional Security Measures

  • Token Expiry and Renewal: Access tokens have an expiration time to ensure that even if a token is compromised, it cannot be used indefinitely. You can easily renew tokens through the API to maintain continuous access.
  • Scope-Based Access: The Bila API allows you to limit the scope of your access, ensuring that your tokens only grant the necessary permissions for your use case.
  • Audit Logs: We maintain comprehensive logs of all API accesses to help you track usage and monitor any unusual activity, enhancing overall security.

​
Conclusion

The Bila API authentication process is built with both ease of use and security in mind. By using JWT tokens and OpenID Connect, we ensure that your interactions with our API are protected by cutting-edge security measures. Whether you are a new user or an experienced developer, our straightforward setup process and robust security protocols allow you to integrate with confidence.