Your first API call
Get a token, call /me, then list your members — in under five minutes.
1. Get API access
Your institution's admin turns on the Connector module and creates an API client in Zung under Connector → API. Staff tokens carry that staff user's permissions and branch access, so create a dedicated API user with only the permissions your integration needs.
2. Send the token
Every Banking API request sends the token as a bearer header:
Authorization: Bearer YOUR_TOKEN
Accept: application/json3. Check who you are
curl https://app.zung.ai/connector/api/banking/me \
-H "Authorization: Bearer $ZUNG_TOKEN" -H "Accept: application/json"4. List members
curl "https://app.zung.ai/connector/api/banking/members?q=njeri&per_page=10" \
-H "Authorization: Bearer $ZUNG_TOKEN" -H "Accept: application/json"List endpoints return data plus a meta block with current_page, last_page, per_page (max 100) and total.
Errors
- 401 — missing or expired token.
- 403 — the API user lacks the permission, or the record is in a branch they can't see.
- 422 — validation failed;
messagesays why. - 429 — rate limit (600 requests a minute per token).
Something unclear or out of date? Tell us and we'll fix it.