Peptide basics
What people actually report to the FDA about semaglutide
On this page
Anyone can query FDA's adverse event database. For reports filed under the name semaglutide, the most-reported terms are nausea, vomiting and diarrhoea.
These are counts of reports, not counts of people harmed. Nobody verifies that the drug caused the event before the report is stored.
There is no denominator. The database does not know how many people took the drug, so a count cannot be turned into a percentage or a risk.
The counts also rise when prescribing rises and when a drug is in the news. A bigger number can mean more attention rather than more harm.
This page reports what one public query returns and what that return can and cannot support. It does not say semaglutide is safe, does not say it is dangerous, and does not tell you what to do about any symptom — that requires someone who can examine you.
The query, stated in full
FDA's Adverse Event Reporting System is exposed through a free, keyless API. The single request behind this page asks for every report naming SEMAGLUTIDE as a product and counts the reported reaction terms: search=patient.drug.medicinalproduct:"SEMAGLUTIDE" with count=patient.reaction.reactionmeddrapt.exact. The extract we read was dated 28 April 2026 and returned 6,618 reports in total under that name.13
The top of that ranked list, in the same extract, was NAUSEA 943, VOMITING 835, DIARRHOEA 589, OFF LABEL USE 426 and FATIGUE 396 — and every one of those numbers is a count of reports mentioning the term, not a count of people, not a count of confirmed events, and not a share of anything.1
- NAUSEA 943 reports mentioning the term — not 943 verified cases.
- VOMITING 835 reports mentioning the term.
- DIARRHOEA 589 reports mentioning the term.
- OFF LABEL USE 426 reports mentioning the term, which describes how a product was used rather than what happened to anyone.
- FATIGUE 396 reports mentioning the term.1
One report can carry several reaction terms, so these counts overlap and do not sum to the number of reports. That is a property of the data structure, not an error in the query.3
Why this is not a rate
A rate needs two numbers: how many events, and how many people were exposed. FAERS supplies neither reliably. It holds reports that someone chose to submit, and it holds no record at all of how many people took the drug and had nothing to report. FDA states the consequence plainly on the dashboard's own limitations page: the information in these reports cannot be used to estimate the incidence of the events reported.2
The same page lists three further limitations before that one: duplicate and incomplete reports are in the system, the existence of a report does not establish causation, and the information in reports has not been medically verified. FDA also states that the data by themselves are not an indicator of a product's safety profile. Those are the publisher's words about its own dataset, not an outside critique of it.2
This is why 943 nausea reports for semaglutide cannot be compared with, say, 220 for a different product and read as a fourfold difference in nausea. The two products have different numbers of users, different indications, different reporting histories and different manufacturers' reporting obligations. The counts are not measured on a shared scale.29
Why causality is not established
A report records that someone experienced something while taking a product. It does not record that the product caused it, and no reviewer confirms causation before the report is stored and published. FDA's own limitations note says that for any given report there is no certainty a suspected drug caused the event, and that the event may relate to the underlying disease, to another drug taken at the same time, or to something else entirely.2
The reports also arrive from mixed sources. In the same extract, reports naming semaglutide were filed by other health professionals (1,974), consumers or non-health professionals (1,922), physicians (1,624), pharmacists (1,034) and lawyers (9) — categories that differ in how they establish what happened, and none of which constitutes an adjudicated diagnosis.1
In the same extract, semaglutide appeared as a suspect product in 6,519 drug entries and as a concomitant product in 3,792 — meaning a large block of these reports concern people who were taking something else as well, with the reaction attributed elsewhere or nowhere.1
Why the counts move for reasons that are not risk
Under-reporting is the normal state of spontaneous surveillance. Hazell and Shakir pooled 37 studies from 12 countries and calculated a median under-reporting rate of 94% (interquartile range 82–98%) — that is, most adverse reactions detected by intensive data collection never reached the spontaneous reporting scheme at all. For studies of specific serious drug–event pairs the median was still 85%.5
That gap is not a fixed multiplier that can be applied to a count to recover the true number. Its size varies by setting, by seriousness and by drug, and it is unknown for any particular product, which is precisely why a count cannot be scaled up into an estimate.5
Reporting also has a shape over time. Hoffman and colleagues examined 62 drugs approved between 2006 and 2010 and found that the classic pattern of reports peaking in the first years after launch does not hold consistently in modern FAERS data: the common shape was a rise over the first three quarters and then a broadly constant count. Either way, the curve is a curve of reporting behaviour.6
And the name you query changes the answer more than anything about the drug does. In the same extract, the generic term SEMAGLUTIDE returned 6,618 reports while OZEMPIC alone returned 57,104 — the same molecule, filed under a different product string. A count is a count of a name, not of a substance.17
What the counts are actually good for
FAERS is built as a signal generator, not a measuring instrument. Its designed purpose is to surface events worth investigating with a study that has a denominator — a rare event nobody expected, a cluster that arrived faster than prescribing did. FDA describes the system in exactly those terms.2
It is also a record of what people chose to report, which is a legitimate object of interest in its own right. That OFF LABEL USE ranks fourth in the semaglutide extract says something about how this product entered the population; it says nothing about anyone's physiology.1
Where a rate does exist
The approved labelling is the place where denominators are published. The prescribing information for semaglutide in weight management tabulates adverse reactions against a placebo column with the number of participants in each — a structure FAERS does not have and cannot be made to have.8
Common questions
Does 943 nausea reports mean semaglutide causes nausea in 943 people?
No. It means 943 reports in that extract mentioned the term nausea. Nobody verified that the drug caused it, one report can list several terms, and the database holds no count of how many people took the drug without reporting anything.
Can I compare two drugs by comparing their FAERS counts?
Not meaningfully. The counts depend on how many people take each product, how long it has been marketed, how much attention it has had, and which product name a report was filed under. None of those are held constant between two queries.
Why do brand-name and generic-name queries disagree so much?
Because the field being searched is the product name written on the report. Reports filed as OZEMPIC and reports filed as SEMAGLUTIDE are separate strings, and querying one returns nothing from the other.
Should a symptom I am having be reported here?
Reporting is open to anyone through FDA's MedWatch programme, and that is a decision for you. What to do about a symptom is a separate question, and it requires someone who can examine you.
Sources
- RegulatoryopenFDA drug adverse event endpoint — query: search=patient.drug.medicinalproduct:"SEMAGLUTIDE"&count=patient.reaction.reactionmeddrapt.exactU.S. Food and Drug Administration, openFDA, 2026api.fda.gov/drug/event.json?search=patient.drug.medicinalproduct ↗↩ Back to text
- RegulatoryFDA Adverse Event Monitoring System (AEMS) Public Dashboard [formerly FAERS] — limitations to the dataU.S. Food and Drug Administration, 2026www.fda.gov/drugs/questions-and-answers-fdas-adverse-event-repor ↗↩ Back to text
- RegulatoryopenFDA: Drug Adverse Event API reference and data caveatsU.S. Food and Drug Administration, openFDA, 2026open.fda.gov/apis/drug/event/ ↗↩ Back to text
- RegulatoryopenFDA: FAERS data — provenance and disclaimerU.S. Food and Drug Administration, openFDA, 2026open.fda.gov/data/faers/ ↗↩ Back to text
- Secondary sourceUnder-reporting of adverse drug reactions: a systematic reviewHazell L, Shakir SAW. Drug Safety, 2006 · doi:10.2165/00002018-200629050-00003 · PMID 16689555doi.org/10.2165/00002018-200629050-00003 ↗↩ Back to text
- Secondary sourceThe Weber effect and the United States Food and Drug Administration's Adverse Event Reporting System (FAERS): analysis of sixty-two drugs approved from 2006 to 2010Hoffman KB, Dimbil M, Erdman CB, Tatonetti NP, Overstreet BM. Drug Safety, 2014 · doi:10.1007/s40264-014-0150-2 · PMID 24643967doi.org/10.1007/s40264-014-0150-2 ↗↩ Back to text
- RegulatoryopenFDA drug adverse event endpoint — query: search=patient.drug.medicinalproduct:"OZEMPIC"&limit=1 (report total from meta.results.total)U.S. Food and Drug Administration, openFDA, 2026api.fda.gov/drug/event.json?search=patient.drug.medicinalproduct ↗↩ Back to text
- Product labelWEGOVY (semaglutide) injection — FDA-approved prescribing informationU.S. Food and Drug Administration (DailyMed SPL), 2024dailymed.nlm.nih.gov/dailymed/drugInfo.cfm?setid=f5e548d0-cc79-4 ↗↩ Back to text
- Regulatory21 CFR 314.80 — Postmarketing reporting of adverse drug experiencesU.S. Government Publishing Office, Electronic Code of Federal Regulations, 2026www.ecfr.gov/current/title-21/chapter-I/subchapter-D/part-314/su ↗↩ Back to text