Skip to main content
PostmanLinkedIn

Postman hosts live session on dependency discovery and CI for coding agents.

Source: Autobound Signal API · 76 signals tracked for Postman · updated

Get Postman's live signals in Claude or ChatGPT, or by API

AskWhat changed at Postman this week? Use Autobound signals for postman.com.

Source

LinkedInNov 12, 2026
likes
11
comments
0

Post

Which APIs does this change touch? Make your agent answer first. If you've asked a coding agent to change code that calls someone else's API, you know the failure modes: - It can't see the services outside your repo. - It stalls when a dependency is unavailable. - Its checks vanish when the session ends. On Tuesday, November 17, 10:00 to 10:30 AM PT, Talia Kohan and Anthony Viard will take one real change through the Postman plugin inside a coding agent. They start by identifying the APIs the change touches and finish by verifying that the completed integration works. It's 30 minutes, live on YouTube and LinkedIn. What they'll cover: → Dependency discovery. Give your agent context about your other services so it finds dependencies outside your repository before it changes any code. → Mocking. When the services you depend on aren't available, the agent mocks them so you can run your service locally without credentials. → CI. One API change goes through collection sync, schema linting, a mock and a CI run on every push, so the agent's verification keeps running after the session ends. To follow along: 1. Install the plugin beforehand with one command (requires Node.js 22 or later). It adds the plugin to every coding agent it detects on your machine: npx @postman/postman-plugin 2. Bring a project that calls at least one API you don't own, so you have something real to...

Keep reading with a free account

The rest of this post, and every signal for Postman, is in your free account.

Extracted by Autobound

From the Signal API record
Signal
LinkedIn

What this signalsCompany posts often show what the team is pushing right now.

More LinkedIn signals at other companies

The full record

From the Signal API record

Topics and mentions

Tags

  • Integration
  • Events

Initiatives

  • live coding agent session on YouTube

Technologies named

  • Node.js
  • Luma event page
  • YouTube

Extraction

Detected
Nov 12, 2026
signal_type
linkedin-post-company
signal_subtype
linkedinPost

Use this data

Get every LinkedIn signal for Postman and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Postman this week?”

  2. Send it to your own tools

    The Signal API returns LinkedIn signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full linkedin-post-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/d9b1dc41-cc93-4804-b94b-74da926e70ee returns this record as JSON. POST /v1/companies/enrich returns every signal for postman.com.

{
  "signal_id": "d9b1dc41-cc93-4804-b94b-74da926e70ee",
  "signal_type": "linkedin-post-company",
  "signal_subtype": "linkedinPost",
  "detected_at": "2026-11-12T18:38:15.024+00:00",
  "company": {
    "name": "Postman",
    "domain": "postman.com"
  },
  "data": {
    "tags": [
      "Events",
      "Integration"
    ],
    "summary": "Postman hosts live session on dependency discovery and CI for coding agents.",
    "post_url": "https://www.linkedin.com/posts/postman-platform_which-apis-does-this-change-touch-make-your-activity-7526714997583007744-ve4N",
    "num_likes": 11,
    "post_text": "Which APIs does this change touch? Make your agent answer first.\n\nIf you've asked a coding agent to change code that calls someone else's API, you know the failure modes:\n- It can't see the services outside your repo.\n- It stalls when a dependency is unavailable.\n- Its checks vanish when the session ends.\n\nOn Tuesday, November 17, 10:00 to 10:30 AM PT, Talia Kohan and Anthony Viard will take one real change through the Postman plugin inside a coding agent. They start by identifying the APIs the change touches and finish by verifying that the completed integration works. It's 30 minutes, live on YouTube and LinkedIn.\n\nWhat they'll cover:\n\n→ Dependency discovery. Give your agent context about your other services so it finds dependencies outside your repository before it changes any code.\n\n→ Mocking. When the services you depend on aren't available, the agent mocks them so you can run your service locally without credentials.\n\n→ CI. One API change goes through collection sync, schema linting, a mock and a CI run on every push, so the agent's verification keeps running after the session ends.\n\nTo follow along:\n1. Install the plugin beforehand with one command (requires Node.js 22 or later). It adds the plugin to every coding agent it detects on your machine:\n npx @postman/postman-plugin\n2. Bring a project that calls at least one API you don't own, so you have something real to...",
    "initiatives": [
      {
        "topic": "live coding agent session on YouTube",
        "urgency": 0.8
      }
    ],
    "posted_date": "2026-11-12T18:38:15.024Z",
    "num_comments": 0,
    "technologies_mentioned": [
      {
        "name": "Node.js",
        "status": "considering"
      },
      {
        "name": "Luma event page",
        "status": "considering"
      },
      {
        "name": "YouTube",
        "status": "considering"
      }
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.