Documentation Index
Fetch the complete documentation index at: https://docs.syntage.com/llms.txt
Use this file to discover all available pages before exploring further.
Walk through
Creating credentials is the first step and is by using the POST /credentials endpoint and applying two approaches to retrieve the status after validation. The first optional block is using POST /webhook-endpoint to create a webhook endpoint that will listen tocredential.update events and notify in the URL once the validation against SAT is done; the second approach could be looping over GET /credentials/ to check the new status of the credential.
Usually, the validation with SAT portals takes between 10s to 20s.
A credential can have one of the following statuses:
| Status | Description |
|---|---|
waiting | Credential validation is temporarily disabled, usually because of an ongoing incident. The credential is validated later. |
pending | Credential validation has been requested and is waiting to be processed. |
valid | The credential was accepted by SAT and can be used for extractions. |
invalid | SAT rejected the credential during validation. |
disabled | SAT reported the credential as disabled or otherwise unrecoverable during validation. |
deactivated | Deprecated. Legacy status retained for existing records. Use disabled for credentials that can no longer be used. |
error | Credential validation failed because of an unexpected error. |
valid, which is a representation of a relationship between the taxpayer and the customer account.
At this point, we can start creating extractions, which are jobs to download the data from different SAT portals depending on the extractor. Two scenarios fit this case: one is having the schedulers for first time extractions enabled (this only can be done on Dashboard), which will trigger extractions automatically based on the rules defined in the scheduler; the second scenario is using the POST /extractions to create the desired extractions.
All extractions are created with a pending status which means that they are waiting in a queue to start. Once it starts, the status change to running. Extractions status are described here.
Customers can subscribe webhook endpoints to extraction events and be notified when extractions are created or updated.
The below sequence diagram represents the flow using the first time scheduler from Dashboard.
Below sequence diagram represents the flow using POST /extractions.
Customers can always retrieve information from extractions reaching the GET /extractions/ endpoint.
After extractions are finished documents can be retrieved through specific endpoint described in our documentation.
Along with Insights and other informations. Check the documentation for futher information.