Authorization
Path Parameters
Request Body
productId may be supplied in the request body OR as a query parameter (see
Query Parameters). At least one location is required.
The unique identifier of the product the member belongs to. Accepted here in the
JSON body, or alternatively as a query parameter.Example:
7c9d2e1f-4a5b-4c6d-8e9f-0a1b2c3d4e5fQuery Parameters
Alternative location for
productId when you prefer not to send a request body.
Use either the body field or this query parameter.Example:?productId=7c9d2e1f-4a5b-4c6d-8e9f-0a1b2c3d4e5fIdempotency (term-based)
Invoices are idempotent per billing term. The endpoint keys on the member’s current billing period: if an unpaid invoice already exists for the current period it is reused and returned instead of creating a duplicate. Calling this endpoint repeatedly within the same billing term therefore returns the same invoice (and the samemembershipBillUrl).
Response
Successful ResponseMain Structure (Root Object)
Status message that describes the result. Note the singular
message key
(write endpoints use message; read/list endpoints use the plural messages).The membership bill URL the customer can use to pay. Built from the tenant’s shop
subdomain in the shape
https://<tenant>.mayar.shop/pl/<link> — this is not an
api.mayar.id URL.Errors
All errors use the envelope{ "statusCode": <code>, "message": "<reason>" } (singular message).
Error Example 400
