> ## Documentation Index > Fetch the complete documentation index at: https://docs.pubrio.com/llms.txt > Use this file to discover all available pages before exploring further. # Company Signal Events > Enriched, paginated drill-down into the signal events driving a single company's expansion. ## OpenAPI ````yaml en-openapi POST /expansions/companies/pulse_events openapi: 3.0.0 info: description: >- The Pubrio API delivers market expansion intelligence — real-time signals that flag when a company enters a new market — alongside the company and people data beneath them. Search, look up, and enrich accounts and contacts, and subscribe to typed, dated movement signals across 200+ markets. version: 1.0.0 title: Pubrio OpenAPI termsOfService: https://pubrio.com/en/terms-of-service contact: email: king.lai@pubrio.com name: King Lai url: https://pubrio.com/en/get-in-touch license: name: Apache 2.0 url: http://www.apache.org/licenses/LICENSE-2.0.html servers: - url: https://api.pubrio.com security: - pubrio_api_key: [] tags: - name: Profile description: Workspace profile information and usage statistics - name: Enrichment description: Enrich people and company records with detailed B2B data - name: Lookalike description: Find companies similar to a given company - name: Search description: Search for people, companies, jobs, news, and advertisements with filters - name: Lookup description: >- Look up detailed information for specific people, companies, jobs, news, advertisements, and technologies - name: LinkedIn description: Look up people and company data via LinkedIn profile URLs - name: Redeem description: Redeem credits to unlock people contact details (single and batch) - name: Channels description: Manage outreach channel templates (create, update, delete, list) - name: Monitor description: Create and manage data monitors with webhooks, statistics, and processing - name: Filters description: >- Retrieve available filter values for search parameters (technologies, locations, verticals, etc.) - name: API Keys description: List and inspect API request logs and usage analytics for API keys - name: Insights description: Aggregated signal insights for companies (jobs, news, advertisements). - name: Export description: Bulk data exports (credit-gated). - name: Expansion description: >- Company market-expansion intelligence: signals, stages, markets, and exports. externalDocs: description: >- The Pubrio API is used to search, preview and enrich Contacts and Accounts. Pubrio database provides extensive B2B contacts and sales intelligence data. url: https://docs.pubrio.com paths: /expansions/companies/pulse_events: post: tags: - Expansion summary: Company Signal Events description: >- Enriched, paginated drill-down into the signal events driving a single company's expansion. operationId: expansions_company_pulse_events requestBody: required: true content: application/json: schema: type: object properties: signal_types: $ref: '#/components/schemas/expansion_signal_type_slugs' country_codes: type: array items: type: string example: - JP - SG description: >- Optional. Scope the feed to one or more foreign markets (ISO 3166-1 alpha-2, e.g. `["JP","SG"]`). Omitted → all foreign markets (the home market is always excluded). transitioned_dates: type: array items: type: string format: date example: - '2026-04-01' - '2026-06-29' description: >- ISO `[from, to]` date range for the signal/transition window. Takes precedence over `window_days` when both are supplied. window_days: type: integer example: 90 default: 90 description: >- Optional. Size of the rolling events window in days. Defaults to **90** (the standard display window) when neither this nor `transitioned_dates` is supplied. `transitioned_dates` takes precedence when both are sent. query: type: string example: >- We sell Employer-of-Record and local payroll; best-fit buyers hire in a new market before setting up a legal entity. description: >- Plain-language description of what you sell, or the buyer profile you're evaluating this company against. Used only to ground the AI `summary` (see `is_explain_match`); unlike the company search, it is NOT interpreted into filters here. is_explain_match: type: boolean example: true description: >- When true and a `query` is supplied, `data.summary` returns a single AI summary of this company's expansion activity read against your `query`, grounded in the company's real signals with `[n]` citations. Unlike the company search's per-company `match_summary`, this summary is built from the company's ENTIRE feed for the window (all markets, every signal), so it is stable regardless of `page` / `per_page`. domain: $ref: '#/components/schemas/domain' linkedin_url: $ref: '#/components/schemas/company_linkedin_url' domain_search_id: $ref: '#/components/schemas/domain_search_id' page: $ref: '#/components/schemas/page' per_page: $ref: '#/components/schemas/per_page' profile_id: $ref: '#/components/schemas/profile_id' anyOf: - title: Domain Search ID required: - domain_search_id - title: Domain required: - domain - title: LinkedIn URL required: - linkedin_url responses: '200': description: >- Paginated signal events. When `is_explain_match` is true and a `query` is supplied, `data.summary` holds an AI summary (`{ text, citations }`) of the company's full-feed activity read against the query; it is `null` otherwise. content: application/json: schema: type: object properties: metadata: type: object data: {} example: metadata: filters: domain_search_id: 550e8400-e29b-41d4-a716-446655440002 data: pagination: page: 1 per_page: 25 total_entries: 42 total_pages: 2 total_display_pages: 2 is_timeout: false events: - signal_type_slug: EXEC stage_slug: expanding country_code: US signal_subtype_slug: country_manager source_type: linkedin polarity: expansion display_label: Hired Country Manager evidence_url: https://linkedin.com/company/example-corp event_date: '2026-06-20T14:00:00.000Z' summary: text: >- Example Corp is hiring across Tokyo[1] and just added a Japan Country Manager[2], yet has no legal entity on file — it is staffing the market before incorporating, which is exactly your window. citations: - 'n': 1 type: HIRE label: Tokyo software & field-ops roles country: JP date: 2026-06 url: null - 'n': 2 type: EXEC label: Country Manager, Japan country: JP date: 2026-06 url: https://linkedin.com/in/example components: schemas: expansion_signal_type_slugs: type: array items: type: string enum: - AD - NEWS - INFRA - PARTNER - EVENT_PLUS - EXEC - OFFICE - HIRE - SCALE - PRODUCT example: - EXEC - HIRE description: Filter to specific signal types. domain: type: string example: pubrio.com description: >- A company domain used for company search operations. If we receive a URL such as `www.pubrio.com` or `https://docs.pubrio.com/`, the system will convert it to `pubrio.com` for processing. company_linkedin_url: type: string example: https://www.linkedin.com/company/pubrio description: >- The fully formed URL of the LinkedIn company profile. URL begin with `http` and contain `linkedin.com/company/` domain_search_id: type: string format: uuid description: A unique identifier for the company search operation. page: type: integer example: 1 description: The page number of the Pubrio data that you want to retrieve. per_page: type: integer example: 25 description: >- The number of search results that should be returned for each page. Limited the number of results per page improves the endpoint's performance. profile_id: type: integer description: >- Optional. An identifier for the user profile (workspace) making the request. This is no longer required as the API key already includes your workspace information. If provided, it helps in associating the lookup with a specific user, allowing for data retrieval and credit tracking. Check out `user details` endpoints under the Profile tab for more information. securitySchemes: pubrio_api_key: type: apiKey name: pubrio-api-key description: >- A unique API token that represents the actions you perform through the API and the corresponding permissions and operations. You can create it through the [Settings](https://dashboard.pubrio.com/#/settings/) section. in: header ````