Updated

Padre API: What Exists and What Does Not

Short answer: Padre publishes no public API. There is no endpoint reference, no authentication scheme and no rate limit documented anywhere — and the subdomain people expect to find one on does not exist.

Checks showing Padre publishes no public API: api.padre.gg does not resolve and the documentation site redirects to the app, while automation exists inside the product
Four checks, and the automation that does exist instead.

What we checked, and what came back

CheckResult (18 Sep 2026)
api.padre.ggDoes not resolve — no host answers
docs.padre.ggRedirects to the application at trade.padre.gg
padre.gg marketing siteDoes not use the word API at all
Published endpoint referenceNone found from Padre or Pump.fun

The documentation that did exist covered trading, Trenches, rewards and the referral program — never an interface for machines. When the product was renamed Terminal after the Pump.fun acquisition, that documentation went offline entirely; the background is on the rebrand page.

Pages that advertise a Padre API

Searches for this term surface a site that imitates Padre's branding and advertises a blog post about "Padre API endpoints, authentication and integration". Nothing in it can be checked against anything Padre publishes. The useful instinct here is the same one that protects you from clone domains: if a third party offers you credentials or an integration for a product whose own operator documents neither, the risk sits entirely with you. Which address is genuinely the app is on the trade.padre.gg page.

What you can automate without an API

Most people searching for this want unattended execution rather than a REST client. The terminal already does that part in the interface:

None of that needs a key, and nothing leaves your browser. Setting the automation up is seven steps on the setup guide, and what each layer of a trade costs is on the fees page.

If you genuinely need programmatic access

Then the terminal is the wrong layer to ask. Orders on Padre end up as ordinary transactions against DEX liquidity on Solana, Ethereum, Base or BNB Chain, so anything a bot would do can be done directly against those chains with an RPC endpoint and a DEX aggregator — with the honest caveat that you are then writing and securing the execution logic yourself, which is most of what a terminal exists to spare you.

For what the product does have rather than what it lacks, see the Padre bot overview.

Padre API — questions

Does Padre have a public API?

No documented one. api.padre.gg does not resolve, the documentation site now redirects to the application, and Padre publishes no endpoints, authentication scheme or rate limits anywhere we can find — checked 18 September 2026.

What about pages advertising "Padre API endpoints and authentication"?

At least one site that copies Padre branding advertises exactly that. Nothing it describes can be verified against anything Padre publishes. Treat API credentials handed out by a third party as a way to lose a wallet, not as a feature.

Can I automate trades on Padre without an API?

Inside the terminal, yes: limit orders, buy-dip orders, take-profit and stop-loss levels that fire on their own, and copy trading. That covers most of what people want an API for, without keys leaving your machine.

Can I export my Padre trade history programmatically?

Padre does not document an export endpoint. Your on-chain history belongs to your wallet address, so a block explorer or a Dune query against that address gives you the same trades without needing anything from Padre.

Will there be a Padre API later?

Nothing is announced. The product was acquired by Pump.fun and renamed Terminal, and the public documentation went offline during that transition, so treat any API roadmap claim as unsourced until Padre publishes it.

Checks run 18 September 2026 against api.padre.gg, docs.padre.gg and padre.gg. We update this page if Padre publishes an API.