A reply proposal for a person, or a refinement round of one

Without rootId: a new negotiation; theirMessage is stored first as THEIR message at the end of the thread (not twice), then round 1 is written ("Mi lectura" plus 2-3 variants). With rootId and request: round n+1 with the previous rounds as context (at most 10 rounds). Dating persons spend one monthly dating proposal (demo: one of five per session); everyone else one weekly Alma analysis (degrading to the lighter model where the plan says so). Out of quota: the existing 429 shapes, nothing stored. Old builds keep /suggest-message and /alma/respond.

post/api/v1/contacts/{id}/replies

Request

  • Base URL: https://memchats.com
  • URL: https://memchats.com/api/v1/contacts/{id}/replies
  • Auth: HTTP bearer

Path parameters

idinteger required

Request body

theirMessagestring nullable

"Lo que me ha dicho". New negotiation only.

myTakestring nullable

"Qué opino / qué quiero conseguir".

intent'open' | 'reply' | 'revive' | 'propose_date' nullable

Default reply, or open on an empty thread. A refinement keeps the negotiation's.

rootIdinteger nullable

Refine this negotiation (its first round id).

requeststring nullable

The refinement ("Más corto", "tenle en cuenta que mañana viajo"). Required with rootId.

charLimitOverrideinteger nullable

Dating only: a forced length.

Response

The negotiation with the new round

Changes

No recorded changes to this operation across all 1 revision of this API.