tallyfy / api-support

This is a public repository aimed specifically at developers using Tallyfy. Tallyfy lets anyone document, launch and run workflows. If you have API questions - please post them here!

Intro

This is a public repository aimed specifically at developers using the Tallyfy API.

Tallyfy lets anyone run smart, digitized operations. It's an API-first and beautifully designed workflow platform that empowers anyone to document, automate and track workflows in real-time. Transform every approval, task, business process, SOP, playbook, form or document into a repeatable, predictable blueprint.

To view our API docs - please go to https://go.tallyfy.com/api

If you have API questions - please post them here! All other issues should be reported to [e-mail]

Our support documentation is at https://support.tallyfy.com and general information is at https://tallyfy.com

Folders

The folder "Backup Blueprints" has some sample Python (contributions untested) to backup your Tallyfy blueprints.

Posting guidelines

1. No inappropriate/offensive language. We reserve the right to edit/remove any post which is deemed inappropriate or offensive by Tallyfy.

2. Check first that the issue you are reporting has not already been reported elsewhere. If it has been reported in another ticket, you may give that ticket a [+1] and/or comment additional helpful information so that we may deal with the issue in the most complete manner possible.

3. Avoid using any uniquely identifiable information in your posts/comments. This includes but is not limited to user ID's, org ID's, user emails, etc. To represent these identifiers in your tickets, we encourage you to user curly braces around the identifier’s name, such as {org_id} or {user_id}.

4. When reporting an issue, always include these pieces of information:
   a. URL (with identifiers removed)
   b. Verb (GET, POST, UPDATE, DELETE)
   c. Request payload and headers
   d. Response and response code