Closed MutatedGamer closed 2 years ago
This looks good. I'm going to skip the createApiKey endpoint for now thought. Azure has an API manager resource that can manage that for us. I'll have the rest in a PR in a few minutes.
@MutatedGamer What are your thoughts on this revision? I'm leaving out information about API keys and authorization for now.
Endpoint | Method |
---|---|
/organizations | GET, POST |
/organizations/{orgId} | GET |
/organizations/{orgId}/members | GET, POST |
/organizations/{orgId}/members/{memberId} | GET, DELETE |
/organizations/{orgId}/members/{memberId}/raceresults | GET, POST |
/races | GET |
/races/{raceId} | GET, POST |
We also need /organizations/{orgId}/raceResults that we can query with dates.
Also, we need some kind of endpoint for verifying results. Perhaps: POST /organizations/{orgId}/members/{memberId}/raceresults/{resultId} which returns a {verificationGuid}
Then we'd have a /organizations/{orgId}/{verificationGuid} that can be GET or POSTed. For GET, it'd return the info for that entey. For POST, it'd verify (or not) the result
Don't forget we need a way to PATCH members probably
Here are backend endpoints I think we will need