Leaf Agriculture API Reference > Leaf User > Provider Credentials > Agvance API
The API Reference > Leaf User > Provider Credentials > Agvance API from Leaf Agriculture — 2 operation(s) for api reference > leaf user > provider credentials > agvance.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/leaf-agriculture-api-reference-leaf-user-provider-credentials-agvance-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Leaf Agriculture Leaf API Reference > Alerts API Reference > Leaf User > Provider Credentials > Agvance API
description: We are Leaf Agriculture, provider of a unified farm data API. After experiencing the difficulty of building applications in food and agriculture first hand as software developers, and hearing similar stories of frustration with existing tools and often insurmountable technical barriers from other companies, we decided to tackle the problem at hand.
version: 1.0.0
tags:
- name: API Reference > Leaf User > Provider Credentials > Agvance
paths:
/services/usermanagement/api/users/{leaf_user_id}/agvance-credentials:
get:
tags:
- API Reference > Leaf User > Provider Credentials > Agvance
summary: Leaf Agriculture Get Agvance credentials from Leaf User
parameters:
- name: Authorization
in: header
schema:
type: string
example: Bearer {{leaf_token}}
- name: Content-Type
in: header
schema:
type: string
example: application/json
- name: leaf_user_id
in: path
schema:
type: string
required: true
responses:
'200':
description: Successful response
content:
application/json: {}
post:
tags:
- API Reference > Leaf User > Provider Credentials > Agvance
summary: Leaf Agriculture Add Agvance credentials to a Leaf User
requestBody:
content:
'*/*':
schema:
type: string
example: '"{\n \"apiKey\": \"{{agvance_api_key}}\",\n \"clientEnvironment\": \"STAGE or PRODUCTION\",\n \"databaseId\": \"{{agvance_database_id}}\",\n \"password\": \"{{agvance_password}}\",\n \"username\": \"{{agvance_username}}\"\n}"'
parameters:
- name: Authorization
in: header
schema:
type: string
example: Bearer {{leaf_token}}
- name: Content-Type
in: header
schema:
type: string
example: application/json
- name: leaf_user_id
in: path
schema:
type: string
required: true
responses:
'200':
description: Successful response
content:
application/json: {}
delete:
tags:
- API Reference > Leaf User > Provider Credentials > Agvance
summary: Leaf Agriculture Delete Agvance credentials from a Leaf User
parameters:
- name: Authorization
in: header
schema:
type: string
example: Bearer {{leaf_token}}
- name: Content-Type
in: header
schema:
type: string
example: application/json
- name: leaf_user_id
in: path
schema:
type: string
required: true
responses:
'200':
description: Successful response
content:
application/json: {}
/services/usermanagement/api/users/{leaf_user_id}/agvance-credentials/events:
get:
tags:
- API Reference > Leaf User > Provider Credentials > Agvance
summary: Leaf Agriculture Get Agvance credentials Events
security:
- bearerAuth: []
parameters:
- name: leaf_user_id
in: path
schema:
type: string
required: true
responses:
'200':
description: Successful response
content:
application/json: {}