feat(adapters): Firma.dev e-signature - #786
Merged
Merged
Conversation
Firma.dev asked to be in the E-Signature category next to Dropbox Sign. 13 tools on their REST API: templates and their recipient slots, a draft signing request from a template, send, resend and cancel, the list of signing requests (trimmed to what a model needs), one request with its recipients, the audit trail and the signed PDF's download URL, plus the company account and its remaining credits. The key goes in the Authorization header without a prefix. Every Firma workspace has a test key that consumes no credits and watermarks the documents; the instructions start people there. Creating a request makes a draft; sending it emails the signers and spends a credit, so send, resend and cancel are advertised as open-world writes and the instructions ask for the user's go-ahead first. No workspace tools: their responses carry API keys. Verified: routes answer 401 without a key and INVALID_API_KEY with a wrong one (so the header is read); 21 static tests through the real engine and the list transform. Live reads are in the spec behind RUN_FIRMA_LIVE for a test key.
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Requested by Firma.dev (contact form, 25 Sep): a connector in the E-Signature category next to Dropbox Sign.
13 tools:
firma_get_company(credits),firma_list_templates,firma_get_template,firma_list_template_recipients,firma_list_signing_requests(trimmed view),firma_get_signing_request,firma_list_signing_request_recipients,firma_get_signing_request_audit,firma_get_signed_document_url,firma_create_signing_request_from_template(draft, no credit),firma_send_signing_request,firma_resend_signing_request,firma_cancel_signing_request.Authorization: <key>, no prefix. Test keys (no credits, watermarked) recommended first in the instructions.RUN_FIRMA_LIVE(test key is enough). Routes probed: 401 without key,INVALID_API_KEYwith a wrong one.