Accounts

Connected accounts allow you to manage multiple customers within your organization. Each account can have its own farms, parcels, and embedded map access.

Account Deletion Behavior

Important: The DELETE endpoint performs a soft delete, which deactivates the account but does not permanently remove it. This means:

• The account email cannot be reused to create a new account

• The account data is preserved and can be reactivated

• You will receive an error if you try to create a new account with the same email

To permanently delete an account:

1. Go to the Graniot App

2. Navigate to Settings > Members

3. Find the deactivated account

4. Click the delete button to permanently remove it

User Roles

Accounts can have different roles that control their permissions in the embedded map:

Role	Can View	Can Edit Geometries	Can Manage
USER	Yes	No	No
TECHNICIAN	Yes	Yes	No
COMPANY_ADMIN	Yes	Yes	Yes

If you want to prevent users from editing parcel geometries in the embedded map, assign them the USER role.

Changing Account Roles

Use the set_role endpoint to change an account's role:

POST /api/accounts/{account_id}/set_role/

Headers:

x-api-key: YOUR_API_KEY

Body:

{"role": "USER"}

or

{"role": "TECHNICIAN"}

The system will verify that licenses are available for the target role before making the change.

---

get

Responses

200Success

application/json

idstringRead-onlyRequired

account_emailstringRequired

embedded_urlstringRead-onlyRequired

account_accessstringRead-onlyRequired

get

/api/accounts/

HTTPcURLJavaScriptPython

GET /api/accounts/ HTTP/1.1
Accept: */*

200Success

[
  {
    "id": "text",
    "account_email": "text",
    "embedded_url": "text",
    "account_access": "text"
  }
]

post

Body

application/jsonapplication/x-www-form-urlencodedmultipart/form-data

idstringRead-onlyRequired

account_emailstringRequired

embedded_urlstringRead-onlyRequired

account_accessstringRead-onlyRequired

Responses

201Success

application/json

post

/api/accounts/

HTTPcURLJavaScriptPython

POST /api/accounts/ HTTP/1.1
Content-Type: application/json
Accept: */*
Content-Length: 24

{
  "account_email": "text"
}

application/jsonapplication/x-www-form-urlencodedmultipart/form-data

201Success

{
  "id": "text",
  "account_email": "text",
  "embedded_url": "text",
  "account_access": "text"
}

put

Update account information. If the request contains embedded_conf, it must be a JSON object with boolean values.

        Allowed keys for `embedded_conf` are:
        - COMPARISON_TAB_VIEW
        - GRAPHS_TAB_VIEW
        - NOTES_TAB_VIEW
        - ZONING_TAB_VIEW
        - WEATHER_FORECAST_TAB_VIEW
        - ADVANCED_TAB_VIEW
        - TREE_ANALYSIS_TAB_VIEW
        - CROPS_TAB_VIEW
        - ACCOUNT_LIMITS (object) - Account-level limits
          - MAX_PARCEL_SIZE (number) - Max parcel size in hectares. Cannot exceed the company limit.

        Example payload:
        {
            "embedded_conf": {
                "COMPARISON_TAB_VIEW": true,
                "ACCOUNT_LIMITS": {
                    "MAX_PARCEL_SIZE": 50
                }
            }
        }

Path parameters

idstringRequired

Body

application/jsonapplication/x-www-form-urlencodedmultipart/form-data

idstringRead-onlyRequired

account_emailstringRequired

embedded_urlstringRead-onlyRequired

account_accessstringRead-onlyRequired

Responses

200Success

application/json

idstringRead-onlyRequired

account_emailstringRequired

embedded_urlstringRead-onlyRequired

account_accessstringRead-onlyRequired

put

/api/accounts/{id}/

HTTPcURLJavaScriptPython

PUT /api/accounts/{id}/ HTTP/1.1
Content-Type: application/json
Accept: */*
Content-Length: 24

{
  "account_email": "text"
}

application/jsonapplication/x-www-form-urlencodedmultipart/form-data

200Success

{
  "id": "text",
  "account_email": "text",
  "embedded_url": "text",
  "account_access": "text"
}

delete

Path parameters

idstringRequired

Responses

204

No response body

delete

/api/accounts/{id}/

HTTPcURLJavaScriptPython

DELETE /api/accounts/{id}/ HTTP/1.1
Accept: */*

204

No response body

No content