---
title: "Expire Creator Invites Endpoint"
method: POST
path: "/api/v1/remy/cron/creator-invites/expire"
tags: ["remy"]
---

# Expire Creator Invites Endpoint

`POST /api/v1/remy/cron/creator-invites/expire`

## Request

- Base URL: `https://api.brandbooster.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.brandbooster.ai/api/v1/remy/cron/creator-invites/expire`
- Auth: none declared

Mark invites whose window has closed as expired. Meant for a daily Cloud Scheduler hit.

Open, like the cron payload routes below — the only effect is writing `expired` onto rows whose
window already closed, which the listing reports anyway.

Safe to run repeatedly and safe to miss: only sent/opened rows past their expiry are picked up,
and the next run catches up on anything that expired while it was down.

`limit` is for a cautious first run; leave it off in the schedule.

## Query parameters

- `limit` integer, nullable: Cap how many invites this run touches

## Response `200`

Successful Response

- CreatorInviteExpirySweepResponseDTO
  - `expired` integer

## Other responses

- `422`: Validation Error

## Changes

> 35 revisions in range; 1 not diffed.

- **2026-09-11** `163530d84bc1`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/brandbooster/apis/fastapi/changes/api/v1/remy/cron/creator-invites/expire/post.md)

---

[API](https://skmtc.dev/brandbooster/apis/fastapi.md) - [All operations](https://skmtc.dev/brandbooster/apis/fastapi/llms.txt) - [OpenAPI document](https://skmtc.dev/brandbooster/apis/fastapi/revisions/8e8c18c2dc35?raw)