Test Authentication in Formapi
A documented Formapi operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Test Authentication
- GETReads data · PDF
api.docspring.com/authentication
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Formapi operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Formapi operations
- Create a new PDF template with a form POST file uploadPOST · changes data
- Create a new custom file from a cached presign uploadPOST · changes data
- Create a new PDF template from a cached presign uploadPOST · changes data
- Create a folderPOST · changes data
- Create a new HTML templatePOST · changes data
- Creates a new data request token for form authenticationPOST · changes data
- Merge submission PDFs, template PDFs, or custom filesPOST · changes data
- Add new fields to a TemplatePUT · changes data
Questions
- Can HumDay test authentication in Formapi?
- Yes. This operation is published in Formapi's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Formapi account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Formapi.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Formapi account.
Where this came from
Read from a published API description for Formapi at docspring.com/api-docs/v1/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.