API reference / Partner
post
/v2/teamInvite a colleague
- Operation
inviteTeamMember- Authentication
- API key
Adds a portal user for this tenant. **No password is set and no key is issued** — the invited person signs in with a single-use email link, which is the only credential the account will ever hold.
Request
Body
emailstringrequiredResponses
201Invited.
userPartnerUserrequired400The request body or query failed validation.
errorobjectrequired401No key, an unknown key, a revoked key, or a key whose tenant is not active. All four return an identical body on purpose: distinguishing them would let a caller discover which partners we have.
errorobjectrequired403The key is valid but lacks the scope, or it asked for a scope it does not itself hold.
errorobjectrequired404Not found, or not yours. A resource belonging to another tenant answers 404 rather than 403, because 403 would confirm the record exists.
errorobjectrequiredExample
curl -X POST https://api.haavisa.com/v2/team \
-H "Authorization: Bearer $HAAVISA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"email": "<email>"
}'More in Partner
Something unclear? The eligibility guide explains the model behind the answers; the errors guide covers the envelope.