OpenAPI 3.1.0 specification
The source file behind the documentation. It is authoritative for the endpoint count.
Developers · Changelog
Follow changes at the source.
The API reference evolves with its published specification. This page shows where to follow those changes, how figures on this site are aligned with the specification, and how often they are rechecked.
Last verified · 26 September 2026
Where can I follow changes to the Aive API?
In the public documentation at api.aive.tech, built from the OpenAPI 3.1.0 specification. It is the reference for paths, parameters, fields and the endpoint count. This site keeps no parallel version history: it points to the specification and aligns its own figures with it. As of today, the published specification documents 48 endpoints.
- Source of truth
- The document that prevails in case of discrepancy. For the Aive API: the published OpenAPI specification.
- Reconciliation
- Bringing a figure shown elsewhere back in line with the source of truth.
Where to look
Three references, only one prevails.
Public documentation
Redocly reference generated from the specification: this is where API changes appear.
Visit api.aive.tech
This page
It records changes to the site and its developer pages, not API versions.
Reconciliation rule
One figure, one source.
The endpoint count shown on this site is always the one in the published OpenAPI specification. The approved wording is: “The published specification documents 48 endpoints.” Any other figure, on a page, a sales document or a presentation, is withdrawn until it is reconciled with the specification.
When the specification changes, the update is coordinated: documentation first, then the pages that quote the figure. Every technical statement is recorded in a register with its source, scope, verification date, owner and expiry date.
Approved wording
“The published specification documents 48 endpoints.” Verified on 26 September 2026 against the published OpenAPI specification.
Site log
Recorded changes.
| Date | Change |
|---|---|
| 26 September 2026 | Launch of the Aive GEO V2 site and of this page |
Only changes to the site and its developer pages are recorded here. API changes are visible in the public documentation.
Review cadence
How statements stay current.
- Every technical statement carries a verification date and an owner
- An expiry of 90 or 180 days is set according to sensitivity
- On expiry, the statement is rechecked against its source or withdrawn
- Any change to the specification triggers a review of the pages that quote it
- The last verification date is shown on technical pages
Frequently asked questions
Questions about the changelog.
Why are there no version numbers here?
Because the public documentation is authoritative. Copying versions onto this site would risk discrepancies, so we point to the published specification instead.
I saw a different endpoint count elsewhere. Which one is right?
The one in the OpenAPI specification published at api.aive.tech. As of this page’s verification date, the published specification documents 48 endpoints.
How will I hear about a change that affects my integration?
How Enterprise customers are informed is defined in the contract and goes through Aive support. Check the public documentation regularly as well.