[2025] Public API route

[pcraig3]

Summary

The endgoal for a public API endpoint is to be able to offer NOFO data to downstream consumers.

Since NOFOs are public once they are published on grants.gov, we should be able to offer the NOFO data publicly as an alternate format to PDF to people or organizations who are interested.

We would need to think on this a bit, as sometimes published NOFOs are updated after publishing and we would want to make sure our content is kept current, and not offer different versions of the same NOFO depending on where you are getting it.

However, the general ID is that we would offer a public GET route to "get a NOFO by ID".

This would be limited to "published" NOFOS, and would therefore exclude archived NOFOs or drafts, etc.

We should also remove personal information or internal metadata which we produce: things like "coach", "designer", "status", which help us manage a NOFO through to publication but are not needed by grant applicants.

If we are talking about publishing a NOFO to SimplerGrants or passing it to another system, we would want to have some kind of authentication set up, which could be a bearer token or it could be something else.

This issue does not need to be actioned until we have a compelling use case or consumer for this data.