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

Ampersand Destination API

The Destination API from Ampersand — 6 operation(s) for destination.

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

Tagged areas include Destination. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, and authentication docs.

This API exposes 12 operations across 6 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

12 operations 6 paths 5 schemas 3 DELETE4 GET2 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.withampersand.com
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Ampersand Destination API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Api-Key (APIKeyHeader). It accepts HTTP bearer tokens (JWT) (Bearer). By default, every request must be authenticated.

Paths & Operations 12

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

Destination 12
POST
/projects/{projectIdOrName}/destinations
Ampersand Create a New Destination
createDestination 1 param body → 201400422default
GET
/projects/{projectIdOrName}/destinations
Ampersand List Destinations
listDestinations 1 param → 200default
GET
/projects/{projectIdOrName}/destinations/{destination}
Ampersand Get a Destination
getDestination 4 params → 404200default
PATCH
/projects/{projectIdOrName}/destinations/{destination}
Ampersand Update a Destination
updateDestination 2 params body → 404400422200default
DELETE
/projects/{projectIdOrName}/destinations/{destination}
Ampersand Delete a Destination
deleteDestination 2 params → 204default
POST
/projects/{projectIdOrName}/topics
Ampersand Create a Topic
createTopic 1 param body → 201400422409default
GET
/projects/{projectIdOrName}/topics
Ampersand List Topics
listTopics 1 param → 200default
PATCH
/projects/{projectIdOrName}/topics/{topicId}
Ampersand Update a Topic
updateTopic 2 params body → 200404422400409default
DELETE
/projects/{projectIdOrName}/topics/{topicId}
Ampersand Delete a Topic
deleteTopic 2 params → 204404default
POST
/projects/{projectIdOrName}/topic-destination-routes
Ampersand Create a Topic Destination Route
createTopicDestinationRoute 1 param body → 201400404422default
GET
/projects/{projectIdOrName}/topic-destination-routes
Ampersand List Topic Destination Routes
listTopicDestinationRoutes 3 params → 200default
DELETE
/projects/{projectIdOrName}/topic-destination-routes/{routeId}
Ampersand Delete a Topic Destination Route
deleteTopicDestinationRoute 2 params → 204404default

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are DestinationWithSecrets (7 properties), Destination (6 properties), Topic (5 properties), TopicDestinationRoute (5 properties). Each schema is shown below with its type and property counts.

Destination
object
6 properties 5 required
TopicDestinationRoute
object
5 properties 5 required
DestinationWithSecrets
object
Destination object with secrets field (returned by getDestination when includeSecrets is true)
7 properties 5 required
Topic
object
5 properties 4 required
WebhookHeaders
objectnull
Additional headers to add when Ampersand sends a webhook message

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ampersand-destination-api-openapi.yml Raw ↑

Other APIs Ampersand publishes across the network.

Ampersand API Key API
Ampersand Billing Account API
Ampersand Connection API
Ampersand Installation API
Ampersand Integration API
Ampersand JWT Key API
Ampersand Notification API
Ampersand OAuth API
Ampersand Objects & Fields API
Ampersand Operation API
Ampersand Org API
Ampersand Project API
Where this information came from

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