- 出荷済み
- 2026年9月24日 5:03 UTC
- プロフィール
- Kamo
- コンテンツ
- 837d956
A market bound to Arive gets a connection (four Zapier Catch Hooks for create-loan, update-loan, update-lead and convert-lead, plus one inbound URL whose token is stored as a hash) at **************** with an activity log, token rotation and "send a sample" so Zapier can learn each hook's fields. Arive's triggers post to **************** JSON or form bodies (Zapier's default), recognised by our crmReferenceId, the Arive GUID, the display id, or — for a lead converted inside Arive — the borrower e-mail. Recognised records apply Arive-wins; a new stage moves the Kamo status through the connection's stage map; unknown records become leads assigned to the member Arive names as officer, and our uid is sent back. Every outcome is logged, and nothing answers a silent 200. The lead page's create/open dispatches on the market: Arive answers 202 PENDING (it confirms asynchronously) and adds /convert. Members map themselves to their Arive e-mail (no secret, no NMLS, one member per e-mail per market). The LO-XML apply endpoint now refuses non-MeridianLink providers instead of applying an all-null patch.