API and Integrations
API fundamentals
Workfront exposes a REST API for objects such as projects, tasks, issues, users, and custom forms. Clients authenticate with an API key, OAuth 2.0, or a session; the identity used determines permissions. Requests target object endpoints and can specify fields, filters, ordering, and paging. Filters use field names and modifiers, and nested or related objects can be requested with joins. Responses return JSON, and errors usually include a message and a status code. Rate limits and asynchronous jobs matter for bulk operations.
Integration traps
A common exam trap is assuming an API key has system-admin power. It inherits the access level and sharing of the user who owns it, so a missing permission often explains a 403 or empty result. Another trap is confusing the API with Fusion: the API is the transport, while Fusion orchestrates multi-step integrations. Also watch custom field identifiers: they use the field name, not the display label, and field names must be unique. Paging defaults can silently truncate large result sets; always set an explicit limit and loop until exhausted.
Worked example
You need projects updated since a date. Call the project search endpoint with a filter on lastUpdateDate using a greater-than-or-equal modifier, request only the fields you need, and page through results. If the call returns fewer projects than expected, verify the token owner can see those projects and that the date filter uses the correct format. Rule of thumb: debug permissions before debugging the query.