Developer API

The Workato Developer API offers access to a wide range of Workato resources that enable you to manage recipes, connections, jobs, and more. You can use this API to automate every aspect of your Workato workspace, from deploying recipe manifests between development and production environments to rolling out new on-premises agents within your network landscape.

Base URL

The Workato API is a collection of API endpoints for interacting with Workato users, recipes, and more. Each endpoint contains the base URL and the resource path to the object.

The base URL of the API endpoint depends on the data center that you use:

• United States (US) data center: https://www.workato.com/api/
• Europe (EU) data center: https://app.eu.workato.com/api/
• Japan (JP) data center: https://app.jp.workato.com/api/
• Singapore (SG) data center: https://app.sg.workato.com/api/
• Australia (AU) data center: https://app.au.workato.com/api/

Authentication

Workato API uses API tokens to authenticate requests. You may generate an API token by creating an API client under Workspace admin and assigning it both a client role and project scopes.

Provide API tokens as a bearer token

Provide your API client’s API token in the request headers as a bearer token.

1
curl -X GET https://www.workato.com/api/users/me \
2
      -H 'Authorization: Bearer <api_token>'

Supported Formats

Workato API supports sending request body with the application/json content-type. All replies are also encoded in application/json; charset=utf-8.

How to generate an API token

You can generate an API token by creating an API Client under Workspace admin and under the API Clients tab. Find out more about configuring API clients and roles.

HTTP response codes

200 Success

The 200 Success response indicates that the request was processed successfully by the server. The response body varies depending on the endpoint and operation performed, but it typically contains the requested data or a confirmation of the action performed.

Sample reply

1
{
2
    "success": true
3
}

400 Bad Request

The 400 Bad Request error indicates that the server couldn’t process the request due to client-side issues. Common causes include malformed requests, invalid fields, or violations of field constraints, such as unsupported data types.

Sample 400 reply

1
{
2
    "errors": [
3
        {
4
            "code": 400,
5
            "title": "No workspaces found matching the specified workspace filter conditions."
6
        }
7
    ]
8
}

401 Unauthorized

The 401 Unauthorized error is returned when the request lacks valid authentication credentials. Common causes include missing tokens, invalid tokens, or incorrect credentials.

Sample 401 reply

1
{
2
    "errors": [
3
        {
4
            "code": 401,
5
            "title": "Unauthorized"
6
        }
7
    ]
8
}

403 Forbidden

The 403 Forbidden error indicates that the client is authenticated but doesn’t have the necessary permissions to access the requested resource.

Sample 403 reply

1
{
2
    "errors": [
3
        {
4
            "code": 403,
5
            "title": "Forbidden"
6
        }
7
    ]
8
}

404 Not Found

The 404 Not Found error is returned when the requested resource doesn’t exist or can’t be found. This can occur if the URL is incorrect or the resource has been deleted.

Sample 400 reply

1
{
2
    "errors": [
3
        {
4
            "code": 404,
5
            "title": "Not found"
6
        }
7
    ]
8
}

500 Server Error

The 500 Server Error code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request. This error is usually caused by server-side issues.

Sample 500 reply

1
{
2
    "errors": [
3
        {
4
            "code": 500,
5
            "title": "Server error",
6
            "detail": "3188c2d0-29a4-4080-908e-582e7ed82580"
7
        }
8
    ]
9
}