> ## Documentation Index > Fetch the complete documentation index at: https://docs.taberna.io/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Taberna is a crypto payments API. Amounts are priced in fiat (USD or EUR) and paid in crypto. > Fiat amounts are ALWAYS decimal strings ("9.99"), never numbers. Crypto amounts are integer strings in the asset's smallest unit. > Authenticate merchant endpoints with `Authorization: Bearer tbrn_live_...`. Every key is bound to one store and carries an explicit scope set, so never pass a store id to a /v1 endpoint. > A 401 means the credential is bad; a 403 means the key lacks a scope. Never retry or re-authenticate on a 403 — surface it as a configuration error. > The /v1/checkouts endpoints are deliberately unauthenticated and run in the buyer's browser. Never send an API key to a browser. > Verify webhook signatures over the RAW request body before parsing JSON, and treat delivery as at-least-once: handlers must be idempotent. > Never grant value based on a browser redirect to successUrl. Fulfil on a signature-verified webhook, or on a server-side read of GET /v1/orders/{id} or GET /v1/invoices/{id}. > There is no test mode: every payment method is a live chain moving real funds. # Email an invoice > Emails an open invoice to the address stored on it. Requires the `invoices:write` scope. Takes no body: the recipient is always the invoice's own `customerEmail` and cannot be overridden. Sends are capped per invoice, per store and platform-wide; the invoice's `email` object reports the remaining allowance, and a rate-limited response carries a `Retry-After` header. ## OpenAPI ````yaml /api-reference/openapi.json post /v1/invoices/{id}/send openapi: 3.1.0 info: title: Taberna API description: >- Accept crypto payments for digital goods. Create orders and invoices, hand the buyer a hosted checkout link, and let webhooks tell you when the money lands. Authenticate merchant endpoints with a store API key as a bearer token (`Authorization: Bearer tbrn_live_…`). Every key is bound to one store and carries an explicit set of scopes; the scope a route requires is stated in its description and in the `x-required-scope` extension. A key without the scope gets a 403 — mint one with the scope rather than retrying. The Checkout endpoints are the exception: they are unauthenticated and meant to be called from the buyer's browser. Possession of the checkout id is the credential there, so never ship an API key to a page. Conventions: ids in links are short ids; fiat amounts are decimal strings ("9.99"); crypto amounts are integer strings in the asset's smallest unit; timestamps are ISO-8601 UTC. Errors carry `{ "error": "…" }` unless documented otherwise. version: 1.0.0 servers: - url: https://api.taberna.io description: Taberna API security: [] tags: - name: Orders description: Carts of products, paid through a hosted checkout. - name: Invoices description: Merchant-issued bills with their own payment page. - name: Invoice Templates description: Saved invoice presets, referenced by `templateId` when creating one. - name: Products description: Catalogue reads and delivery stock top-ups. - name: Store description: What the calling API key is and what it may do. - name: Webhook Deliveries description: Delivery history for the store webhook, and replay. - name: Checkout description: >- Buyer-facing hosted-page endpoints. Unauthenticated by design — never send an API key. paths: /v1/invoices/{id}/send: post: tags: - Invoices summary: Email an invoice description: >- Emails an open invoice to the address stored on it. Requires the `invoices:write` scope. Takes no body: the recipient is always the invoice's own `customerEmail` and cannot be overridden. Sends are capped per invoice, per store and platform-wide; the invoice's `email` object reports the remaining allowance, and a rate-limited response carries a `Retry-After` header. operationId: postV1InvoicesByIdSend parameters: - in: path name: id schema: type: string pattern: ^[1-9A-HJ-NP-Za-km-z]{21,22}$ required: true responses: '200': description: The invoice was handed to the mailer. content: application/json: schema: type: object properties: invoiceId: type: string description: >- Public short id — the value that appears in checkout links. sentTo: type: string sentAt: type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ description: ISO-8601 timestamp in UTC. sendCount: type: integer minimum: -9007199254740991 maximum: 9007199254740991 sendsRemaining: type: integer minimum: -9007199254740991 maximum: 9007199254740991 maxSends: type: integer minimum: -9007199254740991 maximum: 9007199254740991 required: - invoiceId - sentTo - sentAt - sendCount - sendsRemaining - maxSends '400': description: >- The invoice is not in a state that can be emailed — voided, paid, expired, or without a stored customer email. A request rejected before it reaches the mailer (malformed invoice id, failed validation) answers with the plain `{ "error": … }` body instead. content: application/json: schema: type: object properties: error: type: string code: type: string enum: - not_found - not_sendable - rate_limited - send_failed retryAfterSeconds: anyOf: - type: integer minimum: -9007199254740991 maximum: 9007199254740991 - type: 'null' required: - error - code - retryAfterSeconds '401': description: >- Missing, malformed, revoked or expired API key. The `WWW-Authenticate` header names the challenge that failed. content: application/json: schema: type: object properties: error: type: string required: - error description: Error response. '403': description: The key is valid but was not granted the scope this route requires. content: application/json: schema: type: object properties: error: type: string required: - error description: Error response. '404': description: >- No such invoice for this API key's store. A request rejected before it reaches the mailer (malformed invoice id, failed validation) answers with the plain `{ "error": … }` body instead. content: application/json: schema: type: object properties: error: type: string code: type: string enum: - not_found - not_sendable - rate_limited - send_failed retryAfterSeconds: anyOf: - type: integer minimum: -9007199254740991 maximum: 9007199254740991 - type: 'null' required: - error - code - retryAfterSeconds '429': description: >- A send limit was hit. `retryAfterSeconds` is set when the block is a cooldown rather than an exhausted allowance, and is mirrored in the `Retry-After` header. content: application/json: schema: type: object properties: error: type: string code: type: string enum: - not_found - not_sendable - rate_limited - send_failed retryAfterSeconds: anyOf: - type: integer minimum: -9007199254740991 maximum: 9007199254740991 - type: 'null' required: - error - code - retryAfterSeconds '502': description: >- The email provider rejected the send. The attempt does not count against the allowance, so it is safe to retry. content: application/json: schema: type: object properties: error: type: string code: type: string enum: - not_found - not_sendable - rate_limited - send_failed retryAfterSeconds: anyOf: - type: integer minimum: -9007199254740991 maximum: 9007199254740991 - type: 'null' required: - error - code - retryAfterSeconds security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer description: >- A store API key, sent as `Authorization: Bearer `. Live keys are prefixed `tbrn_live_`. Keys are minted per store in the dashboard with an explicit scope set. ````