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 Provider App API

The Provider App API from Ampersand — 2 operation(s) for provider app.

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

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

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

4 operations 2 paths 2 schemas 1 DELETE1 GET1 PATCH1 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 Provider App 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 4

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

Provider App 4
GET
/projects/{projectIdOrName}/provider-apps
Ampersand List Provider Apps
listProviderApps 1 param → 200422default
POST
/projects/{projectIdOrName}/provider-apps
Ampersand Create a New Provider App
createProviderApp 1 param body → 200400422default
DELETE
/projects/{projectIdOrName}/provider-apps/{providerAppId}
Ampersand Delete a Provider App.
deleteProviderApp 2 params → 204422default
PATCH
/projects/{projectIdOrName}/provider-apps/{providerAppId}
Ampersand Update a Provider App
updateProviderApp 2 params body → 200400default

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are ProviderApp (9 properties), ProviderAppMetadata (2 properties). Each schema is shown below with its type and property counts.

ProviderAppMetadata
object
Provider-specific configuration that extends the standard OAuth flow.
2 properties
ProviderApp
object
9 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ampersand-provider-app-api-openapi.yml Raw ↑

Other APIs Ampersand publishes across the network.

Ampersand API Key API
Ampersand Billing Account API
Ampersand Connection API
Ampersand Destination 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
Where this information came from

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