`not_implemented`

The endpoint exists but the requested capability is not yet available.

HTTP 501Repull does not implement this capability yet.

When it fires

The endpoint exists in the API surface, but the requested capability is not yet wired up. This usually shows up on:

Beta endpoints reserved in the OpenAPI spec ahead of full rollout.
Channel-specific operations that work on Airbnb but are not yet wired for Booking.com (or vice-versa).
Combinations of parameters that are documented as "coming soon".

Response shape

Every Repull error follows the same envelope. The code is stable and safe to switch on.

{
  "error": {
    "code": "not_implemented",
    "message": "<human-readable explanation of what went wrong>",
    "docs_url": "https://repull.dev/docs/errors/not_implemented"
  }
}

How to fix

Check the changelog (https://repull.dev/changelog) — newly-shipped capabilities are flagged there.
For a missing channel operation, try the equivalent on a sibling channel as a workaround.
If you depend on the capability, email hello@repull.dev and we can prioritise it.

Examples

curl

# A real endpoint that is declared but not yet implemented
curl https://api.repull.dev/v1/billing \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# {
#   "error": {
#     "code": "not_implemented",
#     "message": "Billing read endpoint is coming soon. Track availability at https://repull.dev/changelog.",
#     "fix": "Use `POST /v1/billing` to start a checkout for the `starter`, `growth`, or `scale` plans in the meantime.",
#     "docs_url": "https://repull.dev/changelog",
#     "request_id": "req_5105b3a8f842415b9a405017"
#   }
# }

TypeScript

// GET /v1/billing is declared but not implemented yet. The SDK has no method
// for it, so this calls the endpoint directly.
const res = await fetch('https://api.repull.dev/v1/billing', {
  headers: { Authorization: `Bearer ${process.env.REPULL_API_KEY}` },
})

if (res.status === 501) {
  const { error } = await res.json()
  if (error.code === 'not_implemented') {
    // Don't retry — the capability does not exist yet
    return { unavailable: true, message: error.message, fix: error.fix }
  }
}

If you're an AI agent

The capability does not exist yet. Do not retry. Tell the user the feature is not available and offer the closest working alternative from the API Reference.

Error reference — the full table of error codes
Using Repull from AI agents — patterns for handling errors in agent loops

Hit an error that isn't covered? Email hello@repull.dev with the request id from the response headers.

Previous← internal_error

not_implemented