Many Subscribe Pro API endpoints accept a common set of metadata fields. Generally the metadata fields are passed in a
_meta field or key in support API requests.
NOTE: See the documentation for each specific API endpoint to confirm if the endpoint supports metadata fields.
All possible metadata fields which may be passed in Subscribe Pro API requests.
Details about the customer, user or other agent who is making the change represented by the associated API request.
Details about an eCommerce order which is associated with subscription(s) referenced in this API request.
This field is used to pass order details to Subscribe Pro when a customer signs up for a new subscription item via the eCommerce checkout on a connected eCommerce store.
See: Order Details Data Definition
Details about the customer who is making the change represented by this request.
Subscribe Pro customer ID.
Customer email address
Customer full name.
Details about the admin user who is making the change represented by this request.
User ID of the user who is making this change. This may be a unique user ID for the the admin user in the merchant's eCommerce platform or another external system.
Admin user's email address.
Admin user's full name.