Leaf connects to Raven Slingshot using API key credentials. Once connected, Leaf ingests machine files from Slingshot for the Leaf user. This is separate from Raven, which uses OAuth 2.0 credentials for grower, farm, and field data.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
- A Raven Slingshot portal account.
- Your
apiKey,accessKey, andsharedSecretfrom the Slingshot portal.
Credentials schema
| Field | Type | Required | Description |
|---|---|---|---|
apiKey | string | Yes | Your Slingshot API key. |
accessKey | string | Yes | Your Slingshot access key. |
sharedSecret | string | Yes | Your Slingshot shared secret. |
Endpoints
| Method | Path | Description |
|---|---|---|
| GET | /users/{leafUserId}/raven-slingshot-credentials | Get stored credentials. |
| POST | /users/{leafUserId}/raven-slingshot-credentials | Create credentials. |
| DELETE | /users/{leafUserId}/raven-slingshot-credentials | Delete credentials. |
| GET | /users/{leafUserId}/raven-slingshot-credentials/events | Get credential events for troubleshooting. |
https://api.withleaf.io/services/usermanagement/api
Create credentials
Response
Troubleshooting
Use the events endpoint to check credential health. Events are retained for 30 days and are deleted when the credential is removed.What to do next
- Raven for OAuth-based grower, farm, and field data.
- API Reference: Providers for the full credential path matrix.

