management api
Everything the console does, as an API.
Proxies, spec versions, publishing, environments, drift, coverage, alerts, keys and domains - all of it is an operation here, and a command in the CLI. A write action that exists only in a browser is one you cannot perform at 3am.
This page is generated from the server
The operations below are not written about our API. They are read
out of the document our API is served from: /v1 resolves
its operations from it, validates every request against it before a
handler runs, and compiles its bearerAuth scheme into the
check that guards each one. An operation it declares that we have not
implemented is a refusal to start, not a 404 you find.
The document itself is at
/api/openapi.json - point a
generator at it.
Getting a token
Issue one on your account page. It is shown once: we keep only its hash, so a token we could show you twice would be one a database dump could show anyone. It belongs to the account rather than to you, so it keeps working when the person who created it leaves.
export APIP_TOKEN=apip_... curl -H "Authorization: Bearer $APIP_TOKEN" https://openapi-proxy.com/v1/proxies
The operations
Every operation with the schemas it declares.
Send one. The try-it forms post to /v1 on
this site with the token you paste into them - the same request the CLI
would send, against your real account, so a delete deletes.