Account settings

Endpoint

PATCH /v1/accounts/me

Example

$ curl -X PATCH https://api.replicant.space/v1/accounts/me \
    -H "Authorization: Bearer $API_KEY" \
    -H "Content-Type: application/json" \
    -d '{
      "name": "Bob",
      "email": "bob@example.com",
      "timezone": "Europe/London",
      "replicant_cooperation": "shared",
      "message_notify": {
        "email": false,
        "webhook": true,
        "preferences": {
          "email": {
            "ami": true,
            "devices": true,
            "location_events": true,
            "mining": true,
            "multiplayer": true,
            "printing": true,
            "progression": true,
            "scanning": true,
            "trade": true,
            "travel": true,
            "hub": true
          },
          "webhook": {
            "ami": true,
            "devices": true,
            "location_events": true,
            "mining": true,
            "multiplayer": true,
            "printing": true,
            "progression": true,
            "scanning": true,
            "trade": true,
            "travel": true,
            "hub": true
          }
        }
      },
      "bobnet_channels": ["#general","#trade"]
    }'

Fields

• name - display name on your account.
• email - the email address associated with your account. Changing this will invoke a verification process.
• timezone - IANA timezone for any time-of-day formatting in emails and notifications.
• replicant_cooperation - controls how your replicants share devices. "individual" (default) means each replicant controls its own devices, with optional per-replicant overrides. "shared" means all your replicants can freely operate on each other's devices.
• message_notify.email - receive notifications over email - master override.
• message_notify.webhook - receive webhook notifications - master override.
• message_notify.preferences - per-category toggles for what you want to be notified about.
• bobnet_channels - BobNet channels to subscribe to.

Note that BobNet messages can only be sent via webhook notifications currently.

Replicant cooperation

The replicant_cooperation field controls whether your replicants can operate on each other's devices — stowing, AMI adoption, attaching, device lists, and more. See Replicants & Accounts for the full explanation of how the two-tier permission model works.

$ curl -X PATCH https://api.replicant.space/v1/accounts/me \
    -H "Authorization: Bearer $API_KEY" \
    -H "Content-Type: application/json" \
    -d '{"replicant_cooperation": "shared"}'

{
  "replicant_cooperation": "shared",
  "name": "Bob",
  "email": "bob@example.com",
  ...
}

When set to "shared", every replicant under your account can see and command every sibling's devices. When set to "individual", each replicant's cohort_permission (set via PATCH /v1/replicants/<code>) determines whether siblings can access its devices — "public" allows access, "private" denies it.