start

jay (jay@undisclosed.example.com) — 2015-02-18T18:08:15+00:00

Welcome... to the 4theFile Support Wiki This wiki provides help and documentation on various aspects of the 4theFile system. Contact Technical Support If you require technical assistance from a mostly-live humanoid, please contact Purplewire technical support Search

sidebar

jay (jay@undisclosed.example.com) — 2015-02-18T18:07:06+00:00

4theFile Home Support Home Contact Tech Support 4theFile FAQs The 4theFile API * The 4theFile API Overview * The 4theFile API Reference * Perl Client Library reference implementation

tech_support_contacts

jay (jay@undisclosed.example.com) — 2015-02-18T16:45:55+00:00

Contact Tech Support Call the support line, M-F, from 9am - 5pm ET at 315-234-0079 x345 or via email at: support@purplewire.com

perl_client_library

jay (jay@undisclosed.example.com) — 2011-11-10T19:34:03+00:00

Perl Client Library reference implementation This simple implementation illustrates how to use a low-level HTTP library to provide an object-oriented interface to the 4theFile API functionality. The users of the resulting module don't need to think about REST or HTTP; their interface is practically identical to what they would see if the 4theFile Resource data was stored in a local database on their server.

4thefile_api_reference

jay (jay@undisclosed.example.com) — 2011-01-04T22:19:50+00:00

4theFile API Reference Introduction The 4theFile API is a REST-style API that uses simple standard technologies: HTTP requests with Basic auth, and XML or JSON response content. The API is designed primarily to allow developers and maintainers of web applications to easily provide an email interface to their applications and integrate the list of submitted emails into their application's interface

resource_attachment_list - created

jay (jay@undisclosed.example.com) — 2011-01-04T21:50:03+00:00

GET /resources/:resourcekey/attachments.format GET /resources/:resourcekey/attachments.format returns a list of attachments and some metadata for resource :resourcekey. If the resource exists but has no attachments, the attachment_count will be 0 and there will be no attachment elements. If the :resourcekey does not exist, a 404 will be returned.

get_collection_resources

jay (jay@undisclosed.example.com) — 2010-12-02T22:34:36+00:00

GET /collections/:collectionkey/resources.format GET /collections/:collectionkey/resources.format returns the list of resources in collection :collectionkey * response formats supported: .xml, .json * query parameters: * per_page (optional - max resources to return at once, default 30)

get_collections

jay (jay@undisclosed.example.com) — 2010-11-08T23:37:01+00:00

GET /collections.format returns the list of collections owned by you. * response formats supported: .xml, .json * query parameters: none * Curl command line: curl -u user:apikey https://4thefile.com/api_v1/collections.xml * example xml response:

4thefile_api

jay (jay@undisclosed.example.com) — 2010-11-08T21:53:27+00:00

The 4theFile API Overview The 4theFile API provides RESTful web services for use in integrating 4theFile with other web-based applications. The API has the following features: * all communication via HTTP or HTTPS * authentication via HTTP Basic auth

leadimporttemplate.xls

tiffany (tiffany@undisclosed.example.com) — 2009-11-24T14:55:57+00:00

error.png

tiffany (tiffany@undisclosed.example.com) — 2009-11-24T14:43:24+00:00