Locked-in knowledge
The useful moments in a video never reach your CMS, your data warehouse or your workflows.
Developers · API
Video GEO API: from source video to articles and exports.
Submit a video, retrieve the analyses and prepared articles, get notified by webhook, then export to your systems. Every output stays linked to its source moment. Your team approves before anything is published.
See integration scenarios Paths, parameters and fields: only the public documentation is authoritative.
Last verified · 26 September 2026
What does the Aive video GEO API do?
The video GEO API lets you plug the Aive pipeline into your systems: video submission, enabled analyses, draft articles, webhook notifications and exports. It is described by a public OpenAPI 3.1.0 specification; the published specification documents 48 endpoints. Access is an Enterprise API on quote, with scopes, limits and support defined in the contract.
- API key
- A secret identifier that authenticates your system. Keep it server-side, never in a browser.
- Scope
- The set of operations a key is allowed to perform. Grant only what the integration needs.
- Export
- A structured output your system retrieves for publishing, archiving or analysis.
The operational problem
Video stays outside your systems.
Manual copy and paste
Transcribing, clipping and rewriting by hand opens gaps between the source and what gets published.
Lost traceability
Without a link to the source moment, nobody can check where a published statement came from.
How it works
Inputs, processing, outputs.
01You send
- A video or its reference
- Its context: language, owner, rights
- The scopes granted to your key
02Aive processes
- Analyses enabled by your contract
- Structuring of moments and sources
- Draft article preparation
- Status notifications by webhook
03You retrieve
- Analyses linked to moments
- Articles awaiting approval
- Exports for your systems
- Entries in the log
Quickstart
Six steps, in this order.
This path is conceptual. Exact endpoint paths, parameters and field names are given only in the public documentation.
- 01Get Enterprise accessThe Aive team scopes the use case, scopes, limits and support with you. These are set in the contract.
- 02Create a key with its scopesGenerate a key limited to the operations you need. Keep it in a server-side secrets vault and plan for rotation.
- 03Submit a videoSend the video or its reference with its context. Rights and content ownership remain your responsibility.
- 04Retrieve analyses and articlesRead the analyses available under your contract and the prepared articles. An article stays a draft until a person approves it.
- 05Receive a webhookYour system is notified of a status change. Check the notification is authentic before processing it.
- 06ExportPull the structured outputs into your CMS, data warehouse or analytics tools.
Exact reference
For every step, the public documentation at api.aive.tech gives paths, parameters, fields, response codes and cURL examples.
- Redocly documentation
- OpenAPI 3.1.0 specification
- cURL examples
Access and governance
Scopes, limits, logging: defined, not assumed.
Scopes
Each key carries a set of scopes. A read key cannot publish; an export key cannot submit.
Limits
Rate limits, quotas and volumes are defined in the contract. This site publishes no values.
Logging
Operations are logged for audit and troubleshooting, according to your workspace settings.
Before you start
What is documented, what is controlled.
What is documented
- Public OpenAPI 3.1.0 specification
- Key-based authentication and scopes
- Pipeline from video to analyses, articles and exports
- Webhooks and cURL examples
Controls
- Keys restricted by scope
- Human approval before publishing
- Operations log
- Every output linked to its source moment
Prerequisites and availability
- Enterprise API on quote
- Scopes, limits and support defined in the contract
- Analyses available per contract
- Rights to the videos you submit
What the API does not promise.
- This page describes no endpoint path, parameter or field: the public documentation is authoritative.
- No rate-limit, quota or turnaround values are published here; they are defined in the contract.
- A generated article is neither published nor verified by default: generation ≠ publishing ≠ truth.
- The API structures and exports content; it promises no citation, ranking or traffic.
- Availability of a test environment is to be confirmed in the contract.
Frequently asked questions
Questions about the video GEO API.
Where do I find exact paths and parameters?
In the public documentation at api.aive.tech, generated from the OpenAPI 3.1.0 specification. This page describes the journey; it does not replace the reference.
How many endpoints does the specification document?
The published specification documents 48 endpoints. The figure is rechecked whenever the specification changes, and the specification remains the source of truth.
Are retrieved articles published automatically?
No. Articles are prepared as drafts and point to their source moments. Publishing to an enabled destination requires approval by your team.
Which limits apply to my integration?
Rate limits, quotas, volumes and support level are defined in your Enterprise contract. They are not published on this site.
Ready to integrate? Let’s scope your access.
Use case, scopes, limits and support: the Aive team prepares the contractual scope with you.