Wave Reusables REST API v3.0 Help

Introduction

The Wave Reusables API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

You can use the Wave Reusables API in test mode, which does not affect your live data or interact with the production environments. The API token you use to authenticate the request determines whether the request is live mode or test mode.

The Wave Reusables API differs for every account as we release new versions and tailor functionality.

Authentication

The Wave Reusables API uses API tokens to authenticate requests.

Your API tokens carry many privileges, so be sure to keep them secure! Do not share your API tokens in publicly accessible areas.

Authentication to the API is performed via OAuth2.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

Errors

Wave Reusables uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted). Codes in the 5xx range indicate an error with Wave Reusables' servers (these are rare).

Handling Errors

Our Client libraries raise exceptions for many reasons, such as a failed saves, invalid parameters, authentication errors, and network unavailability. We recommend writing code that gracefully handles all possible API exceptions.

APIs