Agvance

Documentation Index

Fetch the complete documentation index at: https://docs.withleaf.io/llms.txt

Use this file to discover all available pages before exploring further.

​

Prerequisites

1. Access to an Agvance instance with API access enabled.
2. Your apiKey from Agvance.
3. The username, password, and databaseId for the target Agvance database.
4. Optional: clientEnvironment if you need to override the default environment.

​

Setup steps

curl -X POST \
    -H 'Authorization: Bearer YOUR_TOKEN' \
    -H 'Content-Type: application/json' \
    -d '{
      "apiKey": "your-api-key",
      "clientEnvironment": "PRODUCTION",
      "databaseId": "target-database-id",
      "password": "your-password",
      "username": "your-username"
    }' \
    'https://api.withleaf.io/services/usermanagement/api/users/{leafUserId}/agvance-credentials'

​

Credentials schema

{
  "id": "uuid",
  "status": "str",
  "createdTime": "yyyy-MM-dd'T'HH:mm:ss.SSSSSS'Z'",
  "clientEnvironment": "PRODUCTION",
  "username": "str",
  "password": "str",
  "databaseId": "str",
  "sessionId": "str",
  "apiKey": "str"
}

​

Confirm the credentials are attached

curl "https://api.withleaf.io/services/usermanagement/api/users/{leafUserId}/agvance-credentials" \
  -H "Authorization: Bearer YOUR_TOKEN"

​

Endpoints

​

Troubleshooting

curl -X GET \
    -H 'Authorization: Bearer YOUR_TOKEN' \
    'https://api.withleaf.io/services/usermanagement/api/users/{leafUserId}/agvance-credentials/events'

• Invalid credentials: If the password changes in Agvance, delete and recreate the credentials with the new password.
• Wrong database ID: Verify the databaseId matches the target Agvance database.
• STAGE vs. PRODUCTION mismatch: If you set clientEnvironment explicitly, make sure it matches the Agvance instance you’re connecting to.

​

What to do next

• Growers for how Agvance grower and farm data appears in Leaf.
• Fields Overview for the synced resource hierarchy.
• Provider Credentials API Reference for the credential path matrix.