​

internal_error

This is a Scripe-side bug. The request was rejected, but we cannot tell you exactly what went wrong without your request_id because the underlying exception was logged to Sentry, not to the response body (intentional — we don’t leak stack traces or internal field names). To recover:

1. Retry once with backoff. Some internal_error responses are transient (e.g. a single transient DB blip) and succeed on retry.
2. If you see repeated 500s for the same request, capture the request_id and contact support. We’ll match it to the Sentry trace and respond.

Don’t treat 500s as permanent failures in your retry logic — they’re much closer in spirit to 503 than to 4xx codes.