How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Agave Link Sessions API

Agave Link session management for user authentication.

Agave Link Sessions API is one of 11 APIs that Agave publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Link Sessions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 1 operation across 1 path, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.agaveapi.com.

1 operations 1 paths 3 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.agaveapi.com
Authentication
API Key, API Key, API Key
Resource Areas
1

Authentication & Security 3

Agave Link Sessions API declares 3 security schemes for authenticating requests. An API key is passed in the header as Client-Id (ClientId). An API key is passed in the header as Client-Secret (ClientSecret). An API key is passed in the header as Account-Token (AccountToken). By default, every request must be authenticated.

  • ClientId — Your Agave Client Identifier, always a 36-character UUID. Source https://docs.agaveapi.com/agave-api/headers
  • ClientSecret — Your Agave Client Secret, a 40-character string. Source https://docs.agaveapi.com/agave-api/headers
  • AccountToken — The unique Account Token associated with the linked User account. Not used on Link Token requests. Source https://docs.agaveapi.com/agave-api/headers

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Link Sessions 1

Agave Link session management for user authentication.

POST
/link-sessions
Agave Create Link Session
createLinkSession body → 201400

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are LinkSession (3 properties), Error (3 properties), LinkSessionRequest (2 properties). Each schema is shown below with its type and property counts.

Error
object
API error response.
3 properties
LinkSessionRequest
object
Request payload for creating an Agave Link session.
2 properties 1 required
LinkSession
object
An Agave Link session token.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

agave-link-sessions-api-openapi.yml Raw ↑

Other APIs Agave publishes across the network.

Agave Link Component
Agave File Manager Component
Agave Budgets API
Agave Contracts API
Agave Cost Codes API
Agave Employees API
Agave Invoices API
Agave Projects API
Agave Timesheets API
Agave Vendors API
Where this information came from

This is an independent, third-party profile of Agave Link Sessions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.