Add Fin Agent API to OpenAPI specs and Postman#455
Merged
rahulgdsouza merged 1 commit intomainfrom Apr 16, 2026
Merged
Conversation
The Fin Agent API (POST /fin/start, POST /fin/reply) was documented in developer-docs but missing from the OpenAPI specs. This adds the full API definition including 2 endpoints, 8 component schemas, and the Fin Agent tag to all applicable versions. Also generates the missing v2.15 Postman collection and refreshes v2.14 and Preview collections with the new Fin Agent endpoints. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3bd61a8 to
68a0ef7
Compare
anubhav-intercom
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
The Fin Agent API (
POST /fin/start,POST /fin/reply) was introduced in v2.14 and is fully documented in developer-docs, but was completely missing from the OpenAPI specs in this repo. Since Postman collections are generated from these specs, they were also missing the Fin Agent endpoints. Separately, the v2.15 Postman collection was never generated (the bulk update in PR #302 covered v2.7-2.14 only).How?
Copied the exact Fin Agent API definitions (2 paths, 8 schemas, 1 tag) from the developer-docs YAML specs into v2.14, v2.15, and Preview specs — programmatically verified to match developer-docs exactly. Ran the Postman generation script to create the missing v2.15 collection and refresh v2.14/Preview with the new endpoints. Fern SDK overrides were intentionally skipped (can be added before the next SDK release if custom method naming is desired).
Closes https://github.com/intercom/intercom/issues/489015
Implementation Plan
Plan: Add Fin Agent API to OpenAPI specs + Generate v2.15 Postman Collection
Context
The Fin Agent API (
POST /fin/start,POST /fin/reply) was introduced in v2.14 and is fully documented indeveloper-docs(YAML specs + markdown guides), but is completely missing from theIntercom-OpenAPIrepo. Since Postman collections are auto-generated from this repo's specs, they're also missing the Fin Agent endpoints.Separately, the v2.15 Postman collection was never generated — the bulk Postman update (PR #302) covered v2.7-2.14 and Unstable/Preview, but v2.15 was skipped because the CI pipeline only processes changed YAML files and v2.15 was never touched after the pipeline was set up.
This plan addresses both gaps in a single PR.
What needs to be added
Paths (2 endpoints)
POST /fin/start— Initialize a conversation with FinPOST /fin/reply— Send a user reply back to FinSchemas (8 component schemas)
fin_agent_message— Message object (author, body, timestamp)fin_agent_user— User object (id, name, email, attributes)fin_agent_attachment— File or URL attachmentfin_agent_conversation_metadata— History + conversation attributesfin_agent_attribute_errors— Error details for invalid attributesfin_agent_status_updated_event— Webhook/SSE status change eventfin_agent_replied_event— Webhook/SSE reply eventfin_agent_reply_chunk_event— SSE streaming chunk eventTag (1 new tag)
Fin Agent— Tag definition with descriptionVersions affected
descriptions/2.14/api.intercom.io.yaml— First version with Fin Agent API; drives SDK generation via Ferndescriptions/2.15/api.intercom.io.yaml— Same Fin Agent content as v2.14descriptions/0/api.intercom.io.yaml— Preview; has enhancements (replyingstatus in events)Version differences (Preview vs stable)
fin_agent_status_updated_eventstatus enumescalated, resolved, completeawaiting_user_replyfin_agent_replied_eventstatus enumawaiting_user_replyreplying, awaiting_user_replyfin_agent_reply_chunk_eventstatus enumawaiting_user_replyreplyingImplementation Steps
Step 1: Add Fin Agent API to v2.14 spec
File:
descriptions/2.14/api.intercom.io.yamlcomponents/schemasin alphabetical position/fin/start,/fin/reply) to thepathssectionFin Agenttag to thetagsarrayStep 2: Add Fin Agent API to v2.15 spec
Identical content to v2.14 — same paths, schemas, and tag.
Step 3: Add Fin Agent API to Preview spec
Same structure but with Preview-specific differences in the three event schemas.
Step 4-5: Fern SDK overrides (skipped)
Skipped — Fern will auto-generate SDK method names from operationId. Can be added later.
Step 6: Generate Postman collections
Run
node scripts/postman/generate-postman-in-repo.jsto generate all Postman collections.Step 7: Validate
Generated with Claude Code