Zone members

Zone members decide which users can manage a zone. A zone has one Owner — the user who created it — and any number of Administrators the Owner adds. See DNS hosting.

interface ZoneMember {
  zone_id: string;
  user_id: string;
  email: string;
  role: 'Owner' | 'Administrator';
  created_at: number;
  updated_at: number;
}

List members

GET /api/v1/zone-members

Query zone_id (required). Needs access to the zone.

curl -H "Authorization: Bearer $DINIO_API_KEY" \
  "https://api-dinio.bitelex.com/api/v1/zone-members?zone_id=$ZONE_ID"

Add an Administrator

POST /api/v1/zone-members

Owner only. The new member is always an Administrator.

Field	Type
zone_id	uuid
email	string	The email of the user’s Dinio account; case doesn’t matter.

curl -X POST -H "Authorization: Bearer $DINIO_API_KEY" -H "Content-Type: application/json" \
  -d '{"zone_id":"'$ZONE_ID'","email":"ana@example.com"}' \
  https://api-dinio.bitelex.com/api/v1/zone-members

Returns 202 with no data, whether the user was added, already was a member (their role stays as it is) or no account has that email — the answer never reveals which emails are registered. There are no invitations: an unknown email is ignored. List the members to see the result. 422 for a malformed email.

Remove a member

DELETE /api/v1/zone-members/:zone_id/:user_id

Owner only. The Owner cannot be removed. user_id is the member’s user_id from List members.

curl -X DELETE -H "Authorization: Bearer $DINIO_API_KEY" \
  https://api-dinio.bitelex.com/api/v1/zone-members/$ZONE_ID/$USER_ID