Apollo.io news and product updates

At its ApolloNEXT event Apollo launched the Apollo Intelligence Layer, which it states is available now. It pairs the Apollo Intelligence Profile, a continuously updated contact and account record that merges Apollo data with the customer's CRM, engagement history and other connected sources, with GTM Harness, an engine that applies skills, orchestration, memory and governance to decide which accounts to work, who to engage and what to do next. Apollo says the layer connects customer data and business context to take action with minimal human involvement.

Apollo is moving from a data and sequencing tool toward a system that decides who to contact, so buyers should look closely at how supervision is set and who signs off on independent action.

Apollo added structured error_details to selected REST and MCP errors, with stable codes and recovery guidance covering search validation and enrichment failures. Organization Enrichment requests with a missing or unreadable identifier now return HTTP 422 where they used to return 200 with an empty organization. The legacy top level fields on migrated errors will be removed on 16 February 2027.

The 200 that becomes a 422 is the line to read. Any workflow that treated an empty enrichment as a quiet success will now see a failure, which is the honest answer and also a breaking one. The February 2027 removal date gives integration owners five months to update their error handling.