You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use the library in my project to ask for signatures. As the documentation states after a task start request, we get the remaining credits only.
I just tested but got a "something went wrong on our side". The response contains "remaining_files" but no trace of "remaining_credits" nor "remaining_pages" as Task class references.
Are the credits converted to remaining files properly?
Does it require a library new release with the two new properties (Task::$remainingPages and Task::$remainingCredits) or the documentation needs an update ? Is the Task::$remainingFiles deprecated? It could be nice to add @deprecated in this case and mention it on the documentation.
I am a bit worried that the API may change without notice by removing data from response and break in production. Can you provide some information about your upgrade process?
Thank you
The text was updated successfully, but these errors were encountered:
When user do a start step, api knows the credits cost for the concrete tool, this means it will return remaining pages or remaining files. If you ask to info endpoint, api dones not knows about cost, so response will have remaining credits.
This means for many tools (all previous existing tools), the start will return the same remaining files as before because only new tools are using pages.
Hi,
I use the library in my project to ask for signatures. As the documentation states after a task start request, we get the remaining credits only.
I just tested but got a "something went wrong on our side". The response contains "remaining_files" but no trace of "remaining_credits" nor "remaining_pages" as Task class references.
Are the credits converted to remaining files properly?
Does it require a library new release with the two new properties (
Task::$remainingPages
andTask::$remainingCredits
) or the documentation needs an update ? Is theTask::$remainingFiles
deprecated? It could be nice to add@deprecated
in this case and mention it on the documentation.I am a bit worried that the API may change without notice by removing data from response and break in production. Can you provide some information about your upgrade process?
Thank you
The text was updated successfully, but these errors were encountered: