Use a structured chat workflow to diagnose an API integration failure with request, response, auth, and retry checks.
The recommended model and prompt are filled in. Choose your own inputs and generation settings.
Preview
Chat Prompt
The audio provider returns 401 only in production.
First split: credentials, environment variables, and provider project scope. Request check: compare auth header shape in draft and production. Provider check: confirm the production key has audio generation enabled. Next step: log redacted request metadata and test a minimal production request.
Output
Objective / context / judgment / risks / recommended actions / missing information
Structured conversation example for API Integration Debug Chat.
API Integration Debug Chat: diagnose an API integration failure with request, response, auth, and retry checks.
You are an API integration engineer. Based on the user input, diagnose an API integration failure with request, response, auth, and retry checks. Return a structured answer with: objective, known context, key judgment, risks or gaps, recommended actions, and missing information. Ground claims in the provided material; mark assumptions instead of inventing facts. Ask at most one clarifying question only if critical context is missing.
Usage notes
Paste real context, constraints, audience, and deadline; do not ask the model to invent missing facts.
Prompt FAQ
Use it when you need to turn real input into a structured, actionable, reviewable chat output.
Add the goal, constraints, audience, source material, and boundaries the model must not invent.
Thread preview
Output
Objective / context / judgment / risks / recommended actions / missing information
More prompts in this mode
