> ## Documentation Index > Fetch the complete documentation index at: https://docs.bolta.io/llms.txt > Use this file to discover all available pages before exploring further. # Request Expense Sync > Requests a collection of all expenses connected in the dashboard. The API only accepts the request with `202 Accepted`, and the collection runs asynchronously. Bolta collects expenses periodically, so request a sync only when you need a document just registered with the NTS. There is no path to check collection status. Continue fetching `GET /v1/expenses` with your saved cursor. Each business can request a sync once every 30 minutes and up to 12 times in 24 hours, counted separately from the revenue sync. Requests rejected with `409` or `422` do not count toward the limit. Test keys do not collect anything and return only the acceptance response. [Revenue and expense guide](/en/api-introduction/revenue-expense) ## OpenAPI ````yaml /openapi.en.yaml post /v1/expenses:sync openapi: 3.1.0 info: title: Bolta API description: > The Bolta e-tax invoice API. [API Overview](/en/api-introduction/overview) | [Authentication guide](/en/api-introduction/authentication) | [Use cases](/en/api-introduction/usecase-b2b) version: 1.0.0 servers: - url: https://xapi.bolta.io description: Bolta API server security: - basicAuth: [] tags: - name: Tax Invoice Issuance description: > Issue and amend e-tax invoices. [Calculating the issuance amount](/en/api-introduction/issuance-guide) | [Amendment types](/en/api-introduction/amendment-guide) - name: Tax Invoice Retrieval description: > Retrieve e-tax invoice results and request processing status, and download the PDF of an issued tax invoice. [Tax invoice PDF guide](/en/api-introduction/tax-invoice-pdf) - name: Reverse Issuance description: > Request and manage reverse issuance of e-tax invoices. [Email-approval reverse issuance](/en/api-introduction/usecase-reverse-email) | [Simple-approval reverse issuance](/en/api-introduction/usecase-reverse-simple) - name: Cash Receipt description: > Issue, cancel, and check the status of cash receipts. [Cash receipt guide](/en/api-introduction/cash-receipt-guide) | [Cash receipt webhooks](/en/api-introduction/webhook-cash-receipt) - name: Business Registration Status description: > Check the registration status and tax type of a business registration number. Look up one number or up to 100 numbers at once. This API requires no issuer registration and no certificate. [Business registration status guide](/en/api-introduction/business-registration-status) - name: Revenue and Expense description: > Retrieve the revenue and expense tax invoices of your own business in Bolta in the order they changed, and request a collection. Responses include documents issued through Bolta and documents collected from Hometax. You need a Standard plan or higher, and the calls deduct no points. Connect Hometax in the Bolta dashboard first. [Revenue and expense guide](/en/api-introduction/revenue-expense) - name: Bank Account Transactions description: > Retrieve the bank accounts and transactions connected to your own business in Bolta, and request a sync. You need a Standard plan or higher, and the calls deduct no points. Connect bank accounts in the Bolta dashboard first. [Bank account transactions guide](/en/api-introduction/bank-account-transactions) - name: Bank Account Holder description: > Look up account holder names with a bank code and an account number. One path takes a single account and the other takes up to 100 accounts at once. Each account that returns a holder name deducts 50 points. [Bank account holder guide](/en/api-introduction/bank-account-holder) - name: Document Issuance description: > Issue National Tax Service certificates from Hometax or a certified copy of corporate registry, and download the original PDF. Hometax documents are issued only for the business that owns the API key, and you must register a joint certificate in the Bolta dashboard. A corporate registry is issued for the corporation in `corporationNumber` and needs no joint certificate. Supported corporation types are stock company, limited company, general partnership company, limited partnership company, limited liability company, incorporated association, incorporated foundation, medical corporation, cooperative (including social cooperative), and other corporate entity (such as a patent corporation). Each document deducts 500 points for Hometax documents, 1,000 points for a corporate registry view copy, and 1,500 points for a submission copy. [Document issuance guide](/en/api-introduction/document-issuance) - name: Issuer description: > Register and manage businesses that act as tax invoice issuers. Certificate requirements depend on the issuance type. [Glossary](/en/api-introduction/glossary) | [Delegated issuance](/en/api-introduction/usecase-delegated) | [Brokered Tax Invoice Issuance](/en/api-introduction/usecase-brokered) - name: Certificate description: > Register and manage issuer certificates. [Certificate registration](/en/api-introduction/certificate-registration) paths: /v1/expenses:sync: post: tags: - Revenue and Expense summary: Request Expense Sync description: > Requests a collection of all expenses connected in the dashboard. The API only accepts the request with `202 Accepted`, and the collection runs asynchronously. Bolta collects expenses periodically, so request a sync only when you need a document just registered with the NTS. There is no path to check collection status. Continue fetching `GET /v1/expenses` with your saved cursor. Each business can request a sync once every 30 minutes and up to 12 times in 24 hours, counted separately from the revenue sync. Requests rejected with `409` or `422` do not count toward the limit. Test keys do not collect anything and return only the acceptance response. [Revenue and expense guide](/en/api-introduction/revenue-expense) responses: '202': description: Request accepted content: application/json: schema: $ref: '#/components/schemas/RevenueExpenseSyncResponse' examples: Accepted: x-parity-id: accepted summary: >- Accepted response; the next request is allowed 30 minutes later value: acceptedAt: '2026-09-18T03:00:00Z' nextAvailableAt: '2026-09-18T03:30:00Z' headers: {} '401': description: API key authentication failed. The response has no body. '402': description: >- Your subscription is below the Standard plan. The response `code` is `PLAN_UPGRADE_REQUIRED`. Upgrade your plan from the billing menu in the Bolta dashboard, then call again. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: >- A collection for the same path is already running, including Bolta's regular collection. The response `code` is `SYNC_IN_PROGRESS`. Request again after it ends. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '422': description: >- No expense connection exists in the dashboard. The response `code` is `NO_SOURCE_CONNECTED`. Connect Hometax expenses in the Bolta dashboard first. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '429': description: >- The 30-minute interval or the 12-per-24-hours limit was exceeded. The response `code` is `SYNC_RATE_LIMITED`. Request again after `Retry-After`. headers: Retry-After: description: Seconds until you can retry schema: type: integer content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: >- Internal server error. The response `code` is `INTERNAL_SERVER_ERROR`. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '503': description: > The sync request cannot be evaluated right now. The response `code` is `SYNC_UNAVAILABLE`. Request again shortly. For a temporary internal API communication error, `code` is `SERVICE_UNAVAILABLE`. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' deprecated: false components: schemas: RevenueExpenseSyncResponse: type: object description: Sync request acceptance properties: acceptedAt: type: string format: date-time description: Time the request was accepted (UTC) nextAvailableAt: type: string format: date-time description: >- Next request time that clears the 30-minute interval (UTC). Does not reflect the 12-per-24-hours limit. required: - acceptedAt - nextAvailableAt ErrorResponse: type: object description: The error response returned when an API request fails properties: code: type: string description: Error type identifier message: type: string description: Error description traceId: type: string description: Request trace identifier required: - code - message - traceId securitySchemes: basicAuth: type: http scheme: basic description: >- Append a colon to your API key, Base64-encode it, and put it in the header. Enter the API key as the username and leave the password empty. ````