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

Amigo Data Sources API

The Data Sources API from Amigo — 5 operation(s) for data sources.

Amigo Data Sources API is one of 72 APIs that Amigo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Data Sources. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 8 operations across 5 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 5 base URLs: https://api.amigo.ai, https://internal-api.amigo.ai, https://api-eu-central-1.amigo.ai, https://api-ap-southeast-2.amigo.ai, https://api-ca-central-1.amigo.ai.

8 operations 5 paths 14 schemas 1 DELETE4 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.amigo.ai
Authentication
HTTP Bearer, API Key, HTTP Basic
Resource Areas
1

Authentication & Security 3

Amigo Data Sources API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer-Authorization). An API key is passed in the header as X-ORG-ID (Bearer-Authorization-Organization). It accepts HTTP basic authentication (Basic). By default, every request must be authenticated.

  • Bearer-Authorization — Amigo issued JWT token that identifies an user. It's issued either after logging in through the frontend, or manually through the [SignInWithAPIKey](sign-in-wi…
  • Bearer-Authorization-Organization — An optional organization identifier that indicates from which organization the token is issued. This is used in rare cases where the user to authenticate is ma…
  • Basic — The username should be set to {orgid}{userid}, and the password should be the Amigo issued JWT token that identifies the user.

Paths & Operations 8

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

Data Sources 8
POST
/v1/{workspace_id}/data-sources
Create a data source
create-data-source 1 param body → 201401403422
GET
/v1/{workspace_id}/data-sources
List data sources
list-data-sources 6 params → 200401422
GET
/v1/{workspace_id}/data-sources/{data_source_id}
Get a data source
get-data-source 2 params → 200404401422
PATCH
/v1/{workspace_id}/data-sources/{data_source_id}
Update a data source
update-data-source 2 params body → 200404401422
DELETE
/v1/{workspace_id}/data-sources/{data_source_id}
Delete a data source
delete-data-source 2 params → 204404401422
GET
/v1/{workspace_id}/data-sources/{data_source_id}/status
Get data source status
data-source-status 2 params → 200404401422
GET
/v1/{workspace_id}/data-sources/{data_source_id}/sync-history
Get data source sync history
data-source-sync-history 3 params → 200404401422
POST
/v1/{workspace_id}/data-sources/{data_source_id}/sync
Trigger a manual sync for a data source
trigger-data-source-sync 2 params → 202400404409429503401422

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are DataSourceResponse (18 properties), DataSourceStatusResponse (10 properties), CreateDataSourceRequest (8 properties), UpdateDataSourceRequest (7 properties). Each schema is shown below with its type and property counts.

TriggerSyncResponse
object
3 properties 3 required
CreateDataSourceRequest
object
8 properties 2 required
NameString
string
DataSourceSyncHistoryResponse
object
4 properties 4 required
HTTPValidationError
object
1 property
TriggerSyncConflictResponse
object
Body shape for the 409 returned by POST /sync when the source is already mid-poll. Documented in OpenAPI so SDK consumers get a typed AlreadySyncing error inst…
2 properties 2 required
SyncHistoryEntry
object
4 properties 4 required
DataSourceStatusResponse
object
10 properties 10 required
UpdateDataSourceRequest
object
7 properties
ValidationError
object
5 properties 3 required
TriggerSyncConflictDetails
object
Operational fields included in a 409 to power UI affordances like "syncing for 30s" — strict allowlist, never the whole status entry.
2 properties
DataSourceResponse
object
18 properties 18 required
PaginatedResponse_DataSourceResponse_
object
4 properties 2 required
SyncFailureEntry
object
6 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

amigo-data-sources-api-openapi.yml Raw ↑

Other APIs Amigo publishes across the network.

Amigo Account API
Amigo Admin API
Amigo Agent Definitions API
Amigo Agent Runs API
Amigo Agents API
Amigo Analytics API
Amigo API Keys API
Amigo Audit API
Amigo Auth API
Amigo Billing API
Amigo Calls API
Amigo Command Center API
Where this information came from

This is an independent, third-party profile of Amigo Data Sources 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.