ownerId, or by passing an owner object to create or upsert an owner by email address.
Request Body
The display name for your service. This value appears in the Retempo dashboard, on invoices, and in checkout sessions presented to payers.
A human-readable description of the service. Use this to communicate what the service does or what the subscriber receives.
The initial lifecycle status of the service. Accepted values are
DRAFT, ACTIVE, and DISABLED.DRAFT— the service is created but not yet visible for checkout.ACTIVE— the service is live and can accept new subscribers.DISABLED— the service is deactivated and cannot accept new checkout sessions.
The ID of an existing Retempo user to assign as the service owner. Use this field or the
owner object — not both. If both are provided, ownerId takes precedence.An object to create or upsert a service owner by email. If a user with the given email already exists, Retempo links that user to the service. If no user exists, a new one is created.
Supply either
ownerId or the owner object — not both. If neither is provided, the request returns 400 with "ownerId or owner.email is required.". If you need to associate an owner you have already created, prefer ownerId to avoid accidental upserts.Response
A successful request returns HTTP201 Created with the new service object.
The newly created service object.
Error Responses
| Status | Message | Condition |
|---|---|---|
400 Bad Request | name is required. | name was omitted. |
400 Bad Request | status must be one of: DRAFT, ACTIVE, DISABLED. | An invalid status value was provided. |
400 Bad Request | ownerId or owner.email is required. | Neither ownerId nor owner was provided. |
409 Conflict | A database record with these unique fields already exists. | A conflicting record already exists. |