In Take a NAP, every online store or Software as a Service (SaaS) platform is considered a “Shop.” This terminology encompasses a broad range of entities that engage in online commerce, regardless of their size or specific business model.
The reason for this classification is that each Shop within Take a NAP has the legal capability to:
These functionalities are integral to complying with Bulgarian laws and regulations related to online commerce. By unifying these diverse entities under the concept of a Shop, Take a NAP provides a streamlined and consistent interface for managing essential compliance tasks.
Whether you are a single online store or a multi-platform SaaS provider, Take a NAP’s Shop structure offers the tools and flexibility needed to ensure seamless integration with the regulatory environment.
In this section, we’ll cover how to create, update, and delete shops using the Take a NAP API. Depending on the API key issued, you may create a single store or multiple stores (for store platforms).
Use the following endpoint to create a store:
x-api-key
: Take a NAP API keyx-signature
: Signed payload with Take a NAP API secretRefer to the CreateShopDto
schema in the API reference.
Refer to the ShopDto
schema in the API reference.
If your API key allows for the creation of multiple stores, you can use the same endpoint as above.
Use the following endpoint to update a shop:
x-signature
: Signed payload with Take a NAP API secretx-api-key
: Take a NAP API keyRefer to the UpdateShopDto
schema in the API reference.
Refer to the ShopDto
schema in the API reference.
Use the following endpoint to delete a shop:
When a shop is deleted, all associated data including orders, receipts, and audit files are also permanently deleted. This action is irreversible, so please proceed with caution.
x-api-key
: Take a NAP API keyx-signature
: Signed payload with Take a NAP API secretRefer to the DeleteShopDto
schema in the API reference.
Refer to the DeleteShopResponseDto
schema in the API reference.
For more details on the request and response schemas, please refer to the official API reference. If you encounter any issues or have questions, please contact our support team.
In Take a NAP, every online store or Software as a Service (SaaS) platform is considered a “Shop.” This terminology encompasses a broad range of entities that engage in online commerce, regardless of their size or specific business model.
The reason for this classification is that each Shop within Take a NAP has the legal capability to:
These functionalities are integral to complying with Bulgarian laws and regulations related to online commerce. By unifying these diverse entities under the concept of a Shop, Take a NAP provides a streamlined and consistent interface for managing essential compliance tasks.
Whether you are a single online store or a multi-platform SaaS provider, Take a NAP’s Shop structure offers the tools and flexibility needed to ensure seamless integration with the regulatory environment.
In this section, we’ll cover how to create, update, and delete shops using the Take a NAP API. Depending on the API key issued, you may create a single store or multiple stores (for store platforms).
Use the following endpoint to create a store:
x-api-key
: Take a NAP API keyx-signature
: Signed payload with Take a NAP API secretRefer to the CreateShopDto
schema in the API reference.
Refer to the ShopDto
schema in the API reference.
If your API key allows for the creation of multiple stores, you can use the same endpoint as above.
Use the following endpoint to update a shop:
x-signature
: Signed payload with Take a NAP API secretx-api-key
: Take a NAP API keyRefer to the UpdateShopDto
schema in the API reference.
Refer to the ShopDto
schema in the API reference.
Use the following endpoint to delete a shop:
When a shop is deleted, all associated data including orders, receipts, and audit files are also permanently deleted. This action is irreversible, so please proceed with caution.
x-api-key
: Take a NAP API keyx-signature
: Signed payload with Take a NAP API secretRefer to the DeleteShopDto
schema in the API reference.
Refer to the DeleteShopResponseDto
schema in the API reference.
For more details on the request and response schemas, please refer to the official API reference. If you encounter any issues or have questions, please contact our support team.