awork is an awesome work management tool that helps you to be more productive. Next to a web app and an app for iOS and Android, we also provide a rich API that enables external developers to integrate awork into their workflows. Here you can find more details, FAQ's, code examples and a help forum to get you started even faster.
Detailed infos about the API can be found in our Developer Docs. If you have general questions about how awork works, check out our Help Center.
If you have any questions or need help, feel free to post in the awork Community Developer Forum.
We currently have code examples for C# and Typescript. You can find them in the examples folder above.
Yes, you can use this link to import it: https://swagger-doc.awork.com/api/swagger-combine
The awork API needs authentication for most endpoints.
The easiest way for authentication is to use Token Auth with an admin-level Bearer token which you can create in your awork application: Client Applications and API Keys
The other option for personal authentication is OAuth 2.0: API Authentication
In awork there are different permissions for each of the entities, like projects, tasks and users. For each entity you can either have no, read or write permissions. The permissions you have depends on your general user role in the workspace, allowing you f.e. to see all tasks and edit all projects, or your project specific permissions that are connected to your project role. So in one project you can be able to see all timetrackings, and in another one you can only see the project overview.
More information on permissions can be found in the Help Center or in the Permissions Section of the Developer Docs.
Yes, the awork API supports pagination. More information can be found in the Developer Docs. You can specify pagination attributes in your request by adding the page and pageSize attributes like this:
https://api.awork.com/api/v1/users?page=1&pageSize=50
Now you can reach the next page by setting page=2 and keeping the page size the same. The limit for the page size is 1000 entries.
The API supports filtering using the following syntax. You can filter most of the API endpoints by adding an additional filter attribute to your request: filterby=... More filter options can be found in the Filtering section of the Developer Docs.
https://api.awork.com/api/v1/users?filterby=firstname eq 'John'
In this example, you can filter all users and only return those that have a first name of John. If you want to filter a list of objects, like the members of a project, you can do so like this:
https://api.awork.com/api/v1/projects?filterby=members/any(p: p\FirstName eq 'Neil')
In this example only projects are returned that have a member with the first name Neil.
No, deleted entries cannot be requested from the API. Instead of deleting data completely, we recommend using the archiving option whenever possible.
Yes, you can create webhooks in awork. More information about this can be found in our Developer Docs.