Authentication
Every business endpoint in Credit Core requires the Authorization header, validated by a TOKEN Authorizer at the API Gateway. Webhooks (bank/collector callbacks) and internal events (EventBridge/SNS) are the only exceptions.
Required header
Authorization: <token>
The value is the token issued by Migo. The authorizer rejects any request without a valid token before it reaches the service.
Endpoints under v2/credits/webhooks/... that receive bank, collector or EventBridge callbacks do not go through the TOKEN Authorizer. See Webhooks and notifications.
Universal response format
All responses share the same envelope.
Success — HTTP 200:
{
"success": true,
"data": {}
}
Error:
{
"success": false,
"error": {
"code": "6010",
"name": "<catalog name>",
"description": "<catalog description>",
"message": "Missing user data"
},
"data": {}
}
code/name/descriptioncome from the error catalog (MongoDB).messageis the specific detail added by the service.- The HTTP status is set by the service (
400/401/403/404/409/500).
The full code catalog and the retry strategy are in Error catalog.
Try it in the browser
The Credit Core interactive reference renders every endpoint with Scalar. Set the Authorization header once and every authenticated endpoint reuses it.