Support

Contact

Email support@403fin.io.

Include the request id

Every API response carries an X-Request-Id header (also requestId in error bodies):

X-Request-Id: req_01J9Z3A8B2C3D4E5F6G7H8J9K0

Quote it. Because we never log message bodies, that id is how we locate your request's metadata — status, timing, warning codes — in our systems.

What to include

1. The X-Request-Id (or several, if the issue spans requests)
2. The endpoint and rough timestamp (with timezone)
3. What you expected vs what happened
4. The error type slug if you got one (e.g. unsupported-conversion)

Never email an API key or a real financial message. If a key may be exposed, rotate it first, then tell us the key name. If reproducing the issue needs a message, strip or synthesize the data — we can work from structure.

Requests that go through support today

• IP allowlist setup and changes
• OAuth client provisioning
• usage:read scope grants (Scopes)
• SDK distribution access (Go, TypeScript, Python)
• New format or conversion-pair requests