Skip to content

[IMP] extract_api: adapt documentation to the new integration flow #18185

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
lobaudoux wants to merge 1 commit into from
Closed

[IMP] extract_api: adapt documentation to the new integration flow #18185

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 3 additions & 6 deletions content/developer/reference/extract_api.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -555,12 +555,9 @@ Integration Testing
You can test your integration by using *integration_token* as ``account_token`` in the
:ref:`/parse <extract_api/parse>` request.

Using this token put you in test mode and allows you to simulate the entire flow without really
parsing a document and without being billed one credit for each successful **document** parsing.

The only technical differences in test mode is that the document you send is not parsed by the
system and that the response you get from
:ref:`/get_result <extract_api/get_result>` is a hard-coded one.
Using this token allows you to parse documents without being billed. Please note that the
integration token is subject to strict daily rate limits and is intended solely for testing
purposes. If you exceed this limit, you must wait a full day for the limit to reset.

A python implementation of the full flow for invoices can be found
:download:`here <extract_api/implementation.py>`.
Expand Down