Add api communication #11
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
noplisu
force-pushed
the
gl-rl-add-api-communication
branch
from
8feb887
to
e0e776b
Compare
samlown
previously requested changes
Feb 3, 2024
We want to be able to post invoices into the KSeF API and get back the UPO that proves that the invoice has been accepted by the system. The first step is communicating with the API to get the interactive session. To get the interactive session we need to have the context in which we send the requests this context is the tax id of the company. Next we need a valid token from ksef it can be generated from ksef.mf.gov.pl/web for production or from ksef-test.mf.gov.pl/web for test. The last thing is the public key provided from https://ksef.mf.gov.pl/ and https://ksef-test.mf.gov.pl/. To get the session token we first need to get the authorization challenge for our context. Then we use the context, token and authorization challenge to create a interactive session and get the session token used in other requests.
We want to be able to post invoices into the KSeF API and get back the UPO that proves that the invoice has been accepted by the system. Here we prepare the request that posts the invoice to KSeF backend. We also prepare a request that checks the invoice status. With those requests we can post the invoice and check if it finished processing.
We want to be able to post invoices into the KSeF API and get back the UPO that proves that the invoice has been accepted by the system. The UPO files are generated after the interactive session is terminated. To get the files we first need to terminate the session then after it finishes generating the UPO files we can get them from the session status request. Here we the session termination and status requests used in the process.
noplisu
force-pushed
the
gl-rl-add-api-communication
branch
from
e0e776b
to
e11fc8c
Compare
noplisu
force-pushed
the
gl-rl-add-api-communication
branch
3 times, most recently
from
a5d76a0
to
786be84
Compare
We want to be able to post invoices into the KSeF API and get back the UPO that proves that the invoice has been accepted by the system. Here we get the parameters from the CLI and use the requests we prepared to post the invoice and save the UPO. The example command would look like go run ./cmd/gobl.ksef send ./test/data/out/invoice-pl-pl.xml 1234567788 624A48824F01935DADE66C83D4874C0EF7AF0529CB5F0F412E6932F189D3864A ./api/keys/test.pem
noplisu
force-pushed
the
gl-rl-add-api-communication
branch
from
786be84
to
e8b4051
Compare
torrocus
reviewed
Mar 7, 2024
torrocus
reviewed
Mar 7, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Summary
We want to be able to post invoices into the KSeF API and get back the UPO that proves that the invoice has been accepted by the system.
The first step is communicating with the API to get the interactive session. To get the interactive session we need to have the context in which we send the requests this context is the tax id of the company. Next we need a valid token from KSeF it can be generated from https://ksef.mf.gov.pl/web for production or from https://ksef-test.mf.gov.pl/web for test. The last thing is the public key provided from https://ksef.mf.gov.pl/ and https://ksef-test.mf.gov.pl/.
The UPO files are generated after the interactive session is terminated. To get the files we first need to terminate the session then after it finishes generating the UPO files we can get them from the session status request.
The process is getting the authorization challenge, initializing the interactive session, posting the invoice using the session, waiting for the invoice to process by checking the status. When it is finished we terminate the session wait for the process to finish by checking the status and save the UPO.
An example of using the CLI to post an invoice would look like:
Changes
We add a CLI command for posting the invoice into the KSeF API.
We add handling for requests:
The process of sending a invoice works like presented on this graph:
