> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spenza.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Support

> How to reach Spenza API support and what to include for a fast resolution.

## How to get help

Email **[support@spenza.com](mailto:support@spenza.com)** for API support — account provisioning, credential issues, questions about a specific endpoint's behavior, or anything this documentation doesn't answer (including the gaps called out throughout — webhook payload schemas, sandbox access, and specific rate-limit thresholds, for example).

Check **[status.spenza.com](https://status.spenza.com)** first if you suspect an outage or degraded service rather than a bug in your own integration.

For general product/account questions unrelated to the API itself, use your existing Spenza account representative if you have one.

<Note>
  **More support channels are being decided.** A community forum or chat support for the Partner API aren't set up yet. Until that's settled, treat `support@spenza.com` as the reliable default.
</Note>

## What to include when you report an issue

The faster you can give this, the faster it's actionable:

* **What you were trying to do** — the endpoint (method + path) and a summary of the goal, not just "it's broken."
* **The exact request** — method, full path, headers (**redact your bearer token and any secrets**), and body. Copying the cURL sample from the reference page and adjusting it is often the clearest way to share this.
* **The exact response** — status code and full response body, especially `error.code` and `error.message`.
* **A timestamp** (with timezone/UTC offset) and, if relevant, your account/partner identifier — this lets Spenza correlate your report against server-side logs.
* **For async operations** — the `transactionId`, not just the call that created it. That's the fastest way to look up what actually happened server-side.
* **Whether it's reproducible** — a one-off blip vs. a consistent failure point you can trigger on demand changes how it gets triaged.

<Warning>
  **Never include credentials in a support request.** Redact your API secret, bearer tokens, and any webhook `authentication` credentials before sharing a request. If you believe a credential was exposed, say so explicitly and ask for rotation — see **[Security & Best Practices → Secret rotation](/security#secret-rotation)** — rather than pasting the value itself for reference.
</Warning>

## Before you reach out

Many issues are answered faster by checking these first:

* **[Errors](/errors)** — the full error-code taxonomy and what each one means.
* **[FAQ & Troubleshooting](/faq)** — common setup, auth, and payload issues.
* **API Reference** (sidebar) — the exact field/parameter contract for the endpoint you're calling.