Improved
Conference Speaker Intelligence Replaces the Conference & CFP Signal
12 days ago by ReadMe API
Shipped June 4, 2026.
The conference-cfp signal type has been retired and replaced by conference-speaker, a contact-level feed of real speaking appearances: who is speaking, at which event, and on what topic.
What changed
conference-cfpis fully removed from the API surface: it no longer appears inGET /v1/signals/typesor thesignal_typeenum, and requests filtering on it now return a validation error. The type never carried a live data feed, so if you never referenced it explicitly, nothing changes for you.conference-speaker(association:contact, aliasconference) is live now and appears everywhere signal types are listed, includingGET /v1/signals/types/{type}/history.
What you get with conference-speaker
conference-speakerEach signal ties a speaker to an appearance, with metadata in the signal's data payload:
- Event:
conference_name,conference_date,conference_location,conference_url,conference_topics - Session (where the event publishes it):
session_title,session_description,session_track,session_type,session_recording_url - Speaker:
speaker_bio,co_speakers, plusrelevanceandconfidenceindicators
New data lands monthly.
Action needed
If your integration references conference-cfp in signal type filters or mappings, switch it to conference-speaker.
Questions? [email protected]

