When to use this endpoint
UsePOST /external/events/fit-score when your UI needs to answer a focused question: “Is this event a good fit for the current profile?”
It works best after an event has already been selected from search, profile recommendations, or a saved shortlist. If you need to rank multiple candidates, use Events rank. If you need a full recommendation page from profile inputs, use Apply profile and get recommended events.
Endpoint
POST /external/events/fit-score
Authentication
See AuthenticationSuccess status code
201 Created
Request body
| Name | Required | Type | Notes |
|---|---|---|---|
event_id | Yes | string | Event identifier. |
Request example
Response example
Response fields
| Field | Description |
|---|---|
event | Compact event object for the scored event. |
score | Numeric compatibility score for the authenticated caller’s current profile context. |
recommendation | Human-readable recommendation category. |
breakdown.profile_match | Profile-context compatibility component. |
breakdown.matched_exhibitor_density | Signal based on relevant exhibitor overlap or density. |
breakdown.event_scale | Signal based on event size and scale. |
Interpretation guidance
- Use
scorefor display and ordering, but avoid treating small differences as exact truth. - Use
recommendationas the primary user-facing label. - Use
breakdownto explain why an event is strong or weak when your UI has space for detail.
Error responses
400 Bad Request401 Unauthorized404 Not Found409 Conflict429 Too Many Requests
Notes
- This endpoint uses
POSTbecause the request body can contain structured profile context that does not fit cleanly in query parameters. It does not create a persistent resource. - The current implementation returns
event,score,recommendation, andbreakdownonly. - Older draft fields such as
breakdown_detailsare not part of the live response.