33 docs tagged with "agsync"

Relevant swagger documentation on these APIs can be found below.

Relevant swagger documentation on these APIs can be found below.

<BlockImageView

Below are commonly asked questions related to the AgSync API.

The platform offers numerous API calls to access different types of data, such as:

AgSync leverages an implementation of the OpenID Connect specification. OpenID Connect is an identity layer on top of the OAuth 2.0 Protocol. See OpenID Connect Documentation for more information about the specification.

This flow is used when the client does not want to create their own login page, but still wants refresh token ability. It is recommended to use this flow as the user only has to login once and the refresh token can be used to retrieve access tokens going forward.

Relevant swagger documentation on these APIs can be found below.

Represents a customer that is created, changed, or deleted.

Third-party integrations partners will need to request developer accounts. After these requests have been approved, partners will receive developer credentials. At that point they can begin development.

The table below defines common error codes encountered in AgSync responses.

Represents a farm that is created, changed, or deleted.

Represents a field that is created, changed, or deleted.

With AgSync, users can place orders with a streamlined interface or through one of Raven's API partners. Effectively manage application logistics by dispatching fields to the appropriate applicators. Stay informed with real time work order status notifications via text or email. Keep up to date with the live location of scouts, ground crews and applicators.

Guides to getting started with AgSync API.

The table below contains AgSync-related terms. Their abbreviations and definitions are also listed.

The AgSync platform has specific Request and Response headers.

The platform mainly uses the following HTTP methods:

This flow is a combination of the implicit flow and authorization code flow. It is used when the client does not want to create their own login page, but still wants refresh token ability. It is recommended to use this flow because the user only has to login once and then the refresh token can be used to retrieve access tokens going forward.

This implicit grant flow can be used by both web-based and native applications.

Integration partners are a reserved item used for adding the ability to store a set of partner data within AgSync.

Represents a order that is created, changed, or deleted.

Relevant swagger documentation on these APIs can be found below.

Pagination is supported on a handful of API endpoints.

If one already has a refresh token and the access token has expired, one will need to get another access token using the refresh token. Call the token endpoint specified in the discovery document and pass the grant type and the token. Doing so will get a new access token.

Documentation explaining security features and practices relevant to AgSync API.

There are two primary ways to send a work order:

A list of scopes is available at the discovery endpoints listed in Authentication. Further descriptions of AgSync specific supported scopes are listed below:

Third-party integrations partners will need to request testing accounts. After these requests have been approved, partners will receive tester credentials. At that point they can begin testing.

When information is being exported from AgSync there are a few different methodologies. If using webhooks alone, one can convert data to another without requiring any user interaction with AgSync to authenticate with AgSync.

Guides to some operations and subjects related to AgSync API.

Webhooks allow one to build or set up integrations which subscribe to certain events at agsync.com. When one of those events is triggered, AgSync will send a HTTP POST payload to the webhook's configured URL. Webhooks can be used to update an external system, trigger custom notifications, or journal events with the order.

Represents a zone that is created, changed, or deleted.