> ## Documentation Index > Fetch the complete documentation index at: https://developers.bonifiq.com.br/llms.txt > Use this file to discover all available pages before exploring further. # creates a new product register. ## OpenAPI ````yaml https://api.bonifiq.com.br/swagger/Private%20APIs/swagger.json post /v1/pvt/Product openapi: 3.0.0 info: title: BonifiQ Private APIs description: >- # Introduction This is the BonifiQ Private APIs documentation. With these endpoints you can interact with BonifiQ systems and enhance your program points. # Limitations These endpoints are intended to be used in backend communication so they are not CORS-compatible and cannot be used by in-browser frontend libraries (such as React, Angular, Vue, jQuery, etc) If are required to call BonifiQ API from a browser, please refer to our [Public APIs](https://api.bonifiq.com.br/apidocs/public) # Authentication These Private APis use the [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) scheme. You need both an API Token (Username) and API Key (Password) to use with it You can generate this key pair in BonifiQ admin panel, at the "API Keys" menu. # How to use this page ## Making calls You can simulate, test and make calls to API from this Swagger page. To do that: - Click on the **Authorize** button - Inform the Username (API Token) and Passwoird (API Key) and click on **Authorize** - From the list bellow, choose an API call and click on **Try it out** - Inform the required parameters (if any) and click on **Execute** ## Verifying requests and responses bodies In every API Call there is an explanation of what each field means, theirs types and accepted values for all Requests and Responses. To view this information, just go to any API Call bellow and in the Responses section, click on the Schema. version: 1.0.0 servers: - url: https://api.bonifiq.com.br security: [] tags: - name: POS description: >- Flow methods to integrate BonifiQ with a POS system. Check the Flow Documentation link on the right externalDocs: description: Flow Documentation url: >- https://suporte.bonifiq.com.br/support/solutions/articles/159000319538-integrar-com-pdv - name: Checkout description: Operations related to checkout cashback redeem, refresh and removal - name: Customization description: Retrieve customizations for the loyalty program - name: Rewards description: Interact with rewards already redeemed paths: /v1/pvt/Product: post: tags: - Product summary: creates a new product register. operationId: Product_NewProduct requestBody: x-name: request description: Product Data content: application/json: schema: $ref: '#/components/schemas/CreateProductRequest' required: true x-position: 1 responses: '200': description: '' content: application/json: schema: $ref: >- #/components/schemas/BaseExternalApiResponseOfCreateProductResponse security: - Basic Authentication: [] components: schemas: CreateProductRequest: type: object description: Product model. additionalProperties: false properties: OriginalId: type: string description: Id from the client store. Title: type: string description: Product Name Url: type: string description: Direct url to the product on the client store. nullable: true ImageUrl: type: string description: Product img url. nullable: true IsActive: type: boolean description: if true the product is active on the store. ProductPrice: type: number description: >- How much the customer paid for this product. If it is not null and not zero it can be used with extra points for products rule format: decimal nullable: true ProductBrand: description: Product Brand nullable: true oneOf: - $ref: '#/components/schemas/CreateProductBrandRequest' ProductCategory: description: >- Product Category. Supports hierarchical categories with parent references. nullable: true oneOf: - $ref: '#/components/schemas/CreateProductCategoryRequest' BaseExternalApiResponseOfCreateProductResponse: type: object description: Standard response envelope used by the External API. additionalProperties: false properties: ErrorMessage: type: string description: >- Error message returned when the request fails validation or processing. For warnings and successful responses, consumers should usually inspect `Result`, `Code` and `Severity` first. nullable: true ErrorCode: type: integer description: >- Legacy numeric error code derived from internal API errors when available. This field is relevant only for error flows that use `ApiResponseErrorDescription`. format: int32 nullable: true Result: description: Business payload returned by the endpoint. nullable: true oneOf: - $ref: '#/components/schemas/CreateProductResponse' Code: type: string description: >- Endpoint-specific business code formatted as a two-digit string, such as `03` or `07`. This field is available for success, warning and error outcomes. nullable: true CodeName: type: string description: >- Symbolic enum name associated with `Code`, such as `CheckoutNotFound`. nullable: true Severity: description: >- Final severity of the response. `Success` means the action completed as expected, `Warning` means the request was valid but the business outcome is informational or non-ideal, and `Error` means the request should be treated as a failure. oneOf: - $ref: '#/components/schemas/ExternalApiResponseSeverity' HasWarning: type: boolean description: >- Convenience flag that is `true` when `Severity` is `Warning`. Warnings are valid `200 OK` business outcomes and should not be handled as transport or validation errors. HasError: type: boolean description: >- Indicates whether the request failed and should be handled as an error response. This flag is reserved for real API errors; warnings must keep this property as `false`. CreateProductBrandRequest: type: object additionalProperties: false properties: OriginalId: type: string description: Id from the client store Name: type: string description: Brand Name CreateProductCategoryRequest: type: object description: Product Category model with support for hierarchical categories. additionalProperties: false properties: OriginalId: type: string description: Id from the client store Name: type: string description: Category Name Description: type: string description: Category Description nullable: true ParentCategory: description: |- Parent Category. Use this to create a category tree. For example, if you have Electronics > Smartphones > Android, the Android category would have Smartphones as its ParentCategory, and Smartphones would have Electronics as its ParentCategory. nullable: true oneOf: - $ref: '#/components/schemas/CreateProductCategoryRequest' CreateProductResponse: type: object description: Create Product Response model additionalProperties: false properties: OriginalId: type: string description: Id from the client store Title: type: string description: Product Title/Name Url: type: string description: Url from the client store from the product. nullable: true ImageUrl: type: string description: Url from where the Product image is hosted. nullable: true IsActive: type: boolean description: If true the product is active. ProductPrice: type: number format: decimal nullable: true ExternalApiResponseSeverity: type: integer description: |- 0 = Success 1 = Warning 2 = Error x-enumNames: - Success - Warning - Error enum: - 0 - 1 - 2 securitySchemes: Basic Authentication: type: http description: Use API Basic Auth Keys name: Basic Authentication in: header scheme: basic ````