Closed waldoj closed 9 years ago
Thought: Allowing verification of the outcome of past applications is problematic. It requires statefulness (now we need a database), and presents a security exposure. I'm also not sure about its utility for the client, as planned. Seems like this isn't worth it yet.
Methods:
/api/registrars/
lists every registrar by place name and GNIS ID/api/registrars/[GNIS ID]/
lists the record for a single registrar/api/validator/
accepts JSON and validates it against the schema/api/submit/
accepts JSON, validates it against the schema, and stores it/api/bounce/
receives bounce notifications from the transactional email serverThat bounce notifications bit is tricky. We don't want anybody to be able to invalidate any registrar's email address. The simplest method is probably to have a per-site config file with a single API key to be used by the transactional email server, which can be embedded in the webhook URL.
Seems like there's a few basic things that it clearly needs to do:
Also: