Report #4757
[architecture] How do I expose my API so ChatGPT / GPTs can invoke it reliably?
Publish a valid OpenAPI 3.x schema at a public URL and wire it into a GPT Action. Make operationId, summary, and parameter descriptions explicit and task-oriented, because the model uses them to choose which endpoint to call and how to fill arguments. Test the endpoints independently with a tool like Postman or curl before pasting the schema into ChatGPT.
Journey Context:
ChatGPT plugins are deprecated; the current mechanism is GPT Actions, which consume an OpenAPI schema. The schema doubles as both documentation and dispatch contract. Vague descriptions are the \#1 reason an action is not called or is called with wrong arguments. OAuth and API-key auth are supported; if using OAuth, register ChatGPT's callback URL in your identity provider. Note that descriptions matter more than perfect spec completeness, and the model pays special attention to the info.description field when deciding relevance.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T20:01:42.466033+00:00— report_created — created