Use these endpoints to attach provider credentials to a Leaf user. The base path is consistent, but the request body and supported helper endpoints vary by provider, so this page is best used as a path matrix rather than a single normalized contract.
For setup requirements and request-body examples, see the provider-specific guides under Connecting Providers.
Base URL
Credential path matrix
Common path shape
The credential endpoints always start with the Leaf user:
Examples:
GET /users/{leafUserId}/john-deere-credentials
POST /users/{leafUserId}/ag-leader-credentials
DELETE /users/{leafUserId}/panorama-credentials
Most providers also expose a credential events endpoint:
Use the provider-specific documentation to confirm the exact request body and any provider-specific fields.
Example: get stored credentials
Events endpoint
Many provider credential endpoints expose /events for troubleshooting authentication failures, token refreshes, and sync-related issues.
When available, these endpoints support:
What to do next
- Use Connecting Providers to choose the right provider flow.
- Use the provider-specific guides for request-body schemas and setup details.
- Use Leaf users to create the Leaf user before attaching credentials.
Last modified on April 13, 2026