RCUR

Follow-ups

List follow-ups

get https://rcur.app/api/v2/follow-ups

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

Query parameters

  • page integer

    Page number for pagination

    Default: 1

Responses

200 List of follow-ups object
  • data array of Followups
    18 child attributes · Followup
    • 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
  • links object
    4 child attributes
    • first string
    • last string
    • prev string nullable
    • next string nullable
  • meta object
    4 child attributes
    • current_page integer
    • last_page integer
    • per_page integer
    • total integer
Try it Send this request with your own API key

Requests run against the live data of the organization that owns the key.