postCommerceCatalogEntriesWithHttpInfo method

Future<Response> postCommerceCatalogEntriesWithHttpInfo()

Add a catalog entry

Creates a catalog row from the body and answers it at 201. The slug is required and is the globally-unique catalog key, so a second entry claiming a slug already in use is refused 409 rather than shadowing the first. PLATFORM admin only — this is cross-tenant pricing and packaging data, and an org-level admin is refused 403.

Note: This method returns the HTTP Response.

Implementation

Future<Response> postCommerceCatalogEntriesWithHttpInfo() async {
  // ignore: prefer_const_declarations
  final path = r'/v1/commerce/catalog/entries';

  // ignore: prefer_final_locals
  Object? postBody;

  final queryParams = <QueryParam>[];
  final headerParams = <String, String>{};
  final formParams = <String, String>{};

  const contentTypes = <String>[];


  return apiClient.invokeAPI(
    path,
    'POST',
    queryParams,
    postBody,
    headerParams,
    formParams,
    contentTypes.isEmpty ? null : contentTypes.first,
  );
}