Register event visitors with zero credentials

You host a conference in Próspera, run a coworking space, or operate a travel platform, and you want attendees to request their Próspera visitor pass directly from your own registration flow.

Credential: none. POST visitor_pass_applications is the one unauthenticated endpoint in the API — a deliberate zero-friction entry point.

The flow

Collect the visitor's details in your form, then submit them:

curl -s -X POST https://portal.eprospera.com/api/v1/visitor_pass_applications \
  -H "Content-Type: application/json" \
  -d '{
    "firstName": "Jane",
    "lastName": "Doe",
    "email": "jane@example.com",
    "signature": "<signature string>",
    "consentToBackgroundCheck": true,
    "referralSource": "Acme Conference 2026"
  }'

The applicant receives follow-up steps by email; your platform's job ends at submission. Use referralSource to identify your event or venue — it's how arrivals get attributed to you.

Pair it with verification

If your venue also gates access for existing residents, combine this with RPN verification using a standard API key: visitors go through the pass flow, residents get verified in one call.

What this API does not do

• No status polling for visitor passes — the applicant is contacted by email; there is no read-back endpoint.
• No bulk submission; one application per visitor.

Next steps

• POST visitor_pass_applications — full request schema
• Getting started — if you outgrow the no-auth surface