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

LinkSquares Agreements API

Analyze agreements and document import/upload (confirmed).

LinkSquares Agreements API is one of 6 APIs that LinkSquares publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Agreements. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

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

5 operations 4 paths 5 schemas 3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://api.linksquares.com/api/analyze
Authentication
API Key
Resource Areas
1

Authentication & Security 1

LinkSquares Agreements API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (apiKeyAuth). By default, every request must be authenticated.

  • apiKeyAuth — LinkSquares API key passed as an x-api-key header on every request. Keys are self-managed by Administrator users and are shared across the Analyze and Finalize…

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 3 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Agreements 5

Analyze agreements and document import/upload (confirmed).

GET
/api/analyze/v1/agreements
List agreements
listAgreements 3 params → 200401429
POST
/api/analyze/v1/agreements
Create an agreement (step 1 of import)
createAgreement body → 200401429
GET
/api/analyze/v1/agreements/{agreement_id}
Retrieve a single agreement
getAgreement 1 param → 200401404
PATCH
/api/analyze/v2/agreements/{agreement_id}
Update an agreement
updateAgreement 1 param body → 200401404
GET
/api/analyze/v1/uploads/{upload_id}
Retrieve upload status
getUpload 1 param → 200401404

Schemas 5

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

AgreementCreateInput
object
5 properties 2 required
AgreementList
object
2 properties
Error
object
2 properties
AgreementUpload
object
2 properties
Agreement
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

linksquares-agreements-api-openapi.yml Raw ↑

Other APIs LinkSquares publishes across the network.

LinkSquares User and Group Provisioning (SCIM)
LinkSquares Account API
LinkSquares Attachments API
LinkSquares Finalize API
LinkSquares Metadata and Smart Values API
Where this information came from

This is an independent, third-party profile of LinkSquares Agreements 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.