Naming the federation that approved your card, and the difference between a claim and a confirmation.
This is the whole idea, so it is worth stating plainly.
You may name the federation that sanctioned your event. BoutHost shows that as your claim — the body's name prefixed with "Organizer claims:", alongside "Sanction not confirmed", in neutral amber.
The federation's mark — the badge, the tick, "Sanctioned by" in green — appears only once the claim has been confirmed. Until then the platform is reporting what you told it, and saying so.
That split is not a hurdle. It is what lets an independent club name the body it applied to without the platform having to vouch for it, and what stops anybody presenting an unapproved card as approved.
The create form asks Is a federation sanctioning this event?, and every event you make by hand needs an answer:
The last two ask which federation, and both are a claim: until it is confirmed, your event page says "Organizer claims" whichever you chose. An event imported from Webpoint is not asked, because its federation comes from Webpoint.
On Manage you can name a federation at any time afterwards — the commonest case is an approval that comes through after the event exists. Naming one replaces a Not sanctioned answer.
You can add the sanction number you were issued, either when you claim or later.
Once a sanction number is on a claim, it is fixed. Completing a claim (you applied, approval came through, you now have the number) and correcting one are different acts — a different number is a different assertion.
To correct one, withdraw the claim and make it again.
Nothing can be added or changed once a claim has been reviewed. Evidence must not move underneath somebody's conclusion.
Automatically, if the event was imported from your federation's system. Every detail came from their own record, addressed by their own event identifier, so the claim is confirmed as the event is created. See importing an event from Webpoint.
By review, otherwise. A BoutHost administrator checks the claim and confirms, rejects or revokes it. For boxing, a sanction number can be looked up against USA Boxing's record — either the full code, or just the event id from the end of it.
Even a matching number is a transcription check, not proof. It confirms the number is real; it does not confirm it belongs to your event. A reviewer compares the title, date and venue too.
Only boxing prints a sanction number, so other federations are confirmed by review without one.
An event with no sanction claim says so, neutrally — whether you chose Not sanctioned or simply have not named a federation. An unsanctioned event is a perfectly legitimate thing to run — this platform exists for independent clubs as much as for federation cards — so nothing about it is styled as a warning.
Confirmed and unconfirmed claims are both public. Rejected and revoked claims are not — a rejection is sometimes a correction of a data-entry mistake, and broadcasting it would be an accusation.
You see all of them, including rejected ones, on your own Manage screen. If a rejection has left your event reading as unsanctioned to the public, that screen tells you.
A confirmed sanction is re-checked against the federation's own record. If their record stops supporting it, the mark comes off the public page and the claim returns to being your claim.
A confirmed claim is also unsettled by material edits — renaming the event, moving its dates or moving its venue. The federation approved a particular card. If the card changes, the evidence no longer describes it.
BoutHost is combat-sports event management — hosts run events, fighters declare the weight they will compete at, and federations confirm the cards they have sanctioned.
© 2026 Webpoint Technologies. All rights reserved.
A Webpoint Product
