Error Codes
The API returns structured errors with acode and message. This page documents the error codes you may receive when calling Create Guarantee (POST /guarantees) and how to resolve them.
Create Guarantee (POST /guarantees)
These codes are returned in the response body with HTTP status 400 when a guarantee cannot be created due to validation or business rules.| Code | Message |
|---|---|
| GUA_06 | This credit reference has already been used. Use a new one so we can process this guarantee. |
| GUA_08 | Premium percentage is out of range |
| GUA_15 | Disbursement date is invalid: it is before the license creation month or outside the allowed range. |
| GUA_16 | Disbursement date is invalid: it is before the previous month or after today. |
| GUA_27 | The total loan amount associated with guarantees exceeds the Portfolio Coverage Cap allowed by the license. Please adjust it to continue creating the guarantee. |
| GUA_28 | The credit coverage exceeds the maximum amount allowed by the license. Please adjust it to complete the guarantee creation. |
| GUA_29 | Invalid loan amount for this license. Modify it so it falls within the allowed range |
| GUA_30 | Invalid loan durations |
| GUA_37 | It is not possible to calculate the guarantee premium. Check the data and try again |
| GE_01 | Bad Request |
Cause and resolution
GUA_06 — Duplicate external reference
What happened: TheexternalReference you sent is already associated with an existing guarantee for this license.
What to do: Use a unique value for externalReference per guarantee (e.g. your internal credit or loan ID). Do not reuse the same reference across different guarantee creation requests.
GUA_08 — Premium percentage out of range
What happened: ThepremiumPercentage in the request is outside the min/max range defined in the License configuration.
What to do: Check your License terms for the allowed premium percentage range. Ensure the value you send is within that range (inclusive).
GUA_15 — Disbursement date before license creation month or outside range
What happened: ThedisbursementDate is earlier than the month in which the License was created, or it falls outside the period allowed by the License.
What to do: Set disbursementDate to a date within the valid window defined by the License (on or after the license creation month and within any configured range).
GUA_16 — Disbursement date before previous month or after today
What happened: ThedisbursementDate is either before the previous calendar month or after the current date.
What to do: Use a disbursement date that is within the previous month or the current month (not in the future and not older than the previous month).
GUA_27 — Portfolio / coverage cap exceeded (SURETY)
What happened: For a SURETY-type license, the sum ofloanAmount already associated with existing guarantees plus the loanAmount of the new guarantee would exceed the Portfolio Coverage Cap allowed by the License.
What to do: Reduce the loanAmount of this guarantee, or wait until other guarantees free up cap (e.g. closed or novated). You can also contact your Anzi representative if you need to adjust the license cap.
GUA_28 — Coverage exceeds maximum allowed
What happened: The coverage amount for this guarantee (derived from loan amount and coverage rules) exceeds the maximum per-guarantee coverage allowed by the License. What to do: Lower the loan amount or the effective coverage so it stays within the license’s maximum coverage per guarantee.GUA_29 — Invalid loan amount
What happened: TheloanAmount does not comply with the License configuration (e.g. below minimum, above maximum, or not allowed by product rules).
What to do: Check the License’s min/max loan amount and product rules. Send a loanAmount within the allowed range and that matches the license terms.
GUA_30 — Invalid loan durations
What happened: The combination of dates or terms (e.g.disbursementDate, paymentTerm, or implied loan duration) is not allowed by the License (e.g. duration too short or too long).
What to do: Ensure disbursementDate and paymentTerm (and any other term-related fields) result in a loan duration that is within the License’s allowed range.
GUA_37 — Cannot calculate guarantee premium
What happened: The premium could not be calculated, usually because required data for variable premium calculation is missing or invalid (e.g. loan terms, rates, or dates). What to do: Verify that all fields required for premium calculation are present and valid (amounts, dates, terms). For variable premium licenses, ensure interest rate and payment schedule data are correct and consistent.GE_01 — Bad Request (generic)
What happened: The request failed a general validation or business rule that is not mapped to a specific GUA_xx code. What to do: Review the request body against the Create Guarantee schema and the Guarantee Overview. Check required fields, formats (e.g. dates, IDs), and license constraints. If the issue persists, use the exactcode and message when contacting support.