diff --git a/api-ref/authentication.mdx b/api-ref/authentication.mdx index 7fb67f6..c8ba105 100644 --- a/api-ref/authentication.mdx +++ b/api-ref/authentication.mdx @@ -4,7 +4,7 @@ icon: "lock-a" description: To get started using the Invopop API, you'll need to generate an access token for the workspace you'll be working with. --- -Invopop API Keys are generated using the [Console](https://console.invopop.com). Enter "Configuration", then "API Keys", and tap "New API Key". Enter some reference details and click "Save". You'll be presented with a screen showing a new token. You **must** copy and paste this token, as we do not store it anywhere. If you loose it, you'll need to create a +Invopop API Keys are generated using the [Console](https://console.invopop.com). Enter "Configuration", then "API Keys", and click "New API Key". Enter some reference details and click "Save". You'll be presented with a screen showing a new token. You **must** copy and paste this token, as we do not store it anywhere. If you loose it, you'll need to create a new API key. @@ -22,4 +22,4 @@ endpoint and curl: $ curl -H "Authorization: Bearer [token]" https://api.invopop.com/utils/v1/ping {"ping":"pong"} -``` +``` \ No newline at end of file diff --git a/guides/authentication.mdx b/guides/authentication.mdx index 570f173..bae1b31 100644 --- a/guides/authentication.mdx +++ b/guides/authentication.mdx @@ -23,13 +23,13 @@ the steps to either log in or create an account. 2. Enter the **API Keys** section. -3. Tap the "**New API Key**" button. +3. Click the "**New API Key**" button. 4. Provide a name for future reference, and any notes perhaps describing a use case, then click **Save**. 5. You'll be presented with a new token in text and a button to copy the - details. Tap the copy button, and paste the token somewhere safe. + details. Click the copy button, and paste the token somewhere safe. Invopop uses JSON Web Tokens. If you're interested in seeing the contents, @@ -72,4 +72,4 @@ connection and credentials are valid. ## Conclusion -You've now managed to authenticate with the Invopop API using a generated token. +You've now managed to authenticate with the Invopop API using a generated token. \ No newline at end of file diff --git a/guides/chargebee.mdx b/guides/chargebee.mdx index b5df23a..7a3d0dc 100644 --- a/guides/chargebee.mdx +++ b/guides/chargebee.mdx @@ -30,7 +30,7 @@ This guide assumes that you already have a Chargebee account configured. Firstly, we need to store the details of the supplier, the owner of the Chargebee account, in Invopop: -1. In the [console](https://console.invopop.com), go to "Contacts" then "Suppliers", and tap "New supplier". +1. In the [console](https://console.invopop.com), go to "Contacts" then "Suppliers", and click "New supplier". 2. Add the company's contact details, including the name, tax code, address, etc. in the form. 3. If you're issuing invoices from a region that requires special fields, please contact Invopop support for assistance. 4. Save the document. @@ -145,4 +145,3 @@ You would typically use either `invopop-include` to allowlist the customers to b When you configure a new custom field in Chargebee, it is not immediately added to any preexisting entities. The custom field is only attached to an entity after you edit and save it. This is particularly relevant to the `cf_invopop_include` field. The importer will always import a Customer unless the field is present and set to "False". To ensure the expected behaviour, you should probably [back-populate the field in bulk](https://www.chargebee.com/docs/2.0/bulk-operations.html) for all your Customers to "False" right after configuring the field. - diff --git a/guides/es-ticketbai.mdx b/guides/es-ticketbai.mdx index 2c6ab22..21489ba 100644 --- a/guides/es-ticketbai.mdx +++ b/guides/es-ticketbai.mdx @@ -56,7 +56,7 @@ Currently the Invopop TicketBAI integration does not require a registration work -Head over to **Configuration**, **Apps**, and find **TicketBAI** from the list of apps to discover. Tap the **Connect** button to enable. +Head over to **Configuration**, **Apps**, and find **TicketBAI** from the list of apps to discover. Click the **Connect** button to enable. No further configuration is required. @@ -381,4 +381,4 @@ Observations: -## FAQ +## FAQ \ No newline at end of file diff --git a/guides/gr-iapr.mdx b/guides/gr-iapr.mdx index 8d39ce0..d3d8689 100644 --- a/guides/gr-iapr.mdx +++ b/guides/gr-iapr.mdx @@ -5,7 +5,7 @@ description: Send invoices and credit notes to the Greek IAPR via the myDATA pla ## Introduction -The myDATA (My Digital Accounting and Tax Application) platform is Greece’s standardized electronic invoicing and bookkeeping system, managed by the Independent Authority for Public Revenue (IAPR). This system enables businesses to report invoices and accounting data in real time, ensuring compliance with Greek tax regulations. +The myDATA (My Digital Accounting and Tax Application) platform is Greece's standardized electronic invoicing and bookkeeping system, managed by the Independent Authority for Public Revenue (IAPR). This system enables businesses to report invoices and accounting data in real time, ensuring compliance with Greek tax regulations. This guide will walk you through the process of reporting invoices to the IAPR using myDATA, first registering a supplier, and then issuing invoices and credit notes in their name. @@ -30,15 +30,15 @@ The following steps must be done from the [Invopop Console](https://console.invo -Enter the **Configuration** section, then tap **Apps**. Tap on the **Connect** button of the **ILYDA Greece** app. +Enter the **Configuration** section, then click **Apps**. Click on the **Connect** button of the **ILYDA Greece** app. ILYDA Greece App -Tap the **Configure** button on the app, and choose the "Environment" you want to use. +Click the **Configure** button on the app, and choose the "Environment" you want to use. -Tap the **Save** button. +Click the **Save** button. @@ -60,7 +60,7 @@ The workflow should be named something like "Issue IAPR Invoice", and it will co - **Send to IAPR (via ILYDA)**. - **Set State** - to "sent". -Tap the **Save** button to ensure the workflow has been persisted. +Click the **Save** button to ensure the workflow has been persisted. Copy and paste the following example in the workflow editor: @@ -271,4 +271,4 @@ If you have further questions, don't hesitate to contact the [Invopop support te For further details on how GOBL prepares data for conversion, see the [Greek Tax Regime](https://github.com/invopop/gobl/blob/main/regimes/gr/README.md). - + \ No newline at end of file diff --git a/guides/workflows.mdx b/guides/workflows.mdx index 181650a..ff50147 100644 --- a/guides/workflows.mdx +++ b/guides/workflows.mdx @@ -23,7 +23,7 @@ While it is possible to create workflows via the API, we recommend using the [In - Use the sidebar and tap on the **Workflows** section. + Use the sidebar and click on the **Workflows** section. @@ -45,9 +45,9 @@ This will save the new workflow and present the empty workflow editor screen. -Give your workflow a name for easy identification, like "Process Invoice" by tapping on the pencil symbol in the top bar. +Give your workflow a name for easy identification, like "Process Invoice" by clicking on the pencil symbol in the top bar. -Add steps to your new workflow by tapping on the **+** button and selecting an action from the right. Some steps will require configuration in order to function correctly. +Add steps to your new workflow by clicking on the **+** button and selecting an action from the right. Some steps will require configuration in order to function correctly. The "developer mode" switch at the top right can be used to display the workflow as a JSON document. This makes it really easy to copy and paste workflows from examples or other workspaces. Just be sure to return to the visual editor view to ensure the document is validated. @@ -67,4 +67,4 @@ Before a job can be executed however, you need to [upload the data](/api-ref/sil As a job is executed, the silo entry will be updated with any changes or attachments generated during processing. -The status of a job can be seen in the silo entry's activity tab, or in the **Workflows** - **History** section accessible from the left sidebar. +The status of a job can be seen in the silo entry's activity tab, or in the **Workflows** - **History** section accessible from the left sidebar. \ No newline at end of file diff --git a/mint.json b/mint.json index 8bbdd2a..58684ea 100644 --- a/mint.json +++ b/mint.json @@ -46,7 +46,10 @@ "navigation": [ { "group": "Introduction", - "pages": ["introduction/readme", "introduction/glossary"] + "pages": [ + "introduction/readme", + "introduction/glossary" + ] }, { "group": "API", @@ -73,7 +76,10 @@ }, { "group": "GOBL", - "pages": ["api-ref/silo/gobl/build", "api-ref/silo/gobl/sign"] + "pages": [ + "api-ref/silo/gobl/build", + "api-ref/silo/gobl/sign" + ] } ] }, @@ -100,7 +106,6 @@ } ] }, - { "group": "Sequences", "icon": "list", @@ -150,7 +155,10 @@ { "group": "Utils", "icon": "wrench", - "pages": ["api-ref/utils/ping", "api-ref/utils/uuid"] + "pages": [ + "api-ref/utils/ping", + "api-ref/utils/uuid" + ] } ] }, @@ -177,4 +185,4 @@ "linkedin": "https://www.linkedin.com/company/invopop/", "github": "https://github.com/invopop" } -} +} \ No newline at end of file