Onboard residents as a relocation partner

You run a relocation service, an immigration consultancy, or a digital-nomad platform, and you onboard clients into Próspera residency on their behalf.

Credential: a Partner Key (pk-), issued by the e-Próspera team to approved organizations — Partner Keys covers issuance, 90-day expiry, security responsibilities, and rate limits. This surface is separate from Agent Keys: it is organization-scoped, not person-delegated.

The flow

1. Create a Draft — POST partner/residency_applications with the applicant's personal details and a unique Idempotency-Key. e-Próspera emails the applicant a single-use account-claim link (24-hour expiry).
2. Complete the data — PATCH partner/residency_applications/{id} with expectedVersion for optimistic concurrency.
3. Attach proof of address — upload the document to get an opaque proofOfAddressUploadId, then attach it via PATCH. (The sworn-statement path skips the upload.)
4. Pay — hosted checkout or voucher, each with its own Idempotency-Key.
5. Hand off to the applicant — the applicant claims their account, signs the Agreement of Coexistence at nextSteps.agreementUrl, and completes identity verification in their own session.
6. Submit and poll — once nextSteps.submitReady is true, call POST …/submit, then poll GET …/{id} until Approved/Rejected.

The full nine-step secure flow — including which fields each scope unlocks and the per-endpoint rate limits — is in Partner Keys.

What this API does not do

• No public webhooks — poll application status (lists support cursor pagination).
• No Veriff initiation or results via Partner Keys.
• Partner Keys expire after 90 days — build rotation into your ops calendar.

Next steps

• Partner Keys — the complete integration contract
• Uploads reference — private document handling
• Conventions — idempotency, errors, pagination