Skip to main content
The akta.pro Company Partnerships API returns the full partnership and strategic-relationship list for a single company. Pass a company website domain or UUID in the path and get back an array of partnerships — each tagged with a type (technology integration, strategic co-development, channel partner, etc.), a strategic_tier (Core / Minor), and source URLs the partnership was drawn from. This is a synchronous GET API. Pass the company in the URL path and receive the partnership list immediately in the HTTP response. No polling required. Partnerships vs. full Company Data API: Use this endpoint when you only need the partnership list without the rest of the strategic signal section.
Need the full strategic_signal section with scale_indicator, recent_move, and leadership_change alongside the partnership list? Use the Company Data API and request strategic_signal as a section.
The fields included in every response: Each partnership carries:
  • name — partner name
  • uuid — Akta UUID; pass it to the Company Data API to enrich the partner further
  • type — partnership bucket. technology_integration, strategic_codevelopment, channel_reseller_distributor, etc.
  • strategic_tier — Core (flagship) or Minor (peripheral)
  • description — one paragraph explaining the partnership
  • announced_on — date the partnership was announced (day / month / year)
  • source — array of URLs the partnership was drawn from
Common use cases:
  • Channel and partnership intelligence : surface a “partners” panel on a company record so reps and partnerships teams can spot synergy or conflict
  • Ecosystem mapping : dump the full list into a graph view of a company’s alliances and integrations
  • AI assistant / model integrations : filter by type: technology_integration to find which AI-assistant or model-provider integrations the company has shipped
  • M&A and acquisition context : filter by type: strategic_codevelopment or scan descriptions for acquisition signals
This API is synchronous. The partnership list is returned directly in the HTTP response. No job submission or polling required.