Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
I'm a 300-level Computer Science student at NOUN in Lagos. I have no professional experience in fraud or banking, so this post is me asking for correction from people who do. The problem as I understand it When online fraud happens, the money often moves through several mule accounts and gets cashed out within minutes. Victims usually report hours later.
I recently needed something small: a POST /api/contact endpoint for my portfolio site at https://www.isaiah.name.ng that takes a name, email, and message, validates it, and emails it to me. The kind of thing you'd normally knock out without thinking twice.
• You asked how other people are solving this, so here is where I would press on the design, because generating the spec turns out not to be the hard part. Deriving the docs and the validator from the same schemaOf call removes drift between the doc and the validator. It does not remove drift between either of them and what the handler actually does. Request bodies get parseValidatedBody[T]. Responses get documented and then trusted.
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
