Frequently Asked Questions
Find quick answers to common issues and questions regarding the hexCore API integration.
How do I get my API keys?
You can obtain your Sandbox API keys instantly by creating an account on the hexCore Developer Dashboard. Navigate to the 'Settings' tab and look for the 'API Keys' section. Production keys are only issued after successful UAT Sign-off.
Why am I getting a '401 Unauthorized' error?
This error occurs when the 'Authorization' header is missing from your request, or if the Bearer token provided is invalid or expired. Ensure you are passing the token as 'Bearer sk_test_your_secret_key' and that you are hitting the correct environment (sandbox vs production).
Are webhooks supported?
Yes, hexCore relies heavily on webhooks to deliver asynchronous event updates, particularly for interbank transfers, loan approvals, and virtual account funding. You can configure your webhook URLs in the Developer Dashboard.
What is the rate limit for the Sandbox environment?
The Sandbox environment is rate-limited to 50 requests per second (RPS) per IP address to ensure stability. Production rate limits are significantly higher and are customized based on your institution's negotiated SLA.
How can I simulate a failed transfer in Sandbox?
In the Sandbox environment, you can trigger specific error states by passing special strings in your payload. For instance, passing an amount of '9999' or a destination account of '0000000000' will simulate a rejected transfer. Check our comprehensive Sandbox Mocking guide for all trigger values.
Who do I contact for integration support?
Our integration engineers are available 24/7. You can reach out via the 'Support' ticket system in your Developer Dashboard, or email integration@hexcore.io directly. Priority routing is given to institutions currently in the UAT phase.
Still need help?
If you couldn't find the answer to your question, feel free to reach out to our dedicated integration support team.