Resource Missing (not_found)
Quick Fix & Resolution
Verify the identifier (account G-address, 64-hex transaction hash, ledger sequence, or operation ID) and confirm the resource exists on Stellar Pubnet.
Response Payload & SDK Handling
json
{
"type": "https://orion.stellarchain.io/horizon-errors/not_found",
"title": "Resource Missing",
"status": 404,
"detail": "The resource at the url requested was not found. This usually occurs for one of two reasons: The url requested is not valid, or no data in our database could be found with the parameters provided."
}typescript
import { Horizon } from '@stellar/stellar-sdk';
const server = new Horizon.Server('https://pubnet.stellarchain.io');
try {
const res = await server.ledgers().limit(10).call();
} catch (err: any) {
const problem = err?.response?.data;
if (problem?.type === 'https://orion.stellarchain.io/horizon-errors/not_found') {
console.error('[not_found] HTTP 404:', problem.detail, problem.extras);
}
}go
client := &horizonclient.Client{
HorizonURL: "https://pubnet.stellarchain.io",
}
_, err := client.Root()
if hErr := horizonclient.GetError(err); hErr != nil {
if hErr.Problem.Status == 404 {
log.Printf("Problem (%s): %s - extras=%v", hErr.Problem.Type, hErr.Problem.Detail, hErr.Problem.Extras)
}
}bash
curl -i -s "https://pubnet.stellarchain.io/" \
-H "Accept: application/hal+json"Common Root Causes
- Querying an account (
GET /accounts/{id}) that has not been funded on-chain or was merged. - Querying a transaction hash (
GET /transactions/{hash}) that was never included in a ledger. - Querying a ledger sequence higher than
history_latest_ledgeror0. - Requesting a URL path that does not exist.