Turnout REST API: every request from Part 14, as curl commands
===============================================================

For your own ORDS server. apex.oracle.com sits behind a content network that
blocks command-line tools (curl hangs or gets a 403 page); there, use
part14_try_it.sql in SQL Commands instead. The public GETs also work in a
browser's address bar.

Replace these before you paste:
  BASE           your schema's base URL from Lesson 14.2, for example
                 https://your-server/ords/turnout
  CLIENT_ID      from part14_oauth_client.sql
  CLIENT_SECRET  from part14_oauth_client.sql
  ACCESS_TOKEN   from step 3 (it lasts an hour)
  EVENT_ID       select id from to_events where slug = 'tuesday-track-intervals';
  TICKET_CODE    the checkin_token from the Lesson 7.12 query

On Windows Command Prompt, use double quotes instead of single quotes, and
write the JSON body as "{\"ticket\":\"TICKET_CODE\"}".


1. Public: upcoming events, 25 a page (Lesson 14.3)

curl BASE/turnout/v1/events/


2. Public: one event, by its slugs (Lesson 14.4)

curl BASE/turnout/v1/events/tampa-runners/saturday-long-run


3. Get a token with client credentials (Lesson 14.5)

curl -i -u 'CLIENT_ID:CLIENT_SECRET' -d 'grant_type=client_credentials' BASE/oauth/token


4. Organizer: RSVPs, without a token (expect 401), then with one

curl -i BASE/turnout/v1/organizer/events/EVENT_ID/rsvps

curl -H 'Authorization: Bearer ACCESS_TOKEN' BASE/turnout/v1/organizer/events/EVENT_ID/rsvps


5. Organizer: check a ticket in (expect 200, then 400 the second time)

curl -i -H 'Authorization: Bearer ACCESS_TOKEN' -H 'Content-Type: application/json' -d '{"ticket":"TICKET_CODE"}' BASE/turnout/v1/organizer/events/EVENT_ID/check-in


6. The OpenAPI description (Lesson 14.6)

curl BASE/open-api-catalog/turnout/v1/