A LigdiCash API project groups together your authentication keys, the operators activated on your account, and your integration settings (callback URL, return URL, etc.).Documentation Index
Fetch the complete documentation index at: https://developers.ligdicash.com/llms.txt
Use this file to discover all available pages before exploring further.
What an API project contains
| Element | Description |
|---|---|
Apikey | Key that identifies your project in every request |
API_TOKEN | Bearer token that authenticates your requests |
| Activated operators | Mobile money and/or Visa operators defined in your contract |
callback_url | URL where LigdiCash sends payment notifications |
return_url / cancel_url | Redirect URLs after payment (hosted payin) |
Retrieving your keys
Once your project is activated by the technical team, log in to your LigdiCash dashboard:Apikey and API_TOKEN keys are available in the API project management section.
How to use your keys
All your requests to the LigdiCash API must include these two keys in HTTP headers:Integration account vs production account
During the integration phase, the technical team provides you with a temporary account with a pre-activated API project. This account is used for your integration work and your tests. When going live, you create your own LigdiCash account via the mobile app (App Store / Play Store) and the technical team activates your production project on it. Only your keys change — the code, endpoints, and request structure remain identical. See Environments for process details.Modifying the project configuration
For any change to your production API project (adding an operator, changing the callback URL, etc.), contact the technical team via the Microsoft Teams group dedicated to your integration.Related pages
- Integration protocol — how to obtain your API project
- Authentication — using Apikey and API_TOKEN in your requests
- Environments — temporary account vs production account
