sales

Get Outreach Context

Everything Rooster needs to decide what to say next to one agency.

⛔THE ROUTE THAT MAKES agent_outreach.build_outreach_context MORE THAN A MODULE. It already has a caller inside the API (campaign_worker's automated composition), but Rooster reads over HTTP as a chat-based reasoner, and without this route the brief was unreachable to him: the same "built but not running" state that left am_capture without a scheduler and account-watch without a watcher.

Returns facts and boundaries, never a decision: no ranked option, no chosen template, no score. The judgement is Rooster's, and putting it back into Python would defeat the point of the brief.

⛔SEALED TO ONE AGENCY BY THE PATH ITSELF. org_id is a path parameter rather than a filter, so there is no version of this call that reads across agencies. build_outreach_context raises BlankOrgId rather than degrading, and the response carries a provenance block naming what is sealed and what is shared.

get/api/sales/outreach/context/{org_id}

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/sales/outreach/context/{org_id}
  • Auth: none declared

Path parameters

org_idstring uuid required

Query parameters

contact_idstring uuid nullable

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.