Challenge Overview
Note: This challenge has 3 prizes of the following. We are in the process of updating the page above but please make note below.
1st: $1000
2nd:$1000
3rd: $500
To get started with the DocuSign REST API you need to get a free developer account from the DocuSign Developer Center (www.docusign.com/devcenter)
Build an iOS app that integrates the DocuSign REST API and exposes the functionality listed below in an intuitive and easy to navigate way. The app needs to be written in Objective-C (no code porting allowed) and should be easily extensible. At a minimum the following DocuSign functionality needs to be available in the app, with additional points awarded for additional functionality:
1. Embedded Signing
2. Sending documents for signature (local document & through a Template)
3. Get the status of existing documents
4. Download documents
Participants are free to decide how they want to structure/organize the app menus and screens (i.e. tabs vs. pages vs. whatever), but there should be a focus on ease of use and simplicity. Submission needs to include a readme file that contains a basic description of what the app does and how to accomplish all the separate tasks. The app should have a reasonable amount of comments as well.
Additional Info
- The app needs to log the user in to their DocuSign account in order to see what documents are awaiting their signature, to be able to send a document for signature, and to accomplish the other tasks. This is as easy as making the Login API Call.
- For Embedded Signing (1), the app needs to use the Embedded Signing workflow, where a URL token is generated and is used to start the signing workflow, except that you’ll need to list the envelopes in your account that are awaiting your signature and allow the user to sign any one of them. Look for the Get List of Envelopes in Folders api call where the folder name is awaiting_my_signature.
- For Sending Docs for Signature (2), the user should be able to send a local document for signature, or send from an account template. Templates are design-time objects that and saved in the DocuSign Console and can be accessed in api calls. For more info please see the API Walkthroughs resource which has sample code for both of these api calls, as well as the documentation.
- For Getting Status of Existing Documents (3), the minimum requirement is for the user to be able to see all of the documents in their account and their corresponding statuses. Additional points given for added functionality, such as recipient info, date/time info, individual recipient statuses, etc. Please see the API Walkthroughs on how to get statuses back and do filtering through the api.
- For Downloading Documents (4), from the existing documents screen, on a given completed document, the user should be able to download the document locally.
- Higher scores will be awarded to apps that implement more features than the minimum 4 requirements listed above.
Final Submission Guidelines
Resources
If you have any questions about DocuSign API please post them on Stack Overflow using the DocuSignAPI tag:
http://stackoverflow.com/questions/tagged/docusignapi
DocuSign Developer Center (Your main resource hub)
http://www.docusign.com/developer-center
DocuSign API Explorer (let’s you test DocuSign API calls without writing any code)
http://iodocs.docusign.com/
DocuSign API Walkthroughs (sample code for accomplishing 9 common workflows)
http://iodocs.docusign.com/APIWalkthroughs
API Documentation
http://www.docusign.com/developer-center/documentation
Submission Details
Provide the github or codeplex URL to your project (yes it can be public)