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 Webhook Destination API

The Webhook Destination API from Amigo — 4 operation(s) for webhook destination.

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

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

This API exposes 6 operations across 4 paths, and defines 11 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.

6 operations 4 paths 11 schemas 1 DELETE2 GET3 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 Webhook Destination 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 6

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

Webhook Destination 6
POST
/v1/{organization}/webhook_destination/
Create a webhook destination
create-webhook-destination 3 params body → 201422404409400401403503
GET
/v1/{organization}/webhook_destination/
Get webhook destinations
get_webhook_destinations 4 params → 200422404401403503429
POST
/v1/{organization}/webhook_destination/{webhook_destination_id}
Update a webhook destination
update-webhook-destination 4 params body → 204422404409401403503429
DELETE
/v1/{organization}/webhook_destination/{webhook_destination_id}
Delete a webhook destination
delete-webhook-destination 4 params → 204422404409401403503429
POST
/v1/{organization}/webhook_destination/{webhook_destination_id}/rotate-secret
Rotate the secret of a webhook destination
rotate-webhook-destination-secret 4 params → 200422404409400401403503
GET
/v1/{organization}/webhook_destination/{webhook_destination_id}/delivery
Get webhook deliveries
get-webhook-deliveries 11 params → 200404422401403503429

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are WebhookDeliveryInstance (7 properties), WebhookDestination (5 properties), src__app__endpoints__webhook_destination__get_webhook_deliveries__Response (3 properties), src__app__endpoints__webhook_destination__create_webhook_destination__Request (3 properties). Each schema is shown below with its type and property counts.

DeliveryAttempt
object
2 properties 2 required
src__app__endpoints__webhook_destination__update_webhook_destination__Request
object
2 properties
WebhookDestination
object
5 properties 5 required
WebhookType
string
WebhookDeliveryInstance
object
7 properties 7 required
src__app__endpoints__webhook_destination__get_webhook_destinations__Response
object
1 property 1 required
src__app__endpoints__webhook_destination__get_webhook_deliveries__Response
object
3 properties 3 required
WebhookDeliveryStatus
string
src__app__endpoints__webhook_destination__create_webhook_destination__Request
object
3 properties 2 required
src__app__endpoints__webhook_destination__create_webhook_destination__Response
object
2 properties 2 required
src__app__endpoints__webhook_destination__rotate_webhook_destination_secret__Response
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

amigo-webhook-destination-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 Webhook Destination 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.