openapi: 3.0.0 info: title: BTCPay Greenfield API Keys Stores (Email) API version: v1 description: "# Introduction\n\nThe BTCPay Server Greenfield API is a REST API. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.\n\n# Authentication\n\nYou can authenticate either via Basic Auth or an API key. It's recommended to use an API key for better security. You can create an API key in the BTCPay Server UI under `Account` -> `Manage Account` -> `API keys`. You can restrict the API key for one or multiple stores and for specific permissions. For testing purposes, you can give it the 'Unrestricted access' permission. On production you should limit the permissions to the actual endpoints you use, you can see the required permission on the API docs at the top of each endpoint under `AUTHORIZATIONS`.\n\nIf you want to simplify the process of creating API keys for your users, you can use the [Authorization endpoint](https://docs.btcpayserver.org/API/Greenfield/v1/#tag/Authorization) to predefine permissions and redirect your users to the BTCPay Server Authorization UI. You can find more information about this on the [API Authorization Flow docs](https://docs.btcpayserver.org/BTCPayServer/greenfield-authorization/) page.\n\n# Usage examples\n\nUse **Basic Auth** to read store information with cURL:\n```bash\nBTCPAY_INSTANCE=\"https://mainnet.demo.btcpayserver.org\"\nUSER=\"MyTestUser@gmail.com\"\nPASSWORD=\"notverysecurepassword\"\nPERMISSION=\"btcpay.store.canmodifystoresettings\"\nBODY=\"$(echo \"{}\" | jq --arg \"a\" \"$PERMISSION\" '. + {permissions:[$a]}')\"\n\nAPI_KEY=\"$(curl -s \\\n -H \"Content-Type: application/json\" \\\n --user \"$USER:$PASSWORD\" \\\n -X POST \\\n -d \"$BODY\" \\\n \"$BTCPAY_INSTANCE/api/v1/api-keys\" | jq -r .apiKey)\"\n```\n\n\nUse an **API key** to read store information with cURL:\n```bash\nSTORE_ID=\"yourStoreId\"\n\ncurl -s \\\n -H \"Content-Type: application/json\" \\\n -H \"Authorization: token $API_KEY\" \\\n -X GET \\\n \"$BTCPAY_INSTANCE/api/v1/stores/$STORE_ID\"\n```\n\nYou can find more examples on our docs for different programming languages:\n- [cURL](https://docs.btcpayserver.org/Development/GreenFieldExample/)\n- [Javascript/Node.Js](https://docs.btcpayserver.org/Development/GreenFieldExample-NodeJS/)\n- [PHP](https://docs.btcpayserver.org/Development/GreenFieldExample-PHP/)\n\n" contact: name: BTCPay Server url: https://btcpayserver.org license: name: MIT url: https://github.com/btcpayserver/btcpayserver/blob/master/LICENSE servers: - url: https://{btcpay-host} description: Your BTCPay Server instance variables: btcpay-host: default: mainnet.demo.btcpayserver.org description: The hostname of your BTCPay Server instance security: - API_Key: [] Basic: [] tags: - name: Stores (Email) description: Store Emails operations paths: /api/v1/stores/{storeId}/email: get: tags: - Stores (Email) summary: Get store email settings parameters: - $ref: '#/components/parameters/StoreId' description: Retrieve the email settings configured for specific store. The password field will be masked if present. operationId: Stores_GetStoreEmailSettings responses: '200': description: specified store email settings content: application/json: schema: $ref: '#/components/schemas/GetEmailSettings' '403': description: If you are authenticated but forbidden to view the specified store '404': description: The key is not found for this store security: - API_Key: - btcpay.store.canmodifystoresettings Basic: [] put: tags: - Stores (Email) summary: Update store email settings parameters: - $ref: '#/components/parameters/StoreId' description: Update a store's email settings operationId: Stores_UpdateStoreEmailSettings requestBody: x-name: request content: application/json: schema: $ref: '#/components/schemas/UpdateEmailSettings' required: true x-position: 1 responses: '200': description: The settings were updated content: application/json: schema: $ref: '#/components/schemas/GetEmailSettings' '400': description: A list of errors that occurred when updating the settings content: application/json: schema: $ref: '#/components/schemas/ValidationProblemDetails' '403': description: If you are authenticated but forbidden to modify the store security: - API_Key: - btcpay.store.canmodifystoresettings Basic: [] /api/v1/stores/{storeId}/email/send: post: operationId: Stores_SendStoreEmail tags: - Stores (Email) summary: Send an email for a store description: Send an email using the store's SMTP server parameters: - $ref: '#/components/parameters/StoreId' requestBody: x-name: request content: application/json: schema: type: object additionalProperties: false properties: email: type: string description: Email of the recipient subject: type: string description: Subject of the email body: type: string description: Body of the email to send as plain text. required: true x-position: 1 responses: '200': description: The email was sent (scheduled) successfully '400': description: The store's SMTP is not configured '403': description: If you are authenticated but forbidden to add new stores '404': description: The store was not found security: - API_Key: - btcpay.store.canmodifystoresettings Basic: [] components: schemas: UpdateEmailSettings: allOf: - $ref: '#/components/schemas/EmailSettingsBase' - type: object properties: password: type: string description: SMTP password. Keep null or empty to not update it. nullable: true example: MyS3cr3t GetEmailSettings: allOf: - $ref: '#/components/schemas/EmailSettingsBase' - type: object properties: passwordSet: type: boolean description: '`true` if the password has been set.' EmailSettingsBase: type: object properties: from: type: string description: The sender email address example: sender@gmail.com server: type: string description: SMTP server host example: smtp.gmail.com port: type: integer description: SMTP server port example: 587 login: type: string description: SMTP username example: John.Smith disableCertificateCheck: type: boolean description: Disable TLS certificate security checks example: false StoreId: type: string description: Store ID of the item example: 9CiNzKoANXxmk5ayZngSXrHTiVvvgCrwrpFQd4m2K776 ValidationProblemDetails: type: array description: An array of validation errors of the request items: type: object description: A specific validation error on a json property properties: path: type: string nullable: false description: The json path of the property which failed validation message: type: string nullable: false description: User friendly error message about the validation parameters: StoreId: name: storeId in: path required: true description: The store ID schema: $ref: '#/components/schemas/StoreId' securitySchemes: API_Key: type: apiKey in: header name: Authorization description: 'BTCPay Server API key. Format: ''token {apiKey}''' Basic: type: http scheme: basic description: HTTP Basic Authentication with email and password externalDocs: description: Check out our examples on how to use the API url: https://docs.btcpayserver.org/Development/GreenFieldExample/