RCUR

Follow-ups

Update follow-up status

put https://rcur.app/api/v2/follow-ups/{id}

Requires your API key as Authorization: Bearer <key>. See authentication.

Path parameters

  • id string required

Request body

application/json

Follow-up status update

  • status string required

    New status

    One of pending failed solved

  • resolution string nullable

    Only with status `solved`: whether the customer paid outside RCUR (`paid_manually`) or the amount is written off unpaid (`written_off`). Used by the recovery report; omit it if unknown.

    One of paid_manually written_off

Responses

200 Follow-up details Followup object
  • id string required
  • description string required
  • type string required

    One of both link retry

  • status string required

    One of pending solved failed

  • resolution string nullable

    How a solved follow-up ended: `paid` through RCUR, `paid_manually` outside RCUR, or `written_off` unpaid. Null while not solved, or when unknown.

    One of paid paid_manually written_off

  • amount string required
  • currency string required

    One of AED AUD BGN BRL CAD CHF CZK DKK EUR GBP HKD HUF ILS ISK JPY MXN MYR NOK NZD PHP PLN RON SEK SGD THB TWD USD ZAR

  • mollie_profile_id string nullable
  • mollie_payment_id string nullable
  • reason string nullable
  • reason_code string nullable
  • retries_done integer
  • mails_sent integer
  • next_retry_at string nullable
  • created_at string required
  • customer object nullable
  • subscription object nullable
  • order object nullable
404 Resource not found Error object
  • status integer required
  • error string required
Try it Send this request with your own API key

Requests run against the live data of the organization that owns the key. This PUT request changes that data.