Associate GOFA assessments with customers in your own application.
referenceId is your identifier for the customer or business record associated
with an Inquiry. GOFA returns it with the task so you can reconcile activity with
your own system.
| Identifier | Assigned by | Use |
|---|---|---|
referenceId | Your backend | Associate multiple assessments with the same customer. |
Inquiry id | GOFA | Retrieve one assessment and its result. |
sessionId | GOFA | Identify one access session for that assessment. |
Idempotency-Key | Your backend | Retry one creation request without creating duplicates. |
For example, use member_7f32a or a random identifier mapped to your internal user
record. You do not need to send the customer's name, email, phone number, or identity
document number. Avoid using these as reference values.
The field is optional. When supplied, it must contain 1–128 characters after trimming. The same value may be used for multiple Inquiries and across both services. GOFA does not enforce its uniqueness or create a customer account from it.
Derive the value on your backend after authenticating the customer. Do not trust
an arbitrary referenceId supplied by browser code as proof of identity.
Save an association such as:
Your customer: member_7f32a
→ Inquiry A: AI Nutrition
→ Inquiry B: Vital ScanYour backend must check this association before returning any Inquiry or health
result to a customer. The API key authorizes the enterprise, not a particular
ordinary user. referenceId is a correlation field, not an access-control token.
Use customer filters in the enterprise Platform for operational review. For your
customer-facing history, use your own saved Inquiry IDs. The public list endpoint
currently accepts status and pagination parameters only; it does not filter by
referenceId.