For regulatory authorities

Sending us your notices

If your authority publishes a recall, a suspension or a safety alert, we would rather record it from you than find it later. Three ways to send one are open now. None of them needs an account, and the one that takes least effort is the one we recommend.

What this is not, yet. The Authority Channel described elsewhere on this site — a portal where your named officers publish directly, with no review step, at Tier 0 — is not built. Nothing on the register carries Tier 0 and no authority has been given one. Building it means deciding who here is accountable for what appears, and that decision is not made. We would rather say so than let you find out by trying.

Three ways in

open now

Email it to notices@drugeyeafrica.org

The whole of what is required. Attach the notice, or paste it. We read nothing about the medicine out of the message itself — a person reads the document you sent — and that document is archived as evidence whatever we conclude.

Send the export your system already produces

A CSV, however your database writes it. We map your column headings onto ours rather than asking you to rename them, and a heading we do not recognise stops the import rather than being guessed at.

POST /api/v1/submissions

If your system can send them itself. It needs a key, which names your organisation — ask at notices@drugeyeafrica.org. The data page carries the field list and the exact shapes.

All three end in the same place: a person reading what you sent against the notice, before anything appears. There is no route that skips that step, which is the honest description of what we can offer until the portal exists.

What happens to what you send

It is recorded as coming from you. A notice you confirm to us directly is Tier 2 — confirmed by the authority, not published by them — and the record says so on its face, with who confirmed it and when. It is not recorded as Tier 1, which means you published it on your own channel and we captured it there.

The document is kept. Whatever you attach is stored, hashed and cited by the record as its evidence — up to 4 MB through the API, and any size by email. Regulator links rot, and several in this register already point at third-party hosts; our copy will still be there.

A correction is a correction, never a deletion. If a record here is wrong, tell us and it is superseded: the URL keeps working, the previous state is kept, and the change appears in the public corrections log. We do not quietly remove things, our own mistakes included.

If we cannot use it, you are told why. A submission we set aside keeps its record of having arrived and states the reason. An authority that sent us something and heard nothing back is a failure on our side, not a queue working normally.

Already publishing?

Then the most useful thing you can send is not a notice at all — it is the address of the page where you publish them. We capture from it directly, every notice after this one as well as this one, and those records carry Tier 1: published by you, captured by us, source archived.

Our coverage matrix says what we reach for every African Union member state and where we are blind. If your country’s row is wrong, that is worth an email on its own.

Authorities we do not fetch

Some regulators’ sites ask automated clients not to read them, and we do not. NAFDAC, MCAZ, ARP and AMMPS are not requested at all — by rule rather than by circumstance, and no workaround is built. If you are one of them, a cooperation agreement is the route in, and we would welcome the conversation.

What we will not do

Publish an allegation, a press report or an inference as a record
Build a manufacturer’s profile from anything but published decisions
Alter, translate or tidy your notice text — it is stored verbatim
Delete a record, including at the request of the party named in it

Write to us

notices@drugeyeafrica.org — a notice, a correction, a channel address, or a key.

We would rather answer a question than have you guess at what we do with what you send.