EntryWick developers

The sandbox

An organization of invented people, rebuilt every night. Its key is published on purpose and reaches nothing real: it is a ewk_test_ key, and everything it scans is kept out of every count, report and export.

There is nothing to sign up for. Copy the key and make a call.

Your key

ewk_test_2b5dd27ca40bc017f68eebcd1b783e74a70ea6fc

Base URL https://api.staging.entrywick.com/v1. Send it as Authorization: Bearer … — the key names the organization, so there is none in the address. It is rotated when the sandbox is refreshed, so read it from here rather than hard-coding it.

What is in it right now

Read from the sandbox itself, so these are values you can paste into a call today.

Event
EntryWick Sandbox Day (published)
Event id
01m6t3613spnr0egvca40h0xbr
Day codes
DAY1, DAY2
Attendee type codes
ADT, YTH, CHP, STF, STL
Check-in point codes
PRE-IB, Z-TALENT, Z-SPLASH, Z-REG, Z-FOOD, PRE-QR, PRE-PC, PRE-OB, PRE-NG, PRE-MH, PRE-LM, PRE-KP, PRE-JB, GATE1, PRE-HW, PRE-HQ, PRE-GH, PRE-FG, PRE-EB, PRE-DM, PRE-CF, PRE-BC, PRE-AW, HELP, GATE2
People registered
40
A ticket
DAY1-0040-3783
A registration reference
01m6t36bf4hvq8kepx7gcqkrjk

A call that works right now

Paste this into a terminal. Nothing is substituted — the key and the id are the live ones above.

curl -s "https://api.staging.entrywick.com/v1/events/01m6t3613spnr0egvca40h0xbr" \
  -H "Authorization: Bearer ewk_test_2b5dd27ca40bc017f68eebcd1b783e74a70ea6fc"

And registering somebody — a write, so it needs an idempotency key:

curl -s -X POST "https://api.staging.entrywick.com/v1/events/01m6t3613spnr0egvca40h0xbr/registrations" \
  -H "Authorization: Bearer ewk_test_2b5dd27ca40bc017f68eebcd1b783e74a70ea6fc" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"attendees":[{"attendee_type":"ADT","first_name":"Amina","last_name":"Rahim","email":"amina@example.org","days":["DAY1"]}]}'

What it is not